Page MenuHomeFreeBSD
Files F142625882

D10413.id27898.diff
No OneTemporary
Actions

D10413.id27898.diff
View Options

Index: en_US.ISO8859-1/htdocs/internal/Makefile
===================================================================
--- en_US.ISO8859-1/htdocs/internal/Makefile
+++ en_US.ISO8859-1/htdocs/internal/Makefile
@@ -21,6 +21,7 @@
DOCS+= i18n.xml
DOCS+= internal.xml
DOCS+= machines.xml
+DOCS+= members.xml
DOCS+= mirror.xml
DOCS+= new-account.xml
DOCS+= policies.xml
Index: en_US.ISO8859-1/htdocs/internal/members.xml
===================================================================
--- en_US.ISO8859-1/htdocs/internal/members.xml
+++ en_US.ISO8859-1/htdocs/internal/members.xml
@@ -13,20 +13,46 @@
<body class="navinclude.docs">
- <h1>FreeBSD Project Associate</h1>
+ <h1>FreeBSD Project Members</h1>
- <p>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
+ <p>Membership of the FreeBSD project has been extended to include
+ ordinary members as well as committers. Committers are now
+ distinguished as being those project members who have (or used to
+ have) commit access (a "commit bit") into one or more of the
+ project's repositories.</p>
+
+ <p>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.</p>
+
+ <h3>Committers</h3>
+
+ <p>Committers are those members who have made sufficient
+ contributions that they have been granted commit rights into one
+ or more project code repositories. Committers are expected to
+ ensure that the work they commit is correctly attributed to its
+ authors, that it has appropriate licensing, and that it follows
+ the project's standards and practices. Committers are
+ required to adhere to the FreeBSD project Code of Conduct,
+ particularly when representing the project in external fora.</p>
+
+ <p>Active committers (those who have made a commit within the
+ previous year) are able to vote in Core elections.</p>
+
+ <h3>Ordinary Members</h3>
+
+ <p>Ordinary members 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.</p>
+ practices, that their contributed work is of their own original
+ authorship and is made available under an acceptable license,
+ preferably the standard FreeBSD license.</p>
+
+ <h2>All Members</h2>
- <h2>Associates receive:<h2>
+ <p>All members receive:</p>
<ul>
<li>an @freebsd.org email address which also gives them regular
@@ -38,17 +64,18 @@
<li>access to the developers@ mailing list</li>
</ul>
- <p>Associates MUST create SSH and PGP keys in exactly the same way
- that a committer would to gain access to project resources.</p>
-
- <p>Associates are bound by the Code of Conduct of the FreeBSD Project.</p>
-
- <p>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.</p>
+ <p>Members MUST create SSH and PGP keys in exactly the same way as
+ committers have done previously in order to gain access to project
+ resources.</p>
+
+ <p>Members are bound by the Code of Conduct of the FreeBSD project.</p>
+
+ <p>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.</p>
- <p>Core, or groups that core may designate, that award associate
+ <p>Core, or groups that Core may designate, that award member
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
@@ -59,19 +86,33 @@
<h2>FAQ:</h2>
<dl>
- <dt>Assigning a buddy (or group of buddies) to the
- associate.</dt>
- <dd>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.</dd>
+ <dt>Is a mentor assigned to each newly created project member?</dt>
+ <dd>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.</dd>
+ <dd>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.</dd>
+ <dt>Do you have to become an ordinary member before you can be
+ granted a commit bit?</dt>
+ <dd>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.</dd>
<dt>Do committers who have given up their commit bits
- effectively become associates?</dt>
- <dd>No, they become Alumni.</dd>
+ effectively become just ordinary members?</dt>
+ <dd>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.</dd>
<dt>How does this affect the existing 3rd Party Developer
status?</dt>
<dd>Existing 3rd party developers will be promoted to
- Associates.</dd>
+ project members.</dd>
</dl>
</body>
Index: en_US.ISO8859-1/htdocs/internal/policies.xml
===================================================================
--- en_US.ISO8859-1/htdocs/internal/policies.xml
+++ en_US.ISO8859-1/htdocs/internal/policies.xml
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
-<!ENTITY title "Policies for FreeBSD Committers">
+<!ENTITY title "Policies for FreeBSD Project Members">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
@@ -46,6 +46,7 @@
<li><a href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem Report Handling Guidelines</a></li>
<li><a href="software-license.html">Software License Policy</a></li>
<li><a href="data.html">User Data Policy</a></li>
+ <li><a href="members.html">FreeBSD Project Membership</a></li>
</ul>
<h2><b>The FreeBSD Documentation Project</b></h2>

File Metadata

Mime Type
text/plain
Expires
Thu, Jan 22, 3:04 PM (17 h, 6 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
27853266
Default Alt Text
D10413.id27898.diff (7 KB)

Event Timeline