I've also put up the following which is based on a tool that has been use in taskflow. http://pypi.python.org/pypi/doc8 And inclusion into stackforge (getting it off my github repo). https://review.openstack.org/#/c/94236/ Seems like we can do some of these rules in it. Its pluggable via stevedore[1] so shouldn't be to hard to add custom checks. [1] https://github.com/harlowja/doc8/blob/master/doc8/main.py#L94 -----Original Message----- From: Alexis Lee <alexisl at hp.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org> Date: Monday, May 19, 2014 at 9:38 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org> Subject: [openstack-dev] Divergence of *-specs style checking >We're seeing the spread of various *-specs projects now, which is great >to see. Some of these (nova, neutron and tripleo) include a Python unit >test (tests/test_titles.py) to check the specs follow the template. The >test has been copy-pasted between projects and it's diverging already. >Nova has a couple of extra tests; Neutron has some custom directives; >TripleO disallows additional sections. > >It seems reasonable that while the specific allowed sections and >subsections may vary, the general guidance should apply across all >OpenStack projects much as code shares HACKING. > >I put up a review here: https://review.openstack.org/#/c/91801/ >which makes it more data-driven. Potentially the TITLES structure could >be read from a per-project YAML file and the test itself could be drawn >from some common area? > > >Alexis >-- >Nova Engineer, HP Cloud. AKA lealexis, lxsli. > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev