voting.adoc 2.55 KB
Newer Older
1
= Voting Process
2

3 4 5 6
When important changes to the project as a whole need to happen, it comes down to a vote.
This policy describes how voting is done within Alpine.
If a given action calls for a vote, it should link here.

7 8 9 10 11 12 13 14 15
== Call for Vote
When an event that necessitates a vote occurs, one should call for a vote.
A team member may call for a vote by requesting it of either any team's admin (including theirs) or by requesting a special project-wide vote from the Base team.

TIP: If the person that wishes for a vote is an admin, they may implicitly receive and accept their own call.

NOTE: The base team may refuse to hold a project-wide vote, in which case they will organize an admin vote.

== Admin Vote
16 17 18 19 20
All xref:ROOT:teams.adoc[team administrators] vote.
The medium of the vote is undefined (for example, it may be done in a meeting, through a mailing list, or through irc, so long as it is logged publicly).
The voting process has a time limit of 2 weeks.
If a 2/3 majority is reached within the time limit, the motion passes.
If it is not, but no one objects, the motion fails.
21
If someone objects, then the Base team takes over.
22

23 24 25 26 27 28
[WARNING]
====
Objecting to a failed motion should *ONLY* be done in extreme situations.
Pushing a motion unto base at this stage would mean that, were it to fail again, it cannot be re-voted upon without a massive rework.
If you accept the failure at this stage, you may modify it slightly (as per the requests of the people against it) and bring it back up.
====
29

30 31
IMPORTANT: In the scenario where the topic of a vote is not a simple yes/no question, the vote shall be done in condorset style, in which various options are ranked by preference.

32 33 34 35
== Base Vote
If a significant objection is levered, the xref:ROOT:teams.adoc[Base team members] that are not admins also vote.
These votes are added to the existing tally.
If 2/3 majority has now been reached, the motion passes.
36
If that is not the case, the Base team may choose to hold a project-wide vote (similarly to if it were requested directly).
37

38 39 40 41 42
== Project-Wide Vote
If the base team accepts a request to hold a project-wide vote, or a regular vote escalates to the degree that it is necessary, this option comes into play.
In this scenario, a vote is held by the same rules as an <<_admin_vote>>, except that instead of only the team admins voting, any member of any team is allowed to cast a vote.
If that vote fails to meet a 2/3 majority (of the people that vote) within the time limit, the motion fails, end of discussion.
The motion may not be brought back up without significant modifications afterwards.