&title;

From owner-svn-doc-all@freebsd.org Wed Jul 1 06:07:34 2015 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAA6C992293; Wed, 1 Jul 2015 06:07:34 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8ECA51153; Wed, 1 Jul 2015 06:07:34 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t6167YnU004075; Wed, 1 Jul 2015 06:07:34 GMT (envelope-from matthew@FreeBSD.org) Received: (from matthew@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t6167Y8A004074; Wed, 1 Jul 2015 06:07:34 GMT (envelope-from matthew@FreeBSD.org) Message-Id: <201507010607.t6167Y8A004074@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: matthew set sender to matthew@FreeBSD.org using -f From: Matthew Seaman Date: Wed, 1 Jul 2015 06:07:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46906 - head/en_US.ISO8859-1/htdocs/internal X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire doc trees $except for " user" , " projects" , and " translations" $" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 06:07:34 -0000 Author: matthew (ports committer) Date: Wed Jul 1 06:07:33 2015 New Revision: 46906 URL: https://svnweb.freebsd.org/changeset/doc/46906 Log: Update to the hat policy. With hat: core-secretary Approved by: core Differential Revision: https://reviews.freebsd.org/D2803 Modified: head/en_US.ISO8859-1/htdocs/internal/hats.xml Modified: head/en_US.ISO8859-1/htdocs/internal/hats.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/hats.xml Wed Jul 1 01:33:54 2015 (r46905) +++ head/en_US.ISO8859-1/htdocs/internal/hats.xml Wed Jul 1 06:07:33 2015 (r46906) @@ -6,61 +6,76 @@ - &title; + &title; - $FreeBSD$ - + $FreeBSD$ + - + -

Rationale

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.

Policy

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:

Policy

Core approves their appointment or re-appointment to the + role.
The individual is willing to continue.
The individual is still able to perform the role + effectively.

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.