e69637440f
Currently we try to monitor and move the inactive project to Inactive state before milestone-2 which is deadline from the release team. But there are chances that project can become inactive after milestone-2 and in that case we should mark it Inactive in that cycle itself so that user of it get a clear message about their maintenance status. Modifying the process doc to explicitly cover this case. Change-Id: I0c3908c93bc12db1fb8ef0d2c433352a83e49554 |
||
|---|---|---|
| doc | ||
| goals | ||
| openstack_governance | ||
| pre-history | ||
| reference | ||
| resolutions | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .yamllint | ||
| .zuul.yaml | ||
| bindep.txt | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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.