governance

Go to file

Doug Hellmann 8d38d82b41 show deliverables in the order listed in the projects file

Use an ordered dictionary loader to maintain the order items appear in
the projects file so we can produce them in the same order in the
output.

Change-Id: I96707f96056cc94a34cf9f4b9edfb73f42f7bb27
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

2018-01-11 16:32:35 -05:00

doc

show deliverables in the order listed in the projects file

2018-01-11 16:32:35 -05:00

goals

Merge "Mark the completion of tempest plugin split for Manila team"

2018-01-05 09:36:10 +00:00

pre-history

Add some pre-history meeting summaries

2013-11-11 09:08:57 -06:00

reference

Merge "grammar corrections"

2018-01-09 09:26:39 +00:00

resolutions

Fix typos in governance

2017-09-06 12:18:02 +00:00

tools

add a tool to get the PTL contact details easily

2017-06-22 09:39:00 -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

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

add redirect for renamed top-5-list file

2017-12-15 10:38:58 +01:00

tox.ini

add redirect for renamed top-5-list file

2017-12-15 10:38:58 +01: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.