election_proposal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
election_proposal [2015/09/28 22:37] Dave Neary Formatting |
election_proposal [2015/09/29 15:00] Dave Neary Break proposals into individual chunks |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| > - 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. | > - 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. | ||
| - | ==== Proposed process ==== | + | ==== Proposed process changes ==== |
| + | |||
| + | === Proposal 1: "Active Technical Contributor" === | ||
| I propose adopting the following processes for member board elections: | I propose adopting the following processes for member board elections: | ||
| - | * "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): | + | * "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 | + | * Git commits |
| - | * Gerrit reviews | + | * Gerrit reviews |
| - | * Wiki page edits | + | * Wiki page edits |
| - | * Blueprints submitted to upstream projects | + | * Blueprints submitted to upstream projects |
| - | * OPNFV User Group co-ordination | + | * 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. | 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 | + | === Proposal 2: Community board seat election process === |
| - | * 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 | + | * 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 |
| - | * 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. | + | * Polls will be open for one week, and results will be sent to opnfv-tech-discuss afterwards |
| - | * 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 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. | 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. | ||
| + | |||
| + | === Proposal 3: Publication of full election results === | ||
| 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. | 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. | ||
| + | === Proposal 4: Process for TSC board chair elections === | ||
| I would also like to propose that the same rules apply for the election of the TSC chairman, with some modifications: | 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 | + | * Elections announced 3 weeks before polls close |
| - | * One week nomination period, with nominations sent to opnfv-tsc | + | * One week nomination period, with nominations sent to opnfv-tsc |
| - | * One week polling period | + | * One week polling period |
| - | * Results sent to opnfv-tsc | + | * Results sent to opnfv-tsc |
| + | |||
| + | === Proposal 5: Date restrictions for nomination periods === | ||
| - | 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. | + | I would like to propose 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 advance, to allow for people to indicate timing issues like this). July and August should be avoided for all OPNFV elections, due to the risk of disenfranchising voters on vacation. |
election_proposal.txt · Last modified: 2015/10/01 19:34 by Dave Neary
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
