Index: head/en_US.ISO8859-1/htdocs/internal/associates.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/internal/associates.xml (revision 50194) +++ head/en_US.ISO8859-1/htdocs/internal/associates.xml (nonexistent) @@ -1,78 +0,0 @@ - - -]> - - - - &title; - - $FreeBSD$ - - - - -

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.

- -

Associates receive:

- - - -

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

- -

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

- -

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.

- -
- -

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.
-
How does this affect the existing 3rd Party Developer - status?
-
Existing 3rd party developers will be promoted to - Associates.
-
- - - Property changes on: head/en_US.ISO8859-1/htdocs/internal/associates.xml ___________________________________________________________________ Deleted: svn:eol-style ## -1 +0,0 ## -native \ No newline at end of property Deleted: svn:keywords ## -1 +0,0 ## -FreeBSD=%H \ No newline at end of property Deleted: svn:mime-type ## -1 +0,0 ## -text/xml \ No newline at end of property Index: head/en_US.ISO8859-1/htdocs/internal/Makefile =================================================================== --- head/en_US.ISO8859-1/htdocs/internal/Makefile (revision 50194) +++ head/en_US.ISO8859-1/htdocs/internal/Makefile (revision 50195) @@ -1,54 +1,53 @@ # $FreeBSD$ .if exists(../Makefile.conf) .include "../Makefile.conf" .endif .if exists(../Makefile.inc) .include "../Makefile.inc" .endif DOCS= about.xml -DOCS+= associate.xml DOCS+= bylaws.xml DOCS+= clusteradm.xml DOCS+= code-of-conduct.xml DOCS+= core-vote.xml DOCS+= data.xml DOCS+= developer.xml DOCS+= doceng.xml DOCS+= expire-bits.xml DOCS+= fortunes.xml DOCS+= hats.xml DOCS+= i18n.xml DOCS+= internal.xml DOCS+= machines.xml DOCS+= mirror.xml DOCS+= new-account.xml DOCS+= policies.xml DOCS+= proposing-committers.xml DOCS+= releng.xml DOCS+= resources.xml DOCS+= software-license.xml DOCS+= working-with-hats.xml INDEXLINK= internal.html # build the list of personal homepages of FreeBSD developers only # on the main FreeBSD machines hostname!= hostname .if !empty(hostname:tl:M*.freebsd.org) DOCS+= homepage.xml .if !make(install) .PHONY: homepage.inc .endif homepage.inc: homepage.pl ${PERL} ${.CURDIR}/homepage.pl > ${.TARGET} homepage.html: homepage.inc CLEANFILES+= homepage.inc .endif DATA+= ssh-keys.asc .include "${DOC_PREFIX}/share/mk/web.site.mk" Index: head/en_US.ISO8859-1/htdocs/internal/policies.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/internal/policies.xml (revision 50194) +++ head/en_US.ISO8859-1/htdocs/internal/policies.xml (revision 50195) @@ -1,79 +1,78 @@ + ]> &title; $FreeBSD$

Committer's Guide

The Committer's Guide is an overall guide for all new committers, including both technical details and policy details. For the latter, see the chapters on Conventions and Traditions, Developer Relations, and The FreeBSD Committers' Big List Of Rules.

It contains almost everything a new committer to the FreeBSD Project needs to know. See the Documentation Project Primer and the Ports Guide, below, for more info.

General Policies

The FreeBSD Documentation Project

The FreeBSD Documentation Project Primer for New Contributors covers everything you will need to know in order to start contributing to the FreeBSD Documentation Project, from the tools and software you will be using (both mandatory and recommended) to the philosophy behind the Documentation Project.

The FreeBSD Doceng Team Charter describes the purpose of Doceng.

The FreeBSD Ports Guidelines

The FreeBSD Porter's Handbook is a general guide for FreeBSD ports committers, including both technical information and policy guidelines.

The Ports Management Team has a separate page with policies and other information related to the FreeBSD Ports Collection.

FreeBSD Internal Home