os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update to the hat policy.

Browse source 
With hat:     core-secretary
Approved by:  core
Differential Revision:	https://reviews.freebsd.org/D2803
This commit is contained in:
Matthew Seaman 2015-07-01 06:07:33 +00:00
parent aec92fe410
commit 4544767085
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=46906
1 changed files with 56 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

97
en_US.ISO8859-1/htdocs/internal/hats.xml
View file

@ -6,61 +6,76 @@
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<title>&title;</title> <title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head> </head>
<body class="navinclude.docs"> <body class="navinclude.docs">
<h2>Rationale</h2> <h2>Rationale</h2>
<p>The FreeBSD Core team appoints several individuals <p>The FreeBSD Core team appoints several individuals
(&quot;hats&quot;) that perform critical roles within the (&quot;hats&quot;) that perform critical roles within the
project. It is important to reduce single points of failure in project. It is important to reduce single points of failure in
these roles. Additionally, turnover in hats can provide fresh these roles. Additionally, turnover in hats can provide fresh
insight and help avoid burnout.</p> insight and help avoid burnout.</p>
<p>The current set of core-appointed hats is core secretary, head <p>The current set of core-appointed hats is core secretary,
release engineer, the security officer, and postmaster.</p> head release engineer, the security officer, and postmaster.</p>
<p>It is suggested that shortened terms longer than half of a core <p>The FreeBSD Core team has approved the following hats term
term be considered a full term for purposes of eligibility.</p> limits policy. This was first posted to the Developers mailing
list on June 22, 2012, and amended in June 2015.</p>
<p>This policy will begin with the start of the next core term, and <h2>Policy</h2>
all hats will start off with zero terms at that time.</p>
<p>The FreeBSD Core team approved the following hats term limits <p>An individual may serve as a core-appointed hat given that:</p>
policy which was posted to the Developers mailing list on June 22,
2012.</p>
<h2>Policy</h2> <ul>
<li>Core approves their appointment or re-appointment to the
role.</li>
<li>The individual is willing to continue.</li>
<li>The individual is still able to perform the role
effectively.</li>
</ul>
<p>An individual may serve as a core-appointed hat for at most two <p>Hats are appointed at the pleasure of core. Appointments may
consecutive terms. Each hat's term begins three months after the be rescinded by core at any time where this serves the needs of
start of a core team's term and ends three months after the end of the project.</p>
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>Each hat's term begins three months after the start of a core
team's two year term and ends three months after the end of the
core team's term. Hats are explicitly approved by the new core
team at the start of the hat's term.</p>
<p>If a hat becomes vacant during a term, core shall appoint a <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 replacement for the remainder of the term.</p>
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 <p>Core shall review all hats annually.</p>
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 <p>In general it is expected that volunteers serving in hat
teams with a single lead role, the limits shall apply to the lead positions will be limited to serving for four consecutive years,
role. An individual that is not eligible to serve as the lead of rounded up to the first natural review/appointment cycle.</p>
a team may continue to serve as a member of the team.</p>
<p>Non volunteers serving in hat positions are still expected to
participate in annual reviews and provide for continuity to
core's satisfaction.</p>
<p>Each hat must appoint a deputy who can cover their role in
the case of absence or illness, and be trained and ready to take
over the role (subject to core approval) should the role holder
resign before the end of their term.</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.</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>
</body> </body>
</html> </html>