Cleaned up specs directory

Added a section title try for `playbook impact` as well as a new
section for `playbook/role impact`.

Change-Id: I0e7cf5f8ab56d155463a28093d6572692d1b9973

AUTHORS

@@ -0,0 +1,11 @@
+Darren Birkett <darren.birkett@gmail.com>
+Jacob Wagner <swagner1104@gmail.com>
+Javeria Khan <javeria.ak@gmail.com>
+Javeria Khan <javeriak@plumgrid.com>
+Kenny Johnston <kencjohnston@gmail.com>
+Kevin Carter <kevin.carter@rackspace.com>
+Matthew Kassawara <mkassawara@gmail.com>
+Matthew Thode <mthode@mthode.org>
+Nolan Brubaker <nolan.brubaker@rackspace.com>
+elextro <miguel.cantu@rackspace.com>
+philip williams <phil@philw.com>

ChangeLog

@@ -0,0 +1,18 @@
+CHANGES
+=======
+
+* Cleaned up specs directory
+* Multi-region swift
+* Add standalone swift testing
+* Keystone Federation Deployment
+* Cleaned up all specs
+* Add PLUMgrid Neutron Plugin to neutron playbooks
+* Modularize configuration files
+* Propose new developer documentation
+* added spec build-facts-archive
+* Add spec for BP implement-ceilometer
+* Add modularize-neutron-plays specification
+* Add master-kilofication specification
+* Adds minimal kilo spec
+* Initial commit for OS-Ansible-Deployment specs
+* Added .gitreview

README.rst

@@ -42,4 +42,7 @@ confidence in the Jenkins result), please execute the following command::
   $ tox
 
 After running ``tox``, the documentation will be available for viewing in HTML
-format in the ``doc/build/`` directory.
+format in the ``doc/build/`` directory. Tox is also used to update the
+AUTHORS and ChangeLog files for the specs repository. For every submission
+these files should be updated using the ``tox`` command.
+

specs/template.rst

@@ -77,8 +77,8 @@ a full literature review, but it should demonstrate that thought has been put
 into why the proposed solution is an appropriate one.
 
 
-Playbook impact
----------------
+Playbook/Role impact
+--------------------
 
 What impact will there be on the playbooks?
 

tests/test_titles.py

@@ -62,7 +62,10 @@ class TestTitles(testtools.TestCase):
             self.assertIn('developer impact', titles[proposed])
             self.assertIn('end user impact', titles[proposed])
             self.assertIn('performance impact', titles[proposed])
-            self.assertIn('playbook impact', titles[proposed])
+            try:
+                self.assertIn('playbook impact', titles[proposed])
+            except AssertionError:
+                self.assertIn('playbook/role impact', titles[proposed])
             self.assertIn('security impact', titles[proposed])
             self.assertIn('upgrade impact', titles[proposed])