governance

Go to file

Jean-Philippe Evrard 6405a3fa4c Add new roles to OpenStack-Ansible

Two new roles have been asked by the community: a way to
deploy zun, and a way to use qpid dispatch router instead of
rabbitmq.

This patch includes both new roles, as we usually do:
They will be separate of the openstack-ansible main deliverable,
like other roles before it.

Depends-On: https://review.openstack.org/#/c/572551/
Change-Id: I5fb2f24d2eecd38de793a1e739e14614b488e01d

2018-06-05 22:26:19 +02:00

doc

Replace deprecated library function os.popen() with subprocess

2018-05-23 09:24:04 +07:00

goals

Merge "provide more detail about the expectations we place on goal champions"

2018-06-04 14:39:41 +00:00

pre-history

Add some pre-history meeting summaries

2013-11-11 09:08:57 -06:00

reference

Add new roles to OpenStack-Ansible

2018-06-05 22:26:19 +02:00

resolutions

Merge "Resolution for minimal SIG governance"

2018-03-27 08:49:01 +00: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

move the team badge generation to the end of the build

2018-05-14 10:51:00 -04:00

tox.ini

fix tox to allow building docs locally

2018-03-28 17:34:07 -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.