64d96fda2a
The yaql library has been maintained under murano's governance, but the murano project has been inactive for several cycles. Because this library is used by heat and mistral, we have to maintain it as long as these two projects are maintained. This proposes moving the yaql project to heat's governance as the first step. Later we'll update the core reviewer of the repository so that both heat team and mistral team can maintain it. This transition was earlier proposed in the mailing list[1] but we haven't received any feedback from the murano project, unfortunately. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/KFTPG45LEB5QYY4NELA7EQJ56MSOWULK/ Change-Id: If5d3ed3a8314a8f650cd90416b53e02a84e4ed44 |
||
---|---|---|
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.