0cbc632a38
We have a huge timeout right now for the addition of new projects to a team which is just slowing things down for usually no reason. This aims at speeding up the process by replacing the current one-week waiting period with a need for only two roll-call +1 votes. We can always revert additions if they don't make sense. Change-Id: I4a88916f81699a343812c8e01f7419d33cab1ac3 |
||
|---|---|---|
| doc | ||
| goals | ||
| openstack_governance | ||
| pre-history | ||
| reference | ||
| resolutions | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .yamllint | ||
| .zuul.yaml | ||
| CHAIR.rst | ||
| README.rst | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
openstack-governance
The repository https://opendev.org/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.