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 @@ -1,7 +1,7 @@ + ]> @@ -13,20 +13,23 @@ -

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.

+

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:

-

Associates receive:

+

All members receive:

+ +

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:

+ + -

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.

- -

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.

+

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:

-
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.
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 @@ + ]> @@ -46,6 +46,7 @@
  • Problem Report Handling Guidelines
  • Software License Policy
  • User Data Policy
    • +
  • FreeBSD Project Membership

    • The FreeBSD Documentation Project