openinfra/interop
Code Issues Proposed changes

Update tox.ini to test all rst, fix tox errors

Browse Source 
Updated tox.ini to check current rst documents. Fixed tox errors
in checked documents. Semantics of docments remained unchanged

Change-Id: Ic4b628b551e0c438ca71d5728afa7172bc3cf128
This commit is contained in:
Chris Hoge 2015-05-10 12:42:16 -07:00 committed by Justin Shepherd
parent 7402f39f9a
commit 32bed9e1c8
8 changed files with 36 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.rst
View File

@ -2,7 +2,8 @@
Understanding the DefCore Guidelines
=================================================
This repository contains DefCore committee managed files that provide guidance for the OpenStack community.
This repository contains DefCore committee managed files that provide guidance
for the OpenStack community.
NOTE: Changes to file requires approval of the DefCore committee chair(s).

32
process/2015A.rst
View File

@ -10,25 +10,25 @@ bylaws and approved by the OpenStack Technical Committee and Board.
Expected Time line:
---------------------------------------
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| Time Frame | Milestone | Activities | Lead By |
+============+===========+====================================+===========+
| -3 months | S-3 | "Preliminary” draft (from current) | DefCore |
+------------+-----------+------------------------------------+-----------+
+============+===========+======================================+===========+
| -3 months | S-3 | \"Preliminary\" draft (from current) | DefCore |
+------------+-----------+--------------------------------------+-----------+
| -2 months | S-2 | ID new Capabilities | Community |
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| -1 month | S-1 | Score Capabilities | DefCore |
+------------+-----------+------------------------------------+-----------+
| Summit | S | "Solid" draft | Community |
+ + +------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| Summit | S | \"Solid\" draft | Community |
+ + +--------------------------------------+-----------+
| | | Advisory/Deprecated items selected | DefCore |
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| +1 month | S+1 | Self-testing | Vendors |
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| +2 months | S+2 | Test Flagging | DefCore |
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
| +3 months | S+3 | Approve Guidance | Board |
+------------+-----------+------------------------------------+-----------+
+------------+-----------+--------------------------------------+-----------+
Note: DefCore may accelerate the process to correct errors and omissions.
@ -113,7 +113,8 @@ A4. DefCore Committee identifies required capabilities
6. Capabilities will not be added without being advisory in the previous
Guideline.
A5. Foundation Staff recommends OpenStack Components and OpenStack Platform Scope
A5. Foundation Staff recommends OpenStack Components and OpenStack Platform
Scope
1. Foundation Staff recommends capabilities to include in each OpenStack
Component.
@ -244,9 +245,10 @@ D1. Board will review and approve DefCore Guideline from draft
D2. DefCore Committee has authority on test categorization
1. DefCore Committee can add flagged tests before and after Guideline approval.
2. DefCore Committee cannot add additional Tests to Capability mappings after
1. DefCore Committee can add flagged tests before and after Guideline
approval.
2. DefCore Committee cannot add additional Tests to Capability mappings
after approval.
3. DefCore Committee maintains the test to capability mappings in the
JSON representation.

4
process/DesignatedSections.rst
View File

@ -16,7 +16,9 @@ Designated Sections Selection Guidance
_Approved 2014 Dec 2_
There DefCore committee identified 10 selection criteria. The first seven are technical from the TC and last three allow the Board to resolve issues without needed a technical judgement.
There DefCore committee identified 10 selection criteria. The first seven are
technical from the TC and last three allow the Board to resolve issues without
needed a technical judgement.
1. Designated if the code provides the project external REST API

1
test-requirements.txt
View File

@ -1 +1,2 @@
pygments
doc8

3
tox.ini
View File

@ -10,5 +10,4 @@ deps = -r{toxinidir}/test-requirements.txt
[testenv:doc8]
commands =
doc8 -e .rst 2015.03.rst 2015.04.rst 2015.next.rst CoreDefinition.rst \
GovernanceProcess.rst ProcessCycles.rst README.rst lexicon.rst
doc8 *.rst **/*.rst