governance

Go to file

Lance Bragstad fb1ec6f451 Add ldappool to the keystone managed projects

The ldappool project was adopted by several memebers of the keystone
development team. This commit formally adds the project to the list
of keystone-managed openstack projects.

This will allow us to manage releases the same way we do with the
other libraries we manage.

Change-Id: Ic7b7b693dfb36ca29a8499e2bb3956145ec3c098

2017-05-25 19:31:35 +00:00

doc/source

Merge "Include instructions on how to propose changes"

2017-04-14 09:26:44 +00:00

goals

Merge "Change the target for this goal to uWSGI not Apache mod_wsgi"

2017-05-16 21:03:07 +00:00

pre-history

Add some pre-history meeting summaries

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

reference

Add ldappool to the keystone managed projects

2017-05-25 19:31:35 +00:00

resolutions

Resolution on OpenStack's mission for cloud applications

2017-04-07 10:22:18 -04:00

tools

Merge "More gracefully handle intra-openstack moves"

2017-03-30 09:11:46 +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 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

cap sphinx below 1.6.1

2017-05-16 15:15:36 -04:00

tox.ini

add flake8 to the linter job

2017-03-15 17:47:28 -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.