openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
3,218 Commits 1 Branch 18 Tags 41 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Eric Fried 4243c70cfe Fix doc output path in PTI reference 
The PTI reference implies that the docs build job will output rendered
documents to doc/build when it is in fact doc/build/html.  Fix up the
doc accordingly to avoid confusing the next guy as I myself was
confused.

Change-Id: I7c3e189cb29164c4934e809e5a64e938307fb320
 		2018-06-27 17:22:05 -05:00
doc Fix width of team badges svg 2018-06-20 18:26:29 -07:00
goals add champion section to goal template 2018-06-16 17:26:19 -04:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Fix doc output path in PTI reference 2018-06-27 17:22:05 -05:00
resolutions Merge "add python 2 deprecation timeline" 2018-06-12 18:46:29 +00:00
tools update goal process to use storyboard for tracking 2018-02-13 10:41:01 +01: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 show deliverables in the order listed in the projects file 2018-01-11 16:32:35 -05:00
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 move the team badge generation to the end of the build 2018-05-14 10:51:00 -04:00
tox.ini fix tox python3 overrides 2018-06-09 01:17:31 +08: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.