OpenStack Technical Committee Decisions
Go to file
Thierry Carrez e3a07c82d6 Introduce Top 5 help wanted list
A lot of people, especially contributors and organizations that are new
to OpenStack, are seeking guidance on how to make useful, strategic
contributions to OpenStack. While some of those strategic priorities are
long-standing and well-known, in the absence of a formal list blessed by
the Technical Committee a lot of contributors are turning to
Stackalytics to guess what a useful contribution is. Beyond wasted
resources and being annoying to core reviewers, this results in a
failure to drive those new contributors to what could be extremely
useful contributions, and prevents them to step up in the community.

In order to address that, this change establishes a "top 5" list of
areas where help is wanted. At this stage we'll leave it up to
Foundation staff to promote (through keynotes, web pages and blog
articles) the contributors and organizations who step up to help in
those areas. This list will send a clear signal to folks who are looking
at things like Stackalytics and tell them where exactly their effort is
valuable for the community as a whole. Folks on the Technical Committee
will help guide the work, monitor progress and report back to the wider
audience.

Change-Id: I91a24de4f812319d45709e7c65210c6bc49b3213
Co-Authored-By: Davanum Srinivas <davanum@gmail.com>
2017-06-19 11:59:01 +02:00
doc/source Follow-up precisions on office hours 2017-06-05 13:43:21 +02:00
goals Merge "WSGI goal for cloudkitty" 2017-06-16 08:23:13 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Introduce Top 5 help wanted list 2017-06-19 11:59:01 +02: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.