d7f99e14e9
Recent threads on the openstack-discuss mailing list [0] suggest revisiting the idea of formatting the help-wanted list to represent the value each initiative provides a sponsor. This feedback was given to the Technical Committee during the Vancouver summit in 2018. This is an attempt at describing the value well-documented software has on a business. [0] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html Change-Id: Id12e50f084025713fc3aefc9c9ddf50b3a9072db |
||
---|---|---|
doc | ||
goals | ||
openstack_governance | ||
pre-history | ||
reference | ||
resolutions | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.yamllint | ||
.zuul.yaml | ||
CHAIR.rst | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
openstack-governance
The repository http://git.openstack.org/cgit/openstack/governance/ contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee. It also contains a library for accessing some of the machine-readable data in the repository.
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://governance.openstack.org/tc/ for details.