openstack/governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
2,178 Commits 1 Branch 19 Tags 42 MiB
Python 96.3%
DIGITAL Command Language 2.5%
Shell 1%
C++ 0.2%
fd9d47a0ef
Go to file
Davanum Srinivas fd9d47a0ef Move castellan under Oslo governance 
The Barbican team would like to move Castellan under Oslo. The hope is
to send a clear signal to everyone that castellan is the preferred
library for their key manager needs and sufficiently abstracts hard
dependency to barbican and attract new folks with alternate implementations.

http://lists.openstack.org/pipermail/openstack-dev/2017-March/114335.html
http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-03-20-20.00.txt

Change-Id: I571dc981a198fcde1a8bdf626ce159b860d452aa
2017-03-23 09:18:14 -04:00
doc/source Merge "Replaces yaml.load() with yaml.safe_load() for governance" 2017-03-15 11:02:27 +00:00
goals Merge "Sahara Artifacts to deploy through WSGI" 2017-03-21 13:02:45 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Move castellan under Oslo governance 2017-03-23 09:18:14 -04:00
resolutions Reference doc for new language additions 2017-01-04 10:47:50 +01:00
tools Replaces yaml.load() with yaml.safe_load() for governance 2017-03-10 01:05:29 +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
.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 Keep py3.X compatibility for urllib 2015-12-23 20:48:17 +05:30
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 import theme locally 2017-02-14 17:27:12 -05:00
tox.ini Reduce the scope of yamllints coverage 2016-10-18 14:09:41 +11: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.