openstack/governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
806 Commits 1 Branch 19 Tags 42 MiB
Python 96.3%
DIGITAL Command Language 2.5%
Shell 1%
C++ 0.2%
c6e237eaf4
Go to file
Ben Kero c6e237eaf4 stackforge retirement: make workflow reqs+cla clearer 
There has been some concern voiced over the ambiguity of the language
used in this resolution. Concerns were brought up about whether new or
existing contributors will now need to sign a CLA or alter workflow. It
is my understanding that this is not the case.

To make this clear, I propose adding this unambiguous writing to the
resolution.

Change-Id: Iac0f87678479e694350cccfb9bb87ce3bb946ff6
2015-10-05 19:12:43 +09: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 Merge "Add puppet-infracloud module to Infra project" 2015-10-05 09:33:11 +00:00
resolutions stackforge retirement: make workflow reqs+cla clearer 2015-10-05 19:12:43 +09: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.