a30ef3ecab
the US Senate, Canadian Parliament and Australian Senate, it was causing some confusion. After some consultation with Mark Murray, change this to 'without objection' since often times a plain-speaking term is preferable to a regionally used term. Also, clarify that this procedure is to be used when for more mundane matters that need a sanity check, but don't need the whole, ponderous voting proceedure that more difficult issues require. Core members that read email in any given 48 hour period are trusted enough to know the difference and to provide the sanity check as necessary. Reviewed by: markm
84 lines
2.9 KiB
Text
84 lines
2.9 KiB
Text
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
|
<!ENTITY base CDATA "..">
|
|
<!ENTITY date "$FreeBSD: www/en/internal/core-vote.sgml,v 1.3 2003/12/13 04:52:45 imp Exp $">
|
|
<!ENTITY title "Core's Voting Procedures">
|
|
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
|
]>
|
|
|
|
<html>
|
|
&header;
|
|
|
|
<h2>Core's Voting Procedures</h2>
|
|
|
|
<h3>Committers</h3>
|
|
|
|
<ul>
|
|
<li>All core members vote "yes", "no" or "no objection".</li>
|
|
<li>Successful candidates must get at least one yes vote.</li>
|
|
<li>Successful candidates must not get any 'no' votes.</li>
|
|
<li>At least three people must vote.</li>
|
|
<li>Voting period is normally 1 week, or ending sooner when the
|
|
result is certain.</li>
|
|
<li>Core secretary to deal with the details of voting, notification,
|
|
etc.</li>
|
|
</ul>
|
|
|
|
<h3>Personnel</h3>
|
|
|
|
<ul>
|
|
<li>All core members vote "yes" or "no".</li>
|
|
<li>Successful candidates must get at least (2/3 * core-size)
|
|
yes vote.</li>
|
|
<li>At least (2/3 * core-size) people must vote, or the measure
|
|
will fail.</li>
|
|
<li>Voting period is normally 1 week, or ending sooner when the
|
|
result is certain.</li>
|
|
<li>Core secretary to deal with the details of voting, notification,
|
|
etc.</li>
|
|
</ul>
|
|
|
|
<h3>Issues</h3>
|
|
|
|
<ul>
|
|
<li>Discussion takes place.</li>
|
|
<li>When a consensus resolution appears to have been reached,
|
|
a vote on that takes place.</li>
|
|
<li>All core members vote "yes" or "no".</li>
|
|
<li>Successful resolutions must get at least (2/3 * core-size)
|
|
yes vote.</li>
|
|
<li>At least (2/3 * core-size) people must vote, or the measure
|
|
will fail.</li>
|
|
<li>Voting period is normally 1 week, or ending sooner when the
|
|
result is certain.</li>
|
|
<li>Core secretary to deal with the details of voting, notification,
|
|
etc.</li>
|
|
</ul>
|
|
|
|
<h3>Without Objection</h3>
|
|
|
|
<ul>
|
|
<li>Any core member may ask core, via email, if they can take
|
|
some mundane action, subject to a quick sanity check of the
|
|
rest of core.</li>
|
|
<li>If no one objects within 48 hours, then that person may proceed
|
|
(or sooner if (2/3 * core-size) members agree).</li>
|
|
<li>If there are any objections, then it will be resolved via the
|
|
issue voting procedure.</li>
|
|
<li>Core secretary may send the OK to proceed message, as the
|
|
secretary deems appropriate.</li>
|
|
</ul>
|
|
|
|
<p>Any committer also use this mechanism so long as at least one
|
|
core member says 'yes' and the previous paragraph is otherwise
|
|
followed. It is intended to be used for mundane matters that
|
|
need a quick sanity check, but don't need a more heavy weight
|
|
and deliberative process. It is believed that the subset of
|
|
core present for any given 48 period are sufficient for both
|
|
sanity checking mundane matters and recognizing non-mundane
|
|
matters that need to be handled via the issues voting
|
|
procedure.</p>
|
|
|
|
&footer;
|
|
|
|
</body>
|
|
</html>
|