diff options
author | Chloe Kudryavtsev <toast@toastin.space> | 2019-03-26 21:02:58 -0400 |
---|---|---|
committer | Chloe Kudryavtsev <toast@toastin.space> | 2019-03-26 21:02:58 -0400 |
commit | a27a8157b5d387d6f31df8df402dcea8703be5ef (patch) | |
tree | 001a3c9cebd15d639d6f766d13f07d123d575847 | |
parent | 13f6be2dca9ba84d58c77566b8dcf3e9bf40fb1a (diff) | |
download | governance-a27a8157b5d387d6f31df8df402dcea8703be5ef.tar.bz2 governance-a27a8157b5d387d6f31df8df402dcea8703be5ef.tar.xz |
[policy] Add project-wide voting as a fallback
-rw-r--r-- | modules/Policies/pages/voting.adoc | 28 |
1 files changed, 22 insertions, 6 deletions
diff --git a/modules/Policies/pages/voting.adoc b/modules/Policies/pages/voting.adoc index edff746..2516df7 100644 --- a/modules/Policies/pages/voting.adoc +++ b/modules/Policies/pages/voting.adoc @@ -4,21 +4,37 @@ When important changes to the project as a whole need to happen, it comes down t This policy describes how voting is done within Alpine. If a given action calls for a vote, it should link here. -== Initial Vote +== 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 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. +If someone objects, then the Base team takes over. -NOTE: Objecting to a failed motion should *ONLY* be done in extreme situations, you can always improve the proposal and try again later. +[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. +==== == 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. -Alternatively, if within the Base team, there is a simple majority, the motion also passes. -Otherwise, the motion fails. -If the motion does not pass at this stage, it cannot be revoted on without significant modifications. +If that is not the case, the Base team may choose to hold a project-wide vote (similarly to if it were requested directly). -NOTE: The Base team is allowed to choose to avoid voting for some period of time, in scenarios where there is a clear divide between the two sides of mostly equal size. +== 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. |