Index: head/en_US.ISO8859-1/htdocs/internal/Makefile
===================================================================
--- head/en_US.ISO8859-1/htdocs/internal/Makefile (revision 50323)
+++ head/en_US.ISO8859-1/htdocs/internal/Makefile (revision 50324)
@@ -1,53 +1,54 @@
# $FreeBSD$
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
DOCS= about.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+= members.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/members.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/internal/members.xml (nonexistent)
+++ head/en_US.ISO8859-1/htdocs/internal/members.xml (revision 50324)
@@ -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:
+
+
+ - an @freebsd.org email address which also gives them regular
+ Bugzilla and Phabricator logins
+ - permission to assign bugs to themselves in bugzilla
+ - access to freefall and the universe build machines
+ - access to the test clusters
+ - 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.
+
+
+ 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.
+
+
+
+
Property changes on: head/en_US.ISO8859-1/htdocs/internal/members.xml
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+FreeBSD=%H
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/xml
\ No newline at end of property
Index: head/en_US.ISO8859-1/htdocs/internal/policies.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/internal/policies.xml (revision 50323)
+++ head/en_US.ISO8859-1/htdocs/internal/policies.xml (revision 50324)
@@ -1,78 +1,79 @@
+
]>
&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