Document the new hats term limits policy.
This commit is contained in:
parent
2e437a995c
commit
13fbecdb05
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39128
2 changed files with 65 additions and 0 deletions
en_US.ISO8859-1/htdocs/internal
63
en_US.ISO8859-1/htdocs/internal/hats.sgml
Normal file
63
en_US.ISO8859-1/htdocs/internal/hats.sgml
Normal file
|
@ -0,0 +1,63 @@
|
||||||
|
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
|
||||||
|
<!ENTITY base CDATA "..">
|
||||||
|
<!ENTITY date "$FreeBSD$">
|
||||||
|
<!ENTITY title "Hats Term Limits Policy">
|
||||||
|
<!ENTITY % navinclude.docs "INCLUDE">
|
||||||
|
]>
|
||||||
|
|
||||||
|
<html>
|
||||||
|
&header;
|
||||||
|
|
||||||
|
<h2>Rationale</h2>
|
||||||
|
|
||||||
|
<p>The FreeBSD Core team appoints several individuals
|
||||||
|
(&ldquot;hats&rdquot;) that perform critical roles within the
|
||||||
|
project. It is important to reduce single points of failure in
|
||||||
|
these roles. Additionally, turnover in hats can provide fresh
|
||||||
|
insight and help avoid burnout.</p>
|
||||||
|
|
||||||
|
<p>The current set of core-appointed hats is core secretary, head
|
||||||
|
release engineer, the security officer, and postmaster.</p>
|
||||||
|
|
||||||
|
<p>It is suggested that shortened terms longer than half of a core
|
||||||
|
term be considered a full term for purposes of eligibility.</p>
|
||||||
|
|
||||||
|
<p>This policy will begin with the start of the next core term, and
|
||||||
|
all hats will start off with zero terms at that time.</p>
|
||||||
|
|
||||||
|
<p>The FreeBSD Core team approved the following hats term limits
|
||||||
|
policy which was posted to the Developers mailing list on June 22,
|
||||||
|
2012.</p>
|
||||||
|
|
||||||
|
<h2>Policy</h2>
|
||||||
|
|
||||||
|
<p>An individual may serve as a core-appointed hat for at most two
|
||||||
|
consecutive terms. Each hat's term begins three months after the
|
||||||
|
start of a core team's term and ends three months after the end of
|
||||||
|
a core team's term. Hats are explicitly approved by the new core
|
||||||
|
team at the start of a hat's term. An individual who serves as a
|
||||||
|
hat for two consecutive terms may serve again after a break of at
|
||||||
|
least one full term.</p>
|
||||||
|
|
||||||
|
<p>Core shall review all hats annually.</p>
|
||||||
|
|
||||||
|
<p>If a hat becomes vacant during a term, core shall appoint a
|
||||||
|
replacement for the remainder of the term. It is at core's
|
||||||
|
discretion whether the shortened term will count for purposes of
|
||||||
|
limiting the terms of the replacement.</p>
|
||||||
|
|
||||||
|
<p>If a core team is dissolved prematurely, then the next term for
|
||||||
|
each hat will begin three months after the new core team's term
|
||||||
|
begins. It is at the new core's discretion whether the shortened
|
||||||
|
term will count for purposes of limiting the terms of current
|
||||||
|
hats.</p>
|
||||||
|
|
||||||
|
<p>These limits apply to individual hats and not to teams. For
|
||||||
|
teams with a single lead role, the limits shall apply to the lead
|
||||||
|
role. An individual that is not eligible to serve as the lead of
|
||||||
|
a team may continue to serve as a member of the team.</p>
|
||||||
|
|
||||||
|
&footer;
|
||||||
|
|
||||||
|
</body>
|
||||||
|
</html>
|
|
@ -44,6 +44,8 @@ the
|
||||||
<a href="i18n.html">Internationalization Policy</a>,
|
<a href="i18n.html">Internationalization Policy</a>,
|
||||||
the
|
the
|
||||||
<a href="data.html">User Data Policy</a>,
|
<a href="data.html">User Data Policy</a>,
|
||||||
|
the
|
||||||
|
<a href="hats.html">Hats Term Limits Policy</a>,
|
||||||
and the
|
and the
|
||||||
<a href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem Report Handling Guidelines</a>.</p>
|
<a href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem Report Handling Guidelines</a>.</p>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue