Hi,
Stephen Gallagher proposed a change to FESCo voting rules [1].
The latest draft:
----------&<---------------------------------------------------------
Ticket Votes (Preferred)
Once a formal proposal is made in a ticket, voting will proceed. A
Change ticket is assumed to be a a formal proposal upon creation.
An official vote in a ticket must be one of +1, -1 as defined herein:
+1 — I am in favor of the proposal as currently written.
0 — I am electing to remove myself from the list of eligible
voters. This has no effect unless the ticket votes are used for a
meeting vote.
-1 — I am opposed to the proposal as currently written. This topic
must be discussed live in a meeting.
At the end of one week, if a ticket has at least 3 votes of +1 and no
votes of -1, it is approved and may proceed with implementation. If
there is at least one -1 vote, the ticket must be added to the
upcoming meeting agenda and subject to the Meeting Votes rules.
If there are insufficient +1 votes at the end of one week, one
additional week will be granted. At the end of this period, if there
is at least one +1 vote and no votes of -1, the proposal is
approved. If there is at least one -1 vote, the ticket must be added
to the upcoming meeting agenda and subject to the Meeting Votes
rules. If there are no votes at all, the proposal is considered
rejected and the status quo will be maintained. The submitter may at
this time make a new proposal which will restart this process.
Meeting votes
At the meeting, a reasonable amount of time must be given for
discussion. Once a proposal is made in the chat, the vote will be
tallied as follows:
A proposal must achieve a majority (at least 51%) of +1 votes from
eligible voters. Votes must be one of +1, 0 or -1 as defined herein:
+1 I am in favor of the proposal as currently written.
0 I am electing to remove myself from the list of eligible
voters. This reduces the denominator of the fraction required to
achieve the 51% majority. In effect, I am agreeing to vote with
the remaining majority, whatever they decide.
-1 I am opposed to the proposal as currently written.
Any eligible voter that cannot attend the meeting is assumed to retain
any vote that they have made in the ticket prior to the meeting. Note
that this does not apply to new proposals made in the meeting, with
the exception of simple clarification edits.
If a vote in the meeting achieves a 51% majority in favor of a
proposal (accounting for any explicit 0 votes), that proposal is
accepted.
If a vote in the meeting achieves a 51% majority against a proposal
(accounting for any explicit 0 votes), that proposal is rejected.
If a proposal in a meeting fails to achieve a majority either for or
against, the FESCo members present must either:
Present a new proposal, restarting the meeting voting process.
Return the proposal to the ticket, restarting the ticket voting
process above. All votes made in the meeting will be transferred
to the ticket (Note: negative votes recorded in this way do
trigger discussion at the next meeting as normal). Once FESCo
agrees to return the proposal to the ticket, all discussion in the
current meeting on the topic is ended until that ticket vote has
concluded with either a decision or is transferred to another
meeting.
---------->&---------------------------------------------------------
Please comment here or in the ticket.
[1] https://pagure.io/fesco/issue/3038
Zbyszek, on half of FESCo
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
