Go to file
Thierry Carrez f019d697c6 Write down OpenStack principles
Beyond the Four Opens, the OpenStack community (and the Technical
Committee as its direct representation) operates on a lot of
unwritten principles, which were transmitted by oral tradition
by the elders and appear from time to time as a snippet of wisdom
in the middle of a TC meeting.

It is more than time for us to document those principles, to make
them clearer to everyone and harder to ignore. To give credit where
due, the bulk of this document was written by Monty Taylor, with
input from a number of other folks including (but not limited to)
the list of co-authors below.

Change-Id: I0134b0aa9b512ee61fbb908d23e7260ff2491bba
Co-Authored-By: Monty Taylor <mordred@inaugust.com>
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
Co-Authored-By: John Garbutt <john@johngarbutt.com>
2016-09-22 14:07:15 +02:00
2016-09-22 14:07:15 +02:00
2013-08-30 16:00:06 +00:00
2014-10-27 13:44:50 -04:00
2016-01-25 16:32:54 +01:00
2016-01-25 16:32:54 +01:00

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.

Description
OpenStack Technical Committee Decisions
Readme 44 MiB
Languages
Python 93.8%
DIGITAL Command Language 5.1%
Shell 0.9%
C++ 0.2%