openstack/governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
3,450 Commits 1 Branch 19 Tags 42 MiB
Python 96.3%
DIGITAL Command Language 2.5%
Shell 1%
C++ 0.2%
d2bec92094
Go to file
Zane Bitter d2bec92094 Clarify wording of Python update resolution 
The previous wording introduced unneccesary confusion about when the
goal would be set. Clarify that the goal is set at the beginning of a
release cycle as usual, and should be completed by the end of the
release cycle.

Also, avoid using the word 'support' to refer to which versions of
Python we run unit tests on.

Change-Id: I461ba0c0d4bc1e3d7e2b71ab614003733afdd4ea
2018-12-06 14:33:00 +13:00
doc Update sphinx extension logging 2018-10-16 21:35:30 -05:00
goals Follow publish-to-pypi change 2018-11-05 10:01:51 +01:00
openstack_governance add a script to randomly assign TC members as liaisons 2018-10-09 15:55:24 -04:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Resolution on keeping up with Python 3 releases 2018-11-08 19:03:00 -05:00
resolutions Clarify wording of Python update resolution 2018-12-06 14:33:00 +13:00
tools report the number of votes needed 2018-10-29 14:48:53 -04: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
.zuul.yaml Use tox-docs for building 2018-10-07 10:31:46 +02:00
README.rst propose approval policy for goal responses 2016-08-30 14:56:20 -04:00
requirements.txt add a script to randomly assign TC members as liaisons 2018-10-09 15:55:24 -04:00
setup.cfg move members file parsing into a reusable module 2018-10-08 19:16:34 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt Inherit openstackdocstheme for TC site 2018-09-28 13:03:26 +02:00
tox.ini add pep8 to tox.ini 2018-10-31 13:36:03 -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.