OpenStack Technical Committee Decisions
d2bec92094
The previous wording introduced unneccesary confusion about when the goal would be set. Clarify that the goal is set at the beginning of a release cycle as usual, and should be completed by the end of the release cycle. Also, avoid using the word 'support' to refer to which versions of Python we run unit tests on. Change-Id: I461ba0c0d4bc1e3d7e2b71ab614003733afdd4ea |
||
---|---|---|
doc | ||
goals | ||
openstack_governance | ||
pre-history | ||
reference | ||
resolutions | ||
tools | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
- goals/
Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.