Skip to content

Commit eb3517d

Browse files
beckermrbeckermr
committed
STY formatting changes
1 parent 83381c8 commit eb3517d

File tree

1 file changed

+81
-64
lines changed

1 file changed

+81
-64
lines changed

‎src/orga/governance.rst

Lines changed: 81 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ Here are defined the primary teams participating in conda-forge activities.
3535
dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core
3636
developers. Any core member can also request to become emeritus if they wish to do so
3737
(e.g. taking a sabbatical or long vacation).
38-
Emeritus core members can still vote and move back to active core anytime. Emeritus
39-
votes are used to count towards quorum but the quorum size is computed from the size of
40-
the active core group. The ``core.csv`` list should be updated when a change in the status
38+
Emeritus core members can still vote and move back to active core anytime. Emeritus
39+
votes are used to count towards quorum but the quorum size is computed from the size of
40+
the active core group. The ``core.csv`` list should be updated when a change in the status
4141
of a member occurs.
4242

4343
Sub-Teams
@@ -86,9 +86,9 @@ Standard items are ones where public record and discourse is
8686
preferable. Sensitive voting items are ones where the results of the
8787
vote should remain private to the voters after the vote has occurred.
8888
Sensitive votes should take place on a secure anonymous voting platform
89-
in order to retain election integrity and anonymity. (We have used `Polys <polys.me>`_
90-
and `the Helios voting system <https://vote.heliosvoting.org/>`_, but are
91-
open to any secure, anonymous system.) The email capability of your chosen
89+
in order to retain election integrity and anonymity. (We have used `Polys <polys.me>`_
90+
and `the Helios voting system <https://vote.heliosvoting.org/>`_, but are
91+
open to any secure, anonymous system.) The email capability of your chosen
9292
voting platform should be used for sending voting invitations and reminders,
9393
and you should use the email list from
9494
https://github.com/conda-forge/conda-forge.github.io/blob/master/src/core.csv as
@@ -111,72 +111,89 @@ To call for a standard vote, here is a template PR comment:
111111
This vote will end on {date}.
112112
113113
----
114-
:Posting results: To maintain the historical record, the outcome of any standard vote which invokes the
115-
"time out" rules below should be recorded in the "vote-results" folder at
114+
115+
:Posting results: To maintain the historical record, the outcome of any standard vote which invokes the
116+
"time out" rules below should be recorded in the "vote-results" folder at
116117
https://github.com/conda-forge/conda-forge.github.io/tree/master/src/vote-results
117-
118-
Each vote should be its own file. The filename should reflect the topic and the
118+
119+
Each vote should be its own file. The filename should reflect the topic and the
119120
date that the vote opened. The file should contain at least:
120-
121+
121122
* vote description
122123
* vote policy
123124
* vote totals
124125
* poll open and close dates
125-
* notifications given to the core group
126+
* notifications given to the core group
126127

127128
----
128-
:Quorum: Quorum for votes can be met in one of three ways depending on the vote: the standard quorum rules,
129-
the accelerated quorum rules, and the "time out" quorum rules. The specific quorum rules applicable
130-
for each vote are listed below.
131-
132-
**Standard Quorum Rules**: All percentages below express *both* required participation, as a
133-
fraction of the active core team, as well as the fraction of that
134-
fraction who vote affirmatively on the issue. For example, in a vote
135-
requiring 50%, with 18 active core members, at least 9 must vote;
136-
if 9 vote, there must 5 affirmative votes. If 13 members vote, 7
137-
must be affirmative.
138-
139-
**Accelerated Quorum Rules**: For certain votes, we allow a lower quorum level. For these votes,
140-
if the vote ends after at least a week and there are no "no" votes, a quorum of half of the size
141-
needed for a **standard quorum** above is accepatble. For example, for a vote requiring 50% with 18
142-
active core members, at least 5 people must vote "yes" and exactly 0 people must vote "no".
143-
144-
**Time-out Quorum Rules**: Because everyone is busy and it is difficult sometimes to get quorum,
145-
votes not achieving quorum will eventually time out on their set end date. When this happens,
146-
the current participation level is taken for what it is, and the percentage
147-
of affirmative votes is calculated from whatever the vote total is at that
148-
time. In order for a timeout to occur, the vote must have:
149-
150-
* been open for at least 2 weeks
151-
* been presented and discussed at a Core team meeting
152-
* been advertised on at least 3 separate occasions on the gitter core
153-
channel (beginning of voting period, middle, and one day prior to
154-
proposed timeout)
155-
* been sent to core members via email. Email reminders must have been
156-
sent similarly to the gitter core channel: at least 3 times,
157-
occurring as beginning of voting period, middle, and one day
158-
prior to proposed timeout.
159-
160-
Extending the above example, if 9 people are required for a quorum, but
161-
only 7 have voted, those 7 votes can form the basis of a completed vote
162-
after the above conditions are met. 4 votes within those 7 would be
163-
needed to pass the vote.
164-
165-
To post a timeout reminder, here is a template comment:
166-
167-
.. code-block:: md
168-
169-
@conda-forge/core
170-
This vote falls under the {policy} policy, please vote and/or comment on this PR.
171-
This vote needs {policy_percent} of core to vote yea to pass.
172-
This vote presently has {current_voters}, and needs {policy_percent * core - current_voters} more for quorum.
173-
It is proposed that this vote will time out and be evaluated with the current votes in {days}, on {date}.
174-
To vote please leave Approve (yea) or Request Changes (nay) reviews.
175-
176-
To declare a standard vote "timed out," the person making such a declaration must post a pull-request adding
177-
a vote record to the https://github.com/conda-forge/conda-forge.github.io/tree/master/src/vote-results
178-
folder. The declaration PR should be merged by the first core member who is available to verify that
179-
the requirements for the timeout have been met, based on their own personal records.
129+
130+
:Quorum: Quorum for votes can be met in one of three ways depending on the
131+
vote: the standard quorum rules, the accelerated quorum rules, and the
132+
"time out" quorum rules. The specific quorum rules applicable
133+
for each vote are listed below.
134+
135+
**Standard Quorum Rules**: All percentages below express *both*
136+
required participation, as a
137+
fraction of the active core team, as well as the fraction of that
138+
fraction who vote affirmatively on the issue. For example, in a vote
139+
requiring 50%, with 18 active core members, at least 9 must vote;
140+
if 9 vote, there must 5 affirmative votes. If 13 members vote, 7
141+
must be affirmative.
142+
143+
**Accelerated Quorum Rules**: For certain votes, we allow a lower quorum level.
144+
For these votes,
145+
if the vote ends after at least a week and there are no "no" votes, a quorum
146+
of half of the size
147+
needed for a **standard quorum** above is accepatble. For example, for a vote
148+
requiring 50% with 18
149+
active core members, at least 5 people must vote "yes" and exactly 0 people
150+
must vote "no".
151+
152+
**Time-out Quorum Rules**: Because everyone is busy and it is difficult
153+
sometimes to get quorum,
154+
votes not achieving quorum will eventually time out on their set end date.
155+
When this happens,
156+
the current participation level is taken for what it is, and the percentage
157+
of affirmative votes is calculated from whatever the vote total is at that
158+
time. In order for a timeout to occur, the vote must have:
159+
160+
* been open for at least 2 weeks
161+
* been presented and discussed at a Core team meeting
162+
* been advertised on at least 3 separate occasions on the gitter core
163+
channel (beginning of voting period, middle, and one day prior to
164+
proposed timeout)
165+
* been sent to core members via email. Email reminders must have been
166+
sent similarly to the gitter core channel: at least 3 times,
167+
occurring as beginning of voting period, middle, and one day
168+
prior to proposed timeout.
169+
170+
Extending the above example, if 9 people are required for a quorum, but
171+
only 7 have voted, those 7 votes can form the basis of a completed vote
172+
after the above conditions are met. 4 votes within those 7 would be
173+
needed to pass the vote.
174+
175+
To post a timeout reminder, here is a template comment:
176+
177+
.. code-block:: md
178+
179+
@conda-forge/core
180+
This vote falls under the {policy} policy, please vote
181+
and/or comment on this PR.
182+
This vote needs {policy_percent} of core to vote yea to pass.
183+
This vote presently has {current_voters}, and needs
184+
{policy_percent * core - current_voters} more for quorum.
185+
It is proposed that this vote will time out and be
186+
evaluated with the current votes in {days}, on {date}.
187+
To vote please leave Approve (yea) or Request Changes (nay)
188+
reviews.
189+
190+
To declare a standard vote "timed out," the person making such a declaration
191+
must post a pull-request adding
192+
a vote record to the https://github.com/conda-forge/conda-forge.github.io/tree/master/src/vote-results
193+
folder. The declaration PR should be merged by the first core member
194+
who is available to verify that
195+
the requirements for the timeout have been met, based on their
196+
own personal records.
180197

181198
----
182199

0 commit comments

Comments
 (0)