![]() This project is not healthy as there is no PTL. There is time till milestone-2 of this release cycle to recover the situstion and make project healthy and we can remove it from inactive list. Refer to the below doc to know more about Inactive state - https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html Project gerrit and zuul stats: Validating Gerrit... * There are 11 ready for review patches generated within 180 days * There are 1 not reviewed patches generated within 180 days * There are 10 merged patches generated within 180 days * Unreviewed patch rate for patches generated within 180 days is 9.0 % * Merged patch rate for patches generated within 180 days is 90.0 % * Here's top 10 owner for patches generated within 180 days (Name/Account_ID: Percentage): - OpenStack Release Bot : 27.27% - OpenStack Proposal Bot : 18.18% - XueFengLiu : 18.18% - Erik Olof Gunnar Andersson : 9.09% - Ghanshyam : 9.09% - Dmitriy Rabotyagov : 9.09% - Bui Doan Dang : 9.09% Validate Zuul... Set buildsets fetch size to 500 * Repo: openstack/python-senlinclient gate job builds success rate: 90% * Repo: openstack/senlin-dashboard gate job builds success rate: 92% * Repo: openstack/senlin gate job builds success rate: 94% * Repo: openstack/senlin-tempest-plugin gate job builds success rate: 95% Change-Id: I2b1562be79187beb183ffc173a4deebc127b8da4 |
||
---|---|---|
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.