Update tox.ini to test all rst, fix tox errors
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
Justin Shepherd
parent
7402f39f9a
commit
32bed9e1c8
|
|
@ -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).
|
||||
|
||||
|
|
|
|||
|
|
@ -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 |
|
||||
+------------+-----------+------------------------------------+-----------+
|
||||
| -2 months | S-2 | ID new Capabilities | Community |
|
||||
+------------+-----------+------------------------------------+-----------+
|
||||
| -1 month | S-1 | Score Capabilities | DefCore |
|
||||
+------------+-----------+------------------------------------+-----------+
|
||||
| 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 |
|
||||
+------------+-----------+------------------------------------+-----------+
|
||||
+------------+-----------+--------------------------------------+-----------+
|
||||
| Time Frame | Milestone | Activities | Lead By |
|
||||
+============+===========+======================================+===========+
|
||||
| -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 |
|
||||
+ + +--------------------------------------+-----------+
|
||||
| | | 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,6 @@ Governance Process
|
|||
<https://wiki.openstack.org/wiki/Governance/DefCoreCommittee>`_.
|
||||
|
||||
* Process documents and other "rules of the road" will be maintained and
|
||||
voted on in `Gerrit
|
||||
voted on in `Gerrit
|
||||
<http://git.openstack.org/cgit/openstack/defcore>`_. Committee
|
||||
chairs will have +/-2 voting privilleges.
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Designated Sections
|
|||
intended by the project maintainers to be replaceable, extend the
|
||||
project REST API in a new or different way, or code that is being
|
||||
deprecated.
|
||||
|
||||
|
||||
Flagged Test
|
||||
A test that does not provide consistent results in the
|
||||
field and it not required for vendor self-test.
|
||||
|
|
@ -89,7 +89,7 @@ Participant
|
|||
Platform
|
||||
The collection of components required to use the least restricted mark.
|
||||
|
||||
Self-test
|
||||
Self-test
|
||||
Process by which a vendor runs tests against their product or service
|
||||
without 3rd party observation.
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Objectives
|
|||
* Establish the "must-pass" tests, processes and tools
|
||||
|
||||
* Define tests that will be used to determine core based on Spider
|
||||
cycle work
|
||||
cycle work
|
||||
|
||||
* Lower the water in the discussion to expose broader issues
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ Objectives
|
|||
~~~~~~~~~~
|
||||
|
||||
* Complete Capabilities Score for Havana (Advisory), Icehouse and
|
||||
Juno
|
||||
Juno
|
||||
|
||||
* Recommend by-laws changes for winter voting
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1,2 @@
|
|||
pygments
|
||||
doc8
|
||||
|
|
|
|||
Loading…
Reference in New Issue