openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
2,164 Commits 1 Branch 18 Tags 41 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
Doug Hellmann 1c98c456b5 add flake8 to the linter job 
Turn on flake8 for code style checks, like in our other repos. Fix or
explicitly ignore various issues to allow the linter job to pass.

Change-Id: I7bfd8cf5e9c00dfa83c0393a4307fd54d2113047
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
 		2017-03-15 17:47:28 -04:00
doc/source add flake8 to the linter job 2017-03-15 17:47:28 -04:00
goals Merge "[goals/pike] Responses for the WSGI goals for stable" 2017-03-10 15:05:01 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Merge "Add os_molteniron to OpenStack-Ansible" 2017-03-15 11:06:05 +00:00
resolutions add flake8 to the linter job 2017-03-15 17:47:28 -04:00
tools add flake8 to the linter job 2017-03-15 17:47:28 -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
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 add flake8 to the linter job 2017-03-15 17:47:28 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt add flake8 to the linter job 2017-03-15 17:47:28 -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.