Index: head/en_US.ISO8859-1/htdocs/internal/hats.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/internal/hats.xml +++ head/en_US.ISO8859-1/htdocs/internal/hats.xml @@ -6,61 +6,76 @@
-The FreeBSD Core team appoints several individuals - ("hats") 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.
+The FreeBSD Core team appoints several individuals + ("hats") 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.
-The current set of core-appointed hats is core secretary, head - release engineer, the security officer, and postmaster.
+The current set of core-appointed hats is core secretary, + head release engineer, the security officer, and postmaster.
-It is suggested that shortened terms longer than half of a core - term be considered a full term for purposes of eligibility.
+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.
-This policy will begin with the start of the next core term, and - all hats will start off with zero terms at that time.
+The FreeBSD Core team approved the following hats term limits - policy which was posted to the Developers mailing list on June 22, - 2012.
+An individual may serve as a core-appointed hat given that:
-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.
+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.
-Core shall review all hats annually.
+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.
-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.
+If a hat becomes vacant during a term, core shall appoint a + replacement for the remainder of the term.
-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.
+Core shall review all hats annually.
-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.
+In general it is expected that volunteers serving in hat + positions will be limited to serving for four consecutive years, + rounded up to the first natural review/appointment cycle.
+ +Non volunteers serving in hat positions are still expected to + participate in annual reviews and provide for continuity to + core's satisfaction.
+ +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.
+ +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.
+ +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.