openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
3,291 Commits 1 Branch 18 Tags 40 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Chris Dent e783b307ea Add a house rule about how to signal appointed PTLs 
We've been dealing with how to make appointed PTLs official and
documented in a rather ad hoc fashion: something different each
cycle.

This change provides a house rule which puts the responsibility
and the documentation in the combined hands of the appointed PTL
and the TC that appointed them and not election handling (where
it doesn't make sense since no election happened).

Change-Id: Idf78e00c59d10528a2b4950f8baa93c6731973ea
 		2018-08-13 17:58:40 +01:00
doc Fix width of team badges svg 2018-06-20 18:26:29 -07:00
goals remove placeholder file from stein goals 2018-08-02 09:50:19 -04:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Add a house rule about how to signal appointed PTLs 2018-08-13 17:58:40 +01:00
resolutions Add a house rule about how to signal appointed PTLs 2018-08-13 17:58:40 +01:00
tools add soft validation of extra-atcs 2018-08-03 10:40:30 -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 move the team badge generation to the end of the build 2018-05-14 10:51:00 -04:00
tox.ini add soft validation of extra-atcs 2018-08-03 10:40:30 -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.