f527be33b5
When we have the leaderless project, we should also check the project activity and if any project is not up to date to their basic activies then TC should discuss it to mark Inactive. Ref: This was discussed in previous PTG (2023.2 vPTG): - https://etherpad.opendev.org/p/tc-2024.1-tracker#L7 Change-Id: I7bcdb6051b6504b4155df06b263ae9bd9bf11b05 |
||
|---|---|---|
| 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.