| |
@@ -57,8 +57,11 @@
|
| |
|
| |
Once a ticket has a formal proposal offered, FESCo members have one week to either vote for or against it or else propose the ticket for the next weekly meeting agenda. At the end of that one week, if the proposal has gained at least three "for" votes and no "against" votes, it is approved. Any "against" votes mean that it goes onto the next meeting agenda, unless there are at least 7 negative votes and no positive ones, see below. If the week passes and the required number of votes have not been met, the proposal is extended by one further week and the minimum requirement becomes a single positive "for" vote. This is intended to ensure that proposals do not languish.
|
| |
|
| |
- There is also a shortcut procedure, which does not require waiting for the week to be up.
|
| |
+ There is also a fast-track procedure, which does not require waiting for the week to be up.
|
| |
Seven positive votes with no negative votes will immediately approve a proposal, and seven negative votes with no positive votes will immediately reject a proposal.
|
| |
+ The fast-track procedure must be specifically requested by the person submitting the proposal or a FESCo member and is only in effect when there's agreement from other members.
|
| |
+ Tagging the issue for the meeting agenda is understood to disqualify the proposal for fast-track status.
|
| |
+ Proposals that receive a unanimous vote are immediately considered approved or rejected as appropriate, independent of fast-track status.
|
| |
|
| |
== Meetings
|
| |
|
| |
bcotton
commented 3 years ago
DO NOTE MERGE UNTIL APPROVED BY FESCo
This prevents cases where 7 people vote in agreement quickly, but the remaining members have an objection or concern.