e992832cd3
During OpenStack history we have added a lot of OpenStack project teams, and while we have dropped a few along the way, we do not have a clear set of considerations to take into account in that process. In particular, relying purely on activity levels to consider dropping projects has proved unproductive in the past, as well as encouraging people to step up for less-strategic abandoned projects. Here is a set of guidelines we should use in future such discussions. Change-Id: I2c798a6d52a2666657dce201a7c02561d2f4d4ed
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.