Page MenuHomeFreeBSD
Files F140074895

D2803.id6167.diff
No OneTemporary
Actions

D2803.id6167.diff
View Options

Index: internal/hats.xml
===================================================================
--- internal/hats.xml
+++ internal/hats.xml
@@ -24,38 +24,46 @@
<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>The FreeBSD Core team has approved the following hats term 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
- all hats will start off with zero terms at that time.</p>
+ <h2>Policy</h2>
- <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>
+ <p>An individual may serve as a core-appointed hat so long as:</p>
- <h2>Policy</h2>
+ <ul>
+ <li>They are willing to continue.</li>
+ <li>They are still performing the role effectively.</li>
+ <li>Core approves their appointment or re-appointment to the role.</li>
+ </ul>
+
+ <p>Hats are appointed at the pleasure of core. Appointments may be
+ rescinded by core at any time where this serves the needs of the
+ project.</p>
+
+ <p>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.</p>
- <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>If a hat becomes vacant during a term, core shall appoint a
+ replacement for the remainder of the 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>It is expected that each hat will serve for no more than two
+ complete two-year core terms, but this is not a hard limit and
+ role-holders may continue for longer.</p>
+
+ <p>Each hat should 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. It is at the new core's discretion whether the shortened
- term will count for purposes of limiting the terms of current
- hats.</p>
+ 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

File Metadata

Mime Type
text/plain
Expires
Sat, Dec 20, 9:52 PM (3 h, 53 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
27101405
Default Alt Text
D2803.id6167.diff (3 KB)

Event Timeline