Skip to content

Commit a2fac3f

Browse files
committed
Update voting-majority: min 2 non-proposer votes; no emails
1 parent f0c5bba commit a2fac3f

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

rfcs/0000-voting-majority.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ This RFC proposes updating our voting guidelines to make it easier for
55
uncontroversial proposals to be accepted as the number of members in
66
the working group grows. Specifically, the number of approving votes
77
required will remain 50% of the members for one week, then be decreased
8-
to 33% for two weeks, and then if no concerns are raised any number of
9-
approvals will accept the proposal.
8+
to 33% for two weeks, and then if no concerns only two approvals by members
9+
other than the proposer are required for acceptance.
1010

1111
Considerations are also made for notifying working group members of
1212
outstanding voting issues.
@@ -43,31 +43,32 @@ After one week has passed, the threshold is reduced to 33%, and remains at 33%
4343
for two weeks. There must still be zero unresolved concerns; but only 33% of
4444
the members need to approve for a proposal to be accepted.
4545

46-
After those two weeks have passed (three weeks in total), _any_ number of
47-
approvals will permit a vote to be accepted, so long as there are no unresolved
48-
concerns. A member is explicitly permitted to raise a concern that there are
49-
not sufficient approvals or an issue has not received sufficient attention and
50-
thereby block it from being accepted until that concern is addressed. An
51-
exception is made if the only approval is from the proposer, in which case
52-
one further approval will be required.
46+
After those two weeks have passed (three weeks in total), two approvals from
47+
members who are not the propser will permit a vote to be accepted, so long as
48+
there are no unresolved concerns. A member is explicitly permitted to raise a
49+
concern that there are not sufficient approvals or an issue has not received
50+
sufficient attention and thereby block it from being accepted until that
51+
concern is addressed.
5352

5453
## Notifying Members
5554

5655
At each weekly meeting, outstanding votes will be identified, and members
57-
present at the meeting reminded to consider voting. After each meeting,
58-
all members of the relevant group will be emailed with a reminder of any
59-
pending votes.
56+
present at the meeting reminded to consider voting. It is the responsibiltiy
57+
of the proposer to ensure the vote is listed on a meeting's agenda. Weeks
58+
where a vote is not listed on a meeting's agenda will not count towards
59+
reducing the required voting threshold.
6060

61-
By notifying members of outstanding votes each week, it is hoped that every
62-
member will have sufficient time to consider whether they have concerns over
63-
a specific vote. If the full three weeks elapses with no concerns raised,
64-
we conclude no members have concerns.
61+
By notifying members of outstanding votes at the weekly meetings, it is hoped
62+
that every member will have sufficient time to consider whether they have
63+
concerns over a specific vote. If the full three weeks elapses with no concerns
64+
raised, we conclude no members have concerns.
6565

6666
## Self Voting
6767

6868
We clarify that members may approve their own proposals in order to help reach
6969
the required majority, but such votes will not be sufficient alone to accept a
70-
proposal.
70+
proposal, and at least two approvals by members other than the proposer will
71+
always be required to accept a proposal.
7172

7273
# Alternatives
7374

0 commit comments

Comments
 (0)