governance

Go to file

Monty Taylor d7e8bef560 Add os-service-types repo to shade project

We've recently defined how to consume both official service-types and
their historical aliases, and we're publishing a json document with the
historical mapping. The next step is a simple python library that
encapsulates consuming that data.

Depends-On: If63f602e1e8a4ce3867b99adef5a07c29aa44630
Change-Id: I7621760d16c282c8671580e4f7be17ee1699e511

2017-07-05 16:30:23 -05:00

doc/source

Follow-up precisions on office hours

2017-06-05 13:43:21 +02:00

goals

Remove placeholder file for Queens goals

2017-07-04 10:53:32 -07:00

pre-history

Add some pre-history meeting summaries

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

reference

Add os-service-types repo to shade project

2017-07-05 16:30:23 -05:00

resolutions

guidelines for managing releases of binary artifacts

2017-06-07 12:46:56 +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

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.