openstack/governance
Code Issues Proposed changes

Be specific about geography in release names

Browse Source 
The existing relase name criteria were intentionally vague about
geography to allow us to collect the largest amount of cool names
possible for voting.  Somehow, that did not end up happening and
instead a specific determination of region was used to drop about
2/3 of the otherwise-qualifying names from the M name poll after
nominations were closed.

In order to prevent this from happening again, we will need to
very specifically designate a region upon initiating the process.

Also, provide clear indication that the role of the election
official is not to make subjective determinations.

Also, allow for a time between finalizing the list of names and
the start of the election so that if the election official makes
any disputed decisions, there is an opportunity to address them
before the poll goes out.  This also clarifies when the TC should
add any exceptions to the process.

Finally, add an extra column to the election roster to indicate
where the geographic boundaries should be specified.

For more background, see:
http://lists.openstack.org/pipermail/openstack-dev/2015-June/066995.html

Change-Id: Ia9adc66090f2994bb291967f7f2e1b2b4dd14603
This commit is contained in:
James E. Blair 2015-06-15 13:52:02 -07:00
parent 0ebb6baab5
commit 284efe54fe
1 changed files with 23 additions and 6 deletions

29
reference/release-naming.rst

@ -41,6 +41,21 @@ following steps:
This information will be communicated during the election, but the
names will not be removed from the poll.
#. After the close of nominations, the election official will finalize
the list of proposed names and publicize it. In general, the
official should strive to make objective determinations as to
whether a name meets the `Release Name Criteria`_, but if
subjective evaluation is required, should be generous in
interpreting the rules. It is not necessary to reduce the list of
proposed names to a small number.
#. Once the list is finalized and publicized, a one-week period shall
elapse before the start of the election so that any names removed
from consideration because they did not meet the `Release Name
Criteria`_ may be discussed. Names erroneously removed may be
re-added during this period, and the Technical Committee may vote
to add exceptional names (which do not meet the standard criteria).
#. A Condorcet election is held among all OpenStack Foundation
Individual Members to rank the names. The poll will include the
names along with any links to mailing list discussions provided by
@ -71,7 +86,9 @@ being chosen.
#. The name must refer to the physical or human geography of the
region encompassing the location of the OpenStack design summit for
the corresponding release.
the corresponding release. The exact boundaries of the geographic
region under consideration must be declared before the opening of
nominations, as part of the initiation of the selection process.
#. The name must be a single word with a maximum of 10 characters.
Words that describe the feature should not be included, so "Foo
@ -87,8 +104,8 @@ opens.
Polls
-----
======= ============ ================ ========== ==========
Release Coordinator Nominations Open Poll Open Poll Close
======= ============ ================ ========== ==========
M Monty Taylor 2015-06-01 2015-06-08 2015-06-15
======= ============ ================ ========== ==========
======= ============ ================ ========== ========== =================
Release Coordinator Nominations Open Poll Open Poll Close Geographic Region
======= ============ ================ ========== ========== =================
M Monty Taylor 2015-06-01 2015-06-08 2015-06-15 N/A
======= ============ ================ ========== ========== =================