From owner-svn-doc-all@freebsd.org Wed Jun 7 15:02:44 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 A4B33C779FB; Wed, 7 Jun 2017 15:02:44 +0000 (UTC) (envelope-from gjb@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 804E97731C; Wed, 7 Jun 2017 15:02:44 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v57F2h2s044017; Wed, 7 Jun 2017 15:02:43 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v57F2hop044016; Wed, 7 Jun 2017 15:02:43 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201706071502.v57F2hop044016@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Wed, 7 Jun 2017 15:02:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50326 - 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: Wed, 07 Jun 2017 15:02:44 -0000 Author: gjb Date: Wed Jun 7 15:02:43 2017 New Revision: 50326 URL: https://svnweb.freebsd.org/changeset/doc/50326 Log: Whitespace cleanup and line wrapping. Translators please ignore. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/internal/members.xml Modified: head/en_US.ISO8859-1/htdocs/internal/members.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/members.xml Wed Jun 7 14:57:00 2017 (r50325) +++ head/en_US.ISO8859-1/htdocs/internal/members.xml Wed Jun 7 15:02:43 2017 (r50326) @@ -14,9 +14,9 @@

FreeBSD Project Members

- +

A FreeBSD Project Member is an individual who has made a - notable contribution to the FreeBSD Project. That may be in the + notable contribution to the FreeBSD Project. That may be in the form of new code, documentation, or patches to existing code and documentation, or in other ways that the Core Team designates, including community management and advocacy.

@@ -26,12 +26,12 @@

Committers are those Project members who have been granted commit access (a "commit bit") to one or more of the Project's repositories.

- +

Member Benefits:

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

adheres to the Project's standards and practices.
is correctly attributed to its authors.
has appropriate licensing. Where this is the original - work of the Project Member, the standard FreeBSD license is - preferred.
has appropriate licensing. Where this is the original work + of the Project Member, the standard FreeBSD license is + preferred.

Members MUST create SSH and PGP keys in order to gain access to Project resources.

FAQ:

Is a mentor assigned to each newly created Project Member?
Is a mentor assigned to each newly created Project + Member?: Project Members are only assigned a mentor if they become - a committer, or if they have a commit bit reactivated after a - significant period of inactivity. This only applies to - Committers since the primary purpose of a mentor is to review - what the mentee intends to commit.; No such formal arrangement is required when someone is made into an ordinary Project Member, but it is expected that the people that sponsor a new Member will assist them with @@ -93,20 +94,19 @@
Do you have to become an Ordinary Member before you can be granted a commit bit?: No. There is no requirement for prospective Committers to - have spent time as Ordinary Members. However it is - anticipated that this will become a common practice as part of - the route towards committer-hood.
Do Committers who have given up their commit bits - effectively become just Ordinary Members?: All Committers are Project members, but former Committers are considered Committer Alumni. Alumni may revert back to active Committers simply by requesting reinstatement of their commit access.
How does this affect the existing 3rd Party Developer - status?: Existing 3rd Party Developers will be promoted to - Project Members.; Existing 3rd Party Developers will be promoted to Project + Members.