openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
3,082 Commits 1 Branch 18 Tags 41 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Tony Breeds db4c60e425 Rename and clarify PowerStackers 
This change renames PowerStackers and clarifies mission statement added
in I1b709623df535b662871e9db2bac59b6f55f5277

The project team name and the mission are in disagreement in that the
name and mission cover all POWER CPU implementations but it's clear from
the make up of the group that it refers only to the PowerVM hypervisor.

Change-Id: I95f76f90fa65d0f54fed69b75cb575575976b33e
 		2018-03-10 11:33:53 +11:00
doc Rename goals/template.txt to .rst 2018-02-07 19:56:43 +00:00
goals Merge "Fix the invalid url in page" 2018-03-09 09:14:59 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Rename and clarify PowerStackers 2018-03-10 11:33:53 +11:00
resolutions Add resolution about CI for external projects 2018-02-15 13:06:54 -08:00
tools update goal process to use storyboard for tracking 2018-02-13 10:41:01 +01: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 add redirect for renamed top-5-list file 2017-12-15 10:38:58 +01:00
tox.ini add redirect for renamed top-5-list file 2017-12-15 10:38:58 +01: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.