openstack/governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
978 Commits 1 Branch 19 Tags 42 MiB
Python 96.3%
DIGITAL Command Language 2.5%
Shell 1%
C++ 0.2%
9e9561ef5c
Go to file
Mark McClain 9e9561ef5c This change adds the Astara Neutron driver repo. 
The Astara Neutron repo contains the drivers and plugins necessary to
load into Neutron to interface with the Astara RPC API.  This repo is
being placed under Astara after considering the list conversation
regarding the Neutron Stadium [1].  Since our team will be handling
responsibility for release activities it made since to place it here.

[1] http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html

Change-Id: Ie4a99316e60ca382f8d6323720f92ffb6642b66c
2015-12-14 12:14:39 -05:00
doc/source change projects schema to support more ptl contact data 2015-10-13 20:05:21 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference This change adds the Astara Neutron driver repo. 2015-12-14 12:14:39 -05:00
resolutions stackforge retirement: make workflow reqs+cla clearer 2015-10-05 19:12:43 +09:00
tools Merge "Add a tool that allows visualizing the projects as a graph" 2015-11-20 11:03:31 +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
requirements.txt Add a tool that allows visualizing the projects as a graph 2015-11-10 13:13:48 -08: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 Add team:single-vendor tag 2015-11-12 18:12:37 +01: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.