
Last year we adjusted the definitions of the tools and clients Criteria to make them focus on usage by software external to the OpenStack community and internal to the OpenStack community respectively [1]. However, the definitions in the next.json document still reflect the old, outdated definitions. This patch sets that to rights by adjusting the definitions in the next.json document to reflect the current state of affairs. Note: I considered just removing the definitions here entirely, but it seems logical to keep them since the definitions in the CoreCriteria document can and do change over time (so it's nice to know how the Criteria were defined at the time the Guideline you're looking at was approved). [1] https://review.openstack.org/#/c/226978/ Change-Id: I57af817659a0d66a9d6c3c0d33e92e329033d5b5
Understanding the DefCore Guidelines
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).
DefCore Process Documentation
Want to certify as a vendor? Consult OpenStack Interop.
The /doc/source/process directory contains details about the DefCore process.
The /doc/source/schema directory contains details about the JSON schema versions used to express Guidelines.
The /doc/source/guidelines directory contains RST versions of the DefCore Guidelines approved by the OpenStack Board of Directors.
- Core Definition
-
doc/source/process/CoreDefinition.rst
- Process Goverance
-
doc/source/process/2015A.rst (please check for latest)
- Designated Sections
-
doc/source/process/DesignatedSections.rst
- Core Criteria
-
doc/source/process/CoreCriteria.rst
- DefCore Governance
-
doc/source/process/GovernanceProcess.rst
- Platform and Components
-
doc/source/process/PlatformCap.rst
- DefCore Cycles
-
doc/source/process/ProcessCycles.rst
- Terminology
-
doc/source/process/Lexicon.rst