From owner-svn-doc-all@freebsd.org Wed Jun 7 14:48:28 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 DB329C774F3; Wed, 7 Jun 2017 14:48:28 +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 B2DA376AFC; Wed, 7 Jun 2017 14:48:28 +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 v57EmRmT035999; Wed, 7 Jun 2017 14:48:27 GMT (envelope-from matthew@FreeBSD.org) Received: (from matthew@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v57EmRb0035996; Wed, 7 Jun 2017 14:48:27 GMT (envelope-from matthew@FreeBSD.org) Message-Id: <201706071448.v57EmRb0035996@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: matthew set sender to matthew@FreeBSD.org using -f From: Matthew Seaman Date: Wed, 7 Jun 2017 14:48:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50324 - 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 14:48:29 -0000 Author: matthew (ports committer) Date: Wed Jun 7 14:48:27 2017 New Revision: 50324 URL: https://svnweb.freebsd.org/changeset/doc/50324 Log: Add documentation describing the new 'FreeBSD Project Member' status, as discussed in the core session at BSDCan. Please see review D10413 if you want to suggest any further changes. Approved by: core Differential Revision: https://reviews.freebsd.org/D10413 Added: head/en_US.ISO8859-1/htdocs/internal/members.xml - copied, changed from r50194, head/en_US.ISO8859-1/htdocs/internal/associates.xml Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile head/en_US.ISO8859-1/htdocs/internal/policies.xml Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/Makefile Wed Jun 7 09:52:55 2017 (r50323) +++ head/en_US.ISO8859-1/htdocs/internal/Makefile Wed Jun 7 14:48:27 2017 (r50324) @@ -21,6 +21,7 @@ DOCS+= hats.xml DOCS+= i18n.xml DOCS+= internal.xml DOCS+= machines.xml +DOCS+= members.xml DOCS+= mirror.xml DOCS+= new-account.xml DOCS+= policies.xml Copied and modified: head/en_US.ISO8859-1/htdocs/internal/members.xml (from r50194, head/en_US.ISO8859-1/htdocs/internal/associates.xml) ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/associates.xml Sat Apr 22 17:54:33 2017 (r50194, copy source) +++ head/en_US.ISO8859-1/htdocs/internal/members.xml Wed Jun 7 14:48:27 2017 (r50324) @@ -1,7 +1,7 @@ + ]> @@ -13,20 +13,21 @@ -

FreeBSD Project Associate

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 + 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.

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.

Committers

Associates receive:

+
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 @@ -37,41 +38,74 @@
the right to attend developer summits
access to the developers@ mailing list

+ +

Committer Benefits:

+ +

In addition to the Ordinary Member benefits, active + Committers (those who have made a commit within the previous + year) are able to vote in Core elections.

+ +

Member Responsibilities:

+ +

All Members should ensure that all contributed material:

+ +

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.

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

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

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

Members are bound by the Project's Code of Conduct, + particularly when representing the Project in external fora.

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.

Member status is conferred by a ballot of Core members, or by + a ballot of other groups that Core may designate such as Portmgr + or Doceng. Any FreeBSD Committer or Member may propose + candidates for member 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.

Core, or groups designated by Core that award Member status, + should review that status at least once annually and retire + inactive accounts. There is no formal definition of inactive + accounts. 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.
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 + setting up their accounts and gaining access to Project + resources and so forth.
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 - Associates.; Existing 3rd Party Developers will be promoted to + Project Members.

Modified: head/en_US.ISO8859-1/htdocs/internal/policies.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/policies.xml Wed Jun 7 09:52:55 2017 (r50323) +++ head/en_US.ISO8859-1/htdocs/internal/policies.xml Wed Jun 7 14:48:27 2017 (r50324) @@ -1,7 +1,7 @@ + ]> @@ -46,6 +46,7 @@ below, for more info.

Problem Report Handling Guidelines

Software License Policy

User Data Policy

FreeBSD Project Membership