From 1f4ffcf17f870b68ebb14b55e78304a52e2d2f77 Mon Sep 17 00:00:00 2001 From: Matthew Seaman Date: Wed, 7 Jun 2017 14:48:27 +0000 Subject: [PATCH] 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 --- en_US.ISO8859-1/htdocs/internal/Makefile | 1 + en_US.ISO8859-1/htdocs/internal/members.xml | 112 +++++++++++++++++++ en_US.ISO8859-1/htdocs/internal/policies.xml | 3 +- 3 files changed, 115 insertions(+), 1 deletion(-) create mode 100644 en_US.ISO8859-1/htdocs/internal/members.xml diff --git a/en_US.ISO8859-1/htdocs/internal/Makefile b/en_US.ISO8859-1/htdocs/internal/Makefile index 25870b29a9..0d749025cf 100644 --- a/en_US.ISO8859-1/htdocs/internal/Makefile +++ b/en_US.ISO8859-1/htdocs/internal/Makefile @@ -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 diff --git a/en_US.ISO8859-1/htdocs/internal/members.xml b/en_US.ISO8859-1/htdocs/internal/members.xml new file mode 100644 index 0000000000..a951d0e80e --- /dev/null +++ b/en_US.ISO8859-1/htdocs/internal/members.xml @@ -0,0 +1,112 @@ + + +]> + + + + &title; + + $FreeBSD$ + + + + +

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.

+ +

Committers

+ +

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:

+ + + +

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:

+ + + +

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

+ +

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

+ +

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 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:

+ +
+
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 + Project Members.
+
+ + + diff --git a/en_US.ISO8859-1/htdocs/internal/policies.xml b/en_US.ISO8859-1/htdocs/internal/policies.xml index 9365c80d94..b9bd6af506 100644 --- a/en_US.ISO8859-1/htdocs/internal/policies.xml +++ b/en_US.ISO8859-1/htdocs/internal/policies.xml @@ -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

    • The FreeBSD Documentation Project