doc/en/internal/core-vote.sgml
Hiroki Sato cfd9e12239 www cleanup mega commit:
- Move includes.nav*.sgml to share/sgml/navibar.ent and
   <lang>/share/sgml/nabibar.l10n.ent.

 - Move includes.sgml and includes.xsl to
   share/sgml/common.ent, share/sgml/header.ent, <lang>/share/sgml/l10n.ent,
   and <lang>?share/sgml/header.l10n.ent.

 - Move most of XSLT libraries to share/sgml/*.xsl and
   <lang>/share/sgml/*.xsl.

 - Move news.xml and other *.xml files for the similar purpose
   to share/sgml/*.xml and <lang>/share/sgml/*.xml.

 - Switch to use a custom DTD for HTML document.  Now we use
   "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension", which is
   HTML 4.01 + some entities previously pulled via
   "<!ENTITY % includes SYSTEM "includes.sgml"> %includes;" line.
   The location of entity file will be resolved by using catalog file.

 - Add DOCTYPE declearation to XML documents.  This makes the followings
   possible:

   * Use of &foo; entities for SGML in an XML file instead of defining
     {$foo} as the same content.

   * &symbolic; entities for Latin characters.

 - Duplicated information between SGML and XML, or English and
   translated doc, has been removed as much as possible.
2006-08-19 21:20:54 +00:00

82 lines
2.9 KiB
Text

<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/internal/core-vote.sgml,v 1.8 2006/02/22 13:28:14 joel Exp $">
<!ENTITY title "Core's Voting Procedures">
<!ENTITY % navinclude.docs "INCLUDE">
]>
<html>
&header;
<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>