Differences

This shows you the differences between two versions of the page.

--- election_proposal [2015/09/28 22:35]
Dave Neary Propose election process modifications for committer election and TSC chair election
+++ election_proposal [2015/10/01 19:13]
Dave Neary
@@ Line 23: / Line 23: @@
   * Concerns about TSC being made up of nominees of Platinum sponsors, instead of active technical contributors to the project
-==== Current by-laws and election process ====
+===== Proposed process =====
-The election-related sections of the by-laws are as follows (extract from [[https://www.opnfv.org/about/bylaws-and-policies/bylaws|complete by-laws]]):
+==== Proposal 1: "Active Technical Contributor" ====
-> Section 2.7    Privileges of Individual Committer Membership
+I propose adopting the following processes for member board elections:
->
-> Each Individual Committer Member, while in good standing as a Committer on a project (as such requirements for such Committer role shall be established by the Technical Steering Committee from time to time), shall be entitled to:
->   -  run for election as a Director and participate in the election of Directors in accordance with Section 4.3(e) of these By-laws;
-> Section 4.3    Nomination, Election and Term of Office of Directors
+  * "Individual committer member" to be modified to "Active Technical Contributor", a status to be defined by the board and the TSC, based on active contributions to the project, including (but not limited to):
-> ...
+    * Git commits
-> -  Following the first release of the Platform, each Individual Committer Member (while remaining in good standing) shall have the right to vote, together with the other Individual Committer Members as a class, to elect one (1) Individual Committer Member to serve as a Director (the “Individual Director”), to serve until the next annual action of Members without a meeting and until his or her successor is elected and qualified or until his or her earlier resignation or removal.  The selection of nominees for such position shall be made by the Individual Committer Members (as project committers) and approved by the Board through such nominating procedures as may be set by the Board from time to time.
+    * Gerrit reviews
+    * Wiki page edits
+    * Blueprints submitted to upstream projects
+    * OPNFV User Group co-ordination
-> -  Any Director nominated, appointed or elected by any class of Members or the Technical Steering Committee, or by any Member, may, but shall not automatically, be re-nominated, re-appointed and/or re-elected for additional terms.
+The logic behind this is that OPNFV is a "mid-stream" project - many of the most beneficial activities in our community are not source code related (or, at least, not in the OPNFV project), so this is the wrong metric to use. We will soon have community metrics we can use to measure participation in other areas, and we should use these to define voting rights.
-> Section 5.5    Committees of the Members
+==== Proposal 2: Community election process ====
-> -  A Technical Steering Committee of the OPNFV shall be established consisting of (i) a project lead from each top level project, (ii) a representative designated by each of the Platinum Members, subject to Section 2.4(c); (iii) a representative designated by each of the Platinum Strategic End-User Members, subject to Section 2.4(c); and (iv) such number of individuals to be elected by the active committers as may be specified and under such procedures as may from time to time be approved by the Board.  The operation of the Technical Steering Committee shall be governed by the rules of process of such Committee as from time to time approved by the Board.
+=== Publication of election results ===
-==== Proposed process ====
+For all OPNFV community elections full (anonymized) results are published to allow independent verification of the results.
-I propose adopting the following processes for member board elections:
+=== Community board member election ===
-* "Individual committer member" to be modified to "Active Technical Contributor", a status to be defined by the board and the TSC, based on active contributions to the project, including (but not limited to):
+  *Elections are announced on the 1st of September, or the date of the first TSC meeting after September 1st, on the opnfv-tech-discuss mailing list.
-** Git commits
+    * At this time the list of eligible voters, who are also eligible to be candidates, will be published to the OPNFV web-site allowing one week for errors and omissions to be corrected.
-** Gerrit reviews
+  *The nomination period will begin one week after announcing the election and will continue for one week, until 14 days after the election announcement.  Nominations of candidates can be made either as self-nominations, or by any candidate on their behalf although the nomination must be accepted by the nominee to be valid.
-** Wiki page edits
+  * The list of valid nominees will be announced on opnfv-tech-discuss at the end of the nomination period and posted to the community wiki.  One week will be allowed for community debate and discussion.
-** Blueprints submitted to upstream projects
+  * Polls will be open for one week, from the 21st day after announcing the election until the 28th day at which point results will be sent to opnfv-tech-discuss and posted on the wiki.
-** OPNFV User Group co-ordination
-The logic behind this is that OPNFV is a "mid-stream" project - many of the most beneficial activities in our community are not source code related (or, at least, not in the OPNFV project), so this is the wrong metric to use. We will soon have community metrics we can use to measure participation in other areas, and we should use these to define voting rights.
-* Elections for the community board seat should be held annually, in the month of September, and must be announced one month in advance of the close of the election date (the month of September is arbitrary, added because the 1st election was in September) on the opnfv-tech-discuss mailing list
-** Polls will be open for one week, and results will be sent to opnfv-tech-discuss afterwards
-** The candidate list will be announced on opnfv-tech-discuss 14 days before the close of the election, to allow one week for community debate and discussion
-** The nomination period will open 21 days before the election closes, and will last for one week. Nominations should be sent to opnfv-tech-discuss with a nomination statement. Nominations can be made by any active technical contributor, but must be accepted by the nominee to be valid.
-** The list of eligible voters (who are also the list of people eligible to be candidates) will be published to the OPNFV web-site when the elections are announced, one month before the close of the election, to allow one week for errors and omissions to be corrected.
-The purpose of these proposals is to ensure that the community members are aware of an election, have an opportunity to check the voter roster, and are aware of candidates who have already nominated themselves, before nominating themselves to run. One month before the election will give ample time to debate the issues of the day.
+=== Community TSC member election ===
-As a separate proposal, I would like to propose that for the community board seat, that full (anonymized) results are published to allow independent verification of the results. This is standard in most community project elections.
+(this is according to current bylaws and aligned with the proposed process, assuming we would aim at the same election cadence even if we don't start there.)
+  *Elections are announced on the 1st of September, or the date of the first TSC meeting after September 1st, on the opnfv-tech-discuss mailing list.
+    * At this time the list of eligible voters, who are also eligible to be candidates, will be published to the OPNFV web-site allowing one week for errors and omissions to be corrected.
+  *The nomination period will begin one week after announcing the election and will continue for one week, until 14 days after the election announcement.  Nominations of candidates can be made either as self-nominations, or by any candidate on their behalf although the nomination must be accepted by the nominee to be valid.
+  * The list of valid nominees will be announced on opnfv-tech-discuss at the end of the nomination period and posted to the community wiki.  One week will be allowed for community debate and discussion.
+  * Polls will be open for one week, from the 21st day after announcing the election until the 28th day at which point results will be sent to opnfv-tech-discuss and posted on the wiki.
-I would also like to propose that the same rules apply for the election of the TSC chairman, with some modifications:
-* Elections announced 3 weeks before polls close
-* One week nomination period, with nominations sent to opnfv-tsc
-* One week polling period
-* Results sent to opnfv-tsc
-Also, I would like to suggest that when choosing dates for the TSC elections, that we avoid major European, North American and Chinese holidays (another reason to announce the elections in advancem to allow for people to indicate timing issues like this). And I would like to suggest avoiding July and August for all OPNFV elections, due to the risk of disenfranchising voters on vacation.
+=== TSC Chairperson election ===
+  *Elections are announced on the 7th of September, or the date of the first TSC meeting after September 7th, on the opnfv-tech-discuss mailing list.
+  *The nomination period will begin one week after announcing the election and will continue for one week, until 14 days after the election announcement.  The nomination process for the TSC chairperson is by self-nomination.
+  * Polls will be open for one week, from the 14th day after announcing the election until the 21st day at which point results will be sent to opnfv-tech-discuss and posted on the wiki.

Wiki

User Tools

Site Tools

Differences

Page Tools