From owner-svn-doc-all@freebsd.org Sat Apr 22 13:45:48 2017 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 328EFD4AFAD; Sat, 22 Apr 2017 13:45:48 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::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 E8215143; Sat, 22 Apr 2017 13:45:47 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v3MDjlQ1008977; Sat, 22 Apr 2017 13:45:47 GMT (envelope-from matthew@FreeBSD.org) Received: (from matthew@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v3MDjkIN008975; Sat, 22 Apr 2017 13:45:46 GMT (envelope-from matthew@FreeBSD.org) Message-Id: <201704221345.v3MDjkIN008975@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: matthew set sender to matthew@FreeBSD.org using -f From: Matthew Seaman Date: Sat, 22 Apr 2017 13:45:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50193 - 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.23 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: Sat, 22 Apr 2017 13:45:48 -0000 Author: matthew (ports committer) Date: Sat Apr 22 13:45:46 2017 New Revision: 50193 URL: https://svnweb.freebsd.org/changeset/doc/50193 Log: Add documentation about 'FreeBSD PRoject Associates' Approved by: core (bcr) Differential Revision: https://reviews.freebsd.org/D10413 Added: head/en_US.ISO8859-1/htdocs/internal/associates.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/internal/policies.xml Added: head/en_US.ISO8859-1/htdocs/internal/associates.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/internal/associates.xml Sat Apr 22 13:45:46 2017 (r50193) @@ -0,0 +1,78 @@ + + +]> + + + + &title; + + $FreeBSD$ + + + + +

FreeBSD Project Associate

+ +

An Associate is an individual who has made a notable contribution + to the FreeBSD project. That may be in the form of new code, + documentation, or patches to existing code and documentation + committed through a currently valid Committer, or in other ways + that the Core Team designates, including community management and + advocacy. Associates do not have any voting rights or + responsibilities to the project other than to ensure their + contributed material adheres to the project's standards and + practices, that the work is original to the author and is made + available under the standard, FreeBSD license.

+ +

Associates receive:

+ +
    +
  • an @freebsd.org email address which also gives them regular + Bugzilla and Phabricator logins
    • +
  • permission to assign bugs to themselves in bugzilla
    • +
  • access to freefall and the universe build machines
    • +
  • access to the test clusters
    • +
  • the right to attend developer summits
    • +
  • access to the developers@ mailing list
    • +
+ +

Associates MUST create SSH and PGP keys in exactly the same way + that a committer would to gain access to project resources.

+ +

Associates are bound by the Code of Conduct of the FreeBSD Project.

+ +

Associate status is conferred by a ballot of Core members, or + by other groups that Core may designate such as Portmgr or Doceng. + Any FreeBSD committer or associate may propose candidates for + associate status.

+ +

Core, or groups that core may designate, that award associate + status, should review that status at least once annually and + retire inactive accounts. There is no minimum level of + contribution required, Core and the designated teams may use their + own discretion.

+ +
+ +

FAQ:

+ +
+
Assigning a buddy (or group of buddies) to the + associate.
+
No. Associates will be assigned a mentor when they reach a + level to upgrade from Associate to Committer. Until that time, + they can use the mailing lists and the phabricator review + groups.
+
Do committers who have given up their commit bits + effectively become associates?
+
No, they become Alumni.
+
How does this affect the existing 3rd Party Developer + status?
+
Existing 3rd party developers will be promoted to + Associates.
+
+ + + Modified: head/en_US.ISO8859-1/htdocs/internal/policies.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/policies.xml Fri Apr 21 19:43:56 2017 (r50192) +++ head/en_US.ISO8859-1/htdocs/internal/policies.xml Sat Apr 22 13:45:46 2017 (r50193) @@ -1,7 +1,7 @@ + ]> @@ -46,6 +46,7 @@ below, for more info.

  • Problem Report Handling Guidelines
  • Software License Policy
  • User Data Policy
    • +
  • FreeBSD Project Associates

    • The FreeBSD Documentation Project