Skip to content

Latest commit

 

History

History
106 lines (91 loc) · 5.5 KB

voting.md

File metadata and controls

106 lines (91 loc) · 5.5 KB
Raw

Voting Protocol

1. General Rules

  1. Only Class 1 and Class 2 members of Open Source Matters may initiate a call for votes on a measure.
  2. Votes can be +1 (“in favor”), -1 (“against”), or 0 (“abstain”).
  3. The quorum is met when the number of votes is greater than or equal to the specified fraction of the number of voting members. Example: Let the quorum be one-third.
    • If there are 20, 21, or 22 members, then 7 or more must vote within the time limit for the vote to be valid.
    • If there are 23, 24, or 25 members, then 8 or more must vote within the time limit for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor”, i.e., tne number of "in favor" votes is greater than the number of "against" votes. The measure does not pass otherwise.
  5. The RFC votes are not secret. Names and votes will be published in the Meta document of the RFC, independent from the outcome of the vote.

N.B.: “Abstain” votes are counted only for quorum, and are not counted when calculating majority.

2. Rejection Vote

  1. Production Department Team Leaders and the Production Department Coordinator may vote on Rejection measures for Features and Specifications.
  2. The Rejection vote is conducted in the Production Department lead by the Production Department Coordinator. There are no formal requirements beside the quorum and the majority.
  3. Half or more of the voting members must vote for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor” (i.e., the proposal is rejected). The measure does not pass otherwise (i.e., the proposal passes on to Entrance Vote).
  5. Responsibility for vote tallying is shared between the Production Department Coordinator and the Sponsor of the RFC, both of whom should confirm the result.

3. Entrance Vote

  1. All members of Open Source Matters (Class 1, 2 or 3) may vote on Entrance measures.
  2. The time limit on a Entrance vote is 14 days from the time of the call for votes, or until all voting members have cast their vote, whichever comes first. Votes cast after the time limit are not valid.
  3. One-third or more of the voting members must vote within the time limit for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor”. The measure does not pass otherwise.
  5. Responsibility for vote tallying is shared between the member who starts a vote and the sponsors of the measure, both of whom should confirm the result.

4. Readiness Vote

  1. All members of the Working Group for that specific RFC may vote on Readiness measures.
  2. The Readiness vote is conducted in the Workgroup lead by the Sponsor. There are no formal requirements beside the quorum and the majority.
  3. Half or more of the voting members must vote for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor”. The measure does not pass otherwise.
  5. Responsibility for vote tallying is shared between the Editor and the Sponsor of the RFC, both of whom should confirm the result.

5. Acceptance Vote

  1. Only Team Leaders in the Production Department and the Production Department Coordinator may vote on Acceptance measures for Features, Specifications and purely technical Processes.
  2. Team Leaders in any Department and their Department Coordinator may vote on Acceptance measures for Processes that are not purely technical.
  3. The time limit on a vote is 7 days from the time of the call for votes for an Acceptance vote, or until all voting members have cast their vote, whichever comes first. Votes cast after the time limit are not valid.
  4. One-third or more of the voting members must vote within the time limit for the vote to be valid.
  5. The measure passes if a simple majority of the votes cast are “in favor”. The measure does not pass otherwise.
  6. Responsibility for vote tallying is shared between the member who starts a vote and the sponsors of the measure, both of whom should confirm the result.

6. Deprecation Vote

  1. All members of Open Source Matters (Class 1, 2 or 3) may vote on Deprecation measures.
  2. The time limit on a Deprecation vote is 7 days from the time of the call for votes, or until all voting members have cast their vote, whichever comes first. Votes cast after the time limit are not valid.
  3. One-third or more of the voting members must vote within the time limit for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor”. The measure does not pass otherwise.
  5. Responsibility for vote tallying is shared between the member who starts a vote and the sponsors of the measure, both of whom should confirm the result.

7. Abandonment Vote

  1. All members of Open Source Matters (Class 1, 2 or 3) may vote on Abandonment measures.
  2. The time limit on an Abandonment vote is 7 days from the time of the call for votes, or until all voting members have cast their vote, whichever comes first. Votes cast after the time limit are not valid.
  3. Half or more of the voting members must vote within the time limit for the vote to be valid.
  4. The measure passes if a simple majority of the votes cast are “in favor”. The measure does not pass otherwise.
  5. Responsibility for vote tallying is shared between the member who starts a vote and the sponsors of the measure, both of whom should confirm the result.