governance

Go to file

Terry Wilson 6835570ab7 Add ovsdbapp project

The ovsdb api code from Neutron is used in at least 4 other projects,
so it makes sense to move it into its own project. neutron_lib isn't a
good fit because this code depends on Python code from the OVS project
and users of neutron_lib shouldn't be forced to install OVS.

Change-Id: Idf3dcca7e94fad49725fa427fbf874c674fdfd6a
Depends-On: Icd9be59f8c4e41801e30734d332c572e08680087

2017-02-27 17:05:05 +00:00

doc/source

Merge "import theme locally"

2017-02-24 19:07:30 +00:00

goals

fix markup in wsgi goal for pike

2017-02-14 17:27:12 -05:00

pre-history

Add some pre-history meeting summaries

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

reference

Add ovsdbapp project

2017-02-27 17:05:05 +00:00

resolutions

Reference doc for new language additions

2017-01-04 10:47:50 +01:00

tools

Calculate independent reviewers as independent companies

2017-01-19 01:28:14 +02: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 doc build requirements

2014-10-27 13:44:50 -04:00

setup.py

provide infrastructure for publishing docs to html

2014-01-07 15:29:11 -05:00

test-requirements.txt

import theme locally

2017-02-14 17:27:12 -05:00

tox.ini

Reduce the scope of yamllints coverage

2016-10-18 14:09:41 +11: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.