6a4953f71f
Create a single governance body to represent all contributors to OpenStack (developers, operators and end users of the software). The User Committee is defined in the OpenStack Foundation bylaws, and amending those is very costly (in time, money and effort). Luckily, the bylaws defer most of the UC details to a User Committee charter, which contents are modifiable by the User Committee itself. This change adds a minimal User Committee charter that implements the User Committee as a subcommittee of the Technical Committee. This allows to operate as a single group without requiring costly bylaws changes to be implemented first. Change-Id: I8614f650bbc4176929caf15304cdefaed070c3f6 |
||
|---|---|---|
| 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.