OpenStack Technical Committee Decisions
Go to file
Zuul 6d1008c7b7 Merge "Allow obtaining specifically tagged governance data" 2019-02-06 23:18:45 +00:00
doc Update sphinx extension logging 2018-10-16 21:35:30 -05:00
goals Update the policy-in-code goal for neutron 2018-12-14 16:51:09 +00:00
openstack_governance Allow obtaining specifically tagged governance data 2019-01-14 14:06:09 +11:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Merge "Add Ansible roles for managing HSM software" 2019-02-06 18:16:41 +00:00
resolutions Fix typo 2018-12-19 12:24:37 +13:00
tools report whether delegated reviewer has commented on patch 2018-12-12 11:48:18 -05:00
.gitignore add module for fetching and parsing governance data 2018-11-07 08:30:27 -05:00
.gitreview Added .gitreview 2013-08-30 16:00:06 +00:00
.stestr.conf add module for fetching and parsing governance data 2018-11-07 08:30:27 -05:00
.yamllint Reduce the scope of yamllints coverage 2016-10-18 14:09:41 +11:00
.zuul.yaml add module for fetching and parsing governance data 2018-11-07 08:30:27 -05:00
CHAIR.rst add a note to chair duties about tracking board work 2018-12-20 14:06:43 -05:00
README.rst clean up readme 2018-11-30 14:10:20 -05:00
requirements.txt add a script to randomly assign TC members as liaisons 2018-10-09 15:55:24 -04:00
setup.cfg move members file parsing into a reusable module 2018-10-08 19:16:34 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt add module for fetching and parsing governance data 2018-11-07 08:30:27 -05:00
tox.ini add module for fetching and parsing governance data 2018-11-07 08:30:27 -05:00

README.rst

openstack-governance

The repository http://git.openstack.org/cgit/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.