openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
3,474 Commits 1 Branch 18 Tags 40 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Zuul 6ea5fcac5b Merge "Add new charm repositories" 2018-11-21 19:49:30 +00:00
doc Update sphinx extension logging 2018-10-16 21:35:30 -05:00
goals Follow publish-to-pypi change 2018-11-05 10:01:51 +01:00
openstack_governance mark yamlutils module as private 2018-11-07 09:05:20 -05:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Merge "Add new charm repositories" 2018-11-21 19:49:30 +00:00
resolutions T Release Name 2018-10-19 20:59:43 +11:00
tools Add missing ws seperator between words 2018-11-19 15:48:00 +08: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
README.rst propose approval policy for goal responses 2016-08-30 14:56:20 -04: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

This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.

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://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.