Jump to: navigation, search

Difference between revisions of "Security/OSSG Lead Election Spring 2015"

(Election system)
(Timeline)
Line 11: Line 11:
 
=== Timeline ===
 
=== Timeline ===
 
TODO: Agree DATES
 
TODO: Agree DATES
* October 2nd-19th: Open candidacy to OSSG lead position
+
* April x-y: Open candidacy to Security PTL position
* October 20th-26th: Elections
+
* April y-z: Elections
* October / November: Leadership transition period
+
* May i-n: Leadership transition period
  
 
=== Elected positions ===
 
=== Elected positions ===

Revision as of 17:22, 16 April 2015

Officials

The role of officials is to administer the election process. To ensure that all candidates who announce themselves are eligible as per the criteria below and to generally oversee and improve the election process. Anyone can volunteer to be an official so long as they meet the same requirements as candidates, listed below.

TODO: People

Election system

TODO: Verify

Elections will be held using CIVS and a Condorcet algorithm (Schulze/Beatpath/CSSD variant). Any tie will be broken using Governance/TieBreaking.

Timeline

TODO: Agree DATES

  • April x-y: Open candidacy to Security PTL position
  • April y-z: Elections
  • May i-n: Leadership transition period

Elected positions

This election is for a person to lead the Security project. The term for this position will begin at the Liberty Summit in Vancouver (May 2015) and end at the 'M' Summit in Tokyo (Fall 2015). The elected leader will be responsible for holding a new election to fill the OSSG Lead position for the following term. There are no term limits (an individual may be re-elected as many times as the community chooses).

Electorate

The electorate for this election are members of the Security Launchpad group (https://launchpad.net/~openstack-ossg) who have played an "active role" in the Security community in the last 12 months.

  • Write or review an OSSN
  • Write or review the OpenStack Security Guide
  • Participate in security code reviews
  • Submit or review confirmed vulnerabilities
  • Write security enhancing code for OpenStack (SecImpact)
  • Attend an Security mid cycle meetup
  • Other contributing activities as defined at the discretion of the election officials

Candidates

TODO: Make this inline with other projects Any member of the election electorate (as defined above) can propose his/her candidacy for the same election. No nomination is required. They do so by sending an email to the openstack-security@lists.openstack.org mailing-list, using the subject: "Security PTL Candidacy". The email may include a description of the candidate platform. The candidacy is then confirmed by one of the election officials, after verification of the electorate status of the candidate.

Confirmed Candidates for Spring 2015 Security PTL Elections:

Results

  • TBD