governance

Go to file

Russell Bryant 5c4ff20b3c Note that the TC expects some project history.

The recent application by the Kosmos project [1] prompted a discussion
on whether or not a project should apply to the TC right away or if it
should have some amount of history of operating as an OpenStack project
first.  The consensus on that application was that we should wait and
let the project get going first.

This patch updates the new projects requirements to clarify this point.
As noted by ttx on [1], this guideline will henceforth be known as
"the Kosmos jurisprudence".

[1] https://review.openstack.org/#/c/223674/

Change-Id: Ifc964d09ea2107e3ecd95f9579543bcb77f457d0
Signed-off-by: Russell Bryant <rbryant@redhat.com>

2015-09-30 11:10:30 -04:00

doc/source

Introduce the "deliverables" concept

2015-07-27 15:23:01 +02:00

pre-history

Add some pre-history meeting summaries

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

reference

Note that the TC expects some project history.

2015-09-30 11:10:30 -04:00

resolutions

OpenStack programming languages resolution

2015-09-14 13:49:05 +02:00

tools

Merge "teamstats: Add stats related to team size."

2015-08-12 12:07:41 +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

README.rst

provide infrastructure for publishing docs to html

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

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

Build list of teams from YAML file

2015-02-24 18:15:04 -05:00

tox.ini

Ensure that reference/projects.yaml is sorted

2015-07-29 21:02:12 +02: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.

See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.