openstack
/
governance
Code Issues Proposed changes

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>
This commit is contained in:
Thierry Carrez 2017-05-22 12:22:58 +02:00 committed by Flavio Percoco
parent 56c5604974
commit e3a07c82d6
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
reference/index.rst
View File

@ -11,6 +11,7 @@ Reference documents which need to be revised over time.
principles
charter
projects/index
top-5-help-wanted
new-projects-requirements
new-language-requirements
licensing

24
reference/top-5-help-wanted.rst Normal file
View File

@ -0,0 +1,24 @@
========================
Top 5 help wanted list
========================
This document lists areas where the OpenStack Technical Committee seeks
contributions to significantly help OpenStack as a whole. While in most
cases things happen naturally through the normal contribution dynamics
in the community, in some cases a `tragedy of the commons`_ is at play.
Guidance, leadership and proper recognition of efforts is therefore needed
to encourage individuals or organizations to contribute in areas where they
could make a big impact.
Each item should clearly explain why the item matters (value of the effort
to the community, operators and users), why we need help there (description
of the current situation) and what experience or benefit the volunteer can
expect to gain from tackling it. It should also include the name of a TC
sponsor (responsible for evangelizing, articulating and channelling the work,
but also facilitating connections between candidates and target teams). For
an estimate of the commitment required, interested candidates should reach
out to the TC sponsor, or the PTL of the affected project.
.. _`tragedy of the commons`: https://en.wikipedia.org/wiki/Tragedy_of_the_commons
(insert items here)