OpenStack Technical Committee Decisions
Go to file
Sean McGinnis 83ba960797 Update sphinx extension logging
Sphinx 1.6 deprecated using the application object to perform logging
and it will be removed in the upcoming 2.0 release. This updates our
extensions to use the recommended sphinx.util.logging instead.

Change-Id: Ibf9f1c84171b73bb620f8df9a26ae97a8545b4b2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2018-10-16 21:35:30 -05:00
doc Update sphinx extension logging 2018-10-16 21:35:30 -05:00
goals Merge "Add upgrade testing completion criteria for upgrade-checkers goal" 2018-09-25 18:16:17 +00:00
openstack_governance add a script to randomly assign TC members as liaisons 2018-10-09 15:55:24 -04:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Change email to a private one 2018-10-12 15:46:24 +02:00
resolutions Reverse sort order for resolution date globs 2018-10-05 16:44:07 +00:00
tools add a script to randomly assign TC members as liaisons 2018-10-09 15:55:24 -04:00
.gitignore ignore files created by pbr during build 2015-05-23 08:09:26 -07:00
.gitreview Added .gitreview 2013-08-30 16:00:06 +00:00
.yamllint Reduce the scope of yamllints coverage 2016-10-18 14:09:41 +11:00
.zuul.yaml Use tox-docs for building 2018-10-07 10:31:46 +02: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 Inherit openstackdocstheme for TC site 2018-09-28 13:03:26 +02:00
tox.ini Use tox-docs for building 2018-10-07 10:31:46 +02: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.