openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
2,344 Commits 1 Branch 18 Tags 41 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Doug Hellmann 636a939002 cap sphinx below 1.6.1 
The new sphinx causes an issue with pbr. Cap the allowed range to
exclude the bad version.

Change-Id: Ia29abe93254e12443e4351d67e998908baf97086
Related-Bug: #1691129
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
 		2017-05-16 15:15:36 -04:00
doc/source Merge "Include instructions on how to propose changes" 2017-04-14 09:26:44 +00:00
goals Merge "Add kuryr pike goals information" 2017-05-04 13:46:41 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Merge "Create openstack-zuul-jobs / openstack-zuul-roles projects" 2017-05-15 10:09:15 +00:00
resolutions Resolution on OpenStack's mission for cloud applications 2017-04-07 10:22:18 -04:00
tools Merge "More gracefully handle intra-openstack moves" 2017-03-30 09:11:46 +00: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
README.rst propose approval policy for goal responses 2016-08-30 14:56:20 -04:00
requirements.txt Keep py3.X compatibility for urllib 2015-12-23 20:48:17 +05:30
setup.cfg update sphinx and treat warnings as errors 2017-03-15 17:47:34 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt cap sphinx below 1.6.1 2017-05-16 15:15:36 -04:00
tox.ini add flake8 to the linter job 2017-03-15 17:47:28 -04: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.