Add a new administration page. It contains better information about what
the different teams do and what their responsibilities are. Our developers are generally very confused when it comes to finding the right person to talk to, for example when requesting repo-copies or new perforce accounts etc. This will hopefully improve the situation somewhat. This is meant to replace certain sections of the contributors article, as this contains more up-to-date information and more teams etc. I'll take a look at removing the sections in question and all references to them soon. Also, the translation teams generally don't translate the contributors article since it doesn't seem to be worth the effort. Hopefully this will change now, since this can be quite important information even for non-English speaking people. I've based my work on comments from many developers and patches have been floating around on the doc list for a while, so it's about time I commit it. Reviewed by: doc@
This commit is contained in:
Joel Dahl
parent
186dea4022
commit
e18c48cd65
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=29677
3 changed files with 585 additions and 2 deletions
|
|
@ -1,4 +1,4 @@
|
|||
# $FreeBSD: www/en/Makefile,v 1.137 2006/07/11 13:36:17 hrs Exp $
|
||||
# $FreeBSD: www/en/Makefile,v 1.138 2007/01/07 22:44:45 keramida Exp $
|
||||
|
||||
.if exists(Makefile.conf)
|
||||
.include "Makefile.conf"
|
||||
|
|
@ -10,6 +10,7 @@
|
|||
# These are turned into validated, normalized HTML files.
|
||||
|
||||
DOCS= about.sgml
|
||||
DOCS+= administration.sgml
|
||||
DOCS+= applications.sgml
|
||||
DOCS+= art.sgml
|
||||
DOCS+= availability.sgml
|
||||
|
|
|
|||
581
en/administration.sgml
Normal file
581
en/administration.sgml
Normal file
|
|
@ -0,0 +1,581 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
|
||||
<!ENTITY date "$FreeBSD$">
|
||||
<!ENTITY title "FreeBSD Project Administration and Management">
|
||||
<!ENTITY % navinclude.about "INCLUDE">
|
||||
<!ENTITY % developers SYSTEM "developers.sgml"> %developers;
|
||||
]>
|
||||
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
<p>This page lists teams, groups and individuals within the
|
||||
FreeBSD project with designated project roles and areas of
|
||||
responsibility, along with brief descriptions and contact
|
||||
information.</p>
|
||||
|
||||
<ul>
|
||||
<li>Project Management
|
||||
<ul>
|
||||
<li><a href="#t-core">Core Team</a></li>
|
||||
<li><a href="#t-doceng">Documentation Engineering Team</a></li>
|
||||
<li><a href="#t-portmgr">Port Management Team</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Release Engineering
|
||||
<ul>
|
||||
<li><a href="#t-re">Primary Release Engineering Team</a></li>
|
||||
<li><a href="#t-re-alpha">FreeBSD/alpha Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-amd64">FreeBSD/amd64 Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-ia64">FreeBSD/ia64 Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-x86">FreeBSD/i386 Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-pc98">FreeBSD/pc98 Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-ppc">FreeBSD/ppc Release Engineering
|
||||
Team</a></li>
|
||||
<li><a href="#t-re-sparc64">FreeBSD/sparc64 Release Engineering
|
||||
Team</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Teams
|
||||
<ul>
|
||||
<li><a href="#t-donations">Donations Team</a></li>
|
||||
<li><a href="#t-marketing">Marketing Team</a></li>
|
||||
<li><a href="#t-secteam">Security Team</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Secretaries
|
||||
<ul>
|
||||
<li><a href="#t-core-secretary">Core Team Secretary</a></li>
|
||||
<li><a href="#t-portmgr-secretary">Port Management Team
|
||||
Secretary</a></li>
|
||||
<li><a href="#t-secteam-secretary">Security Team Secretary</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Internal Administration
|
||||
<ul>
|
||||
<li><a href="#t-accounts">Accounts Team</a></li>
|
||||
<li><a href="#t-backups">Backup Administrators</a></li>
|
||||
<li><a href="#t-bugmeister">Bugmeisters & GNATS
|
||||
Administrators</a></li>
|
||||
<li><a href="#t-clusteradm">Cluster Administrators</a></li>
|
||||
<li><a href="#t-dcvs">CVS doc/www Repository Managers</a></li>
|
||||
<li><a href="#t-pcvs">CVS ports Repository Managers</a></li>
|
||||
<li><a href="#t-ncvs">CVS src Repository Managers</a></li>
|
||||
<li><a href="#t-cvsup-master">CVSup Mirror Site
|
||||
Coordinators</a></li>
|
||||
<li><a href="#t-dnsadm">DNS Administrators</a></li>
|
||||
<li><a href="#t-mirror-admin">FTP/WWW Mirror Site
|
||||
Coordinators</a></li>
|
||||
<li><a href="#t-perforce-admin">Perforce Repository
|
||||
Administrators</a></li>
|
||||
<li><a href="#t-postmaster">Postmaster Team</a></li>
|
||||
<li><a href="#t-refadm">Ref Administrators</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<h3><a name="t-core">FreeBSD Core Team</a>
|
||||
<<a href="mailto:core@">core@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Core Team constitutes the project's "Board of Directors",
|
||||
responsible for deciding the project's overall goals and direction as
|
||||
well as managing specific areas of the FreeBSD project landscape. The
|
||||
Core Team is elected by the active developers in the project.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.wilko; <<a href="mailto:wilko@">wilko@</a>></li>
|
||||
<li>&a.brooks; <<a href="mailto:brooks@">brooks@</a>></li>
|
||||
<li>&a.keramida; <<a href="mailto:keramida@">keramida@</a>></li>
|
||||
<li>&a.imp; <<a href="mailto:imp@">imp@</a>></li>
|
||||
<li>&a.gnn; <<a href="mailto:gnn@">gnn@</a>></li>
|
||||
<li>&a.wes; <<a href="mailto:wes@">wes@</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@">hrs@</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-doceng">FreeBSD Documentation Engineering Team</a>
|
||||
<<a href="mailto:doceng@">doceng@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Documentation Engineering Team is responsible for
|
||||
defining and following up documentation goals for the committers
|
||||
in the Documentation project. The <a
|
||||
href="internal/doceng.html">doceng team charter</a>
|
||||
describes the duties and responsibilities of the Documentation
|
||||
Engineering Team in greater detail.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.nik; <<a href="mailto:nik@">nik@</a>></li>
|
||||
<li>&a.blackend; <<a href="mailto:blackend@">blackend@</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@">hrs@</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-portmgr">FreeBSD Port Management Team</a>
|
||||
<<a href="mailto:portmgr@">portmgr@</a>></h3>
|
||||
|
||||
<p>The primary responsibility of the FreeBSD Port Management Team is to
|
||||
ensure that the FreeBSD Ports Developer community provides a ports
|
||||
collection that is functional, stable, up-to-date and full-featured.
|
||||
Its secondary responsibility is to coordinate among the committers
|
||||
and developers who work on it. The <a
|
||||
href="portmgr/charter.html">portmgr team charter</a>
|
||||
describes the duties and responsibilities of the Port Management
|
||||
Team in greater detail.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.marcus; <<a href="mailto:marcus@">marcus@</a>></li>
|
||||
<li>&a.clement; <<a href="mailto:clement@">clement@</a>></li>
|
||||
<li>&a.erwin; <<a href="mailto:erwin@">erwin@</a>></li>
|
||||
<li>&a.linimon; <<a href="mailto:linimon@">linimon@</a>></li>
|
||||
<li>&a.pav; <<a href="mailto:pav@">pav@</a>></li>
|
||||
<li>&a.kris; <<a href="mailto:kris@">kris@</a>></li>
|
||||
<li>&a.krion; <<a href="mailto:krion@">krion@</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<h3><a name="t-re">Primary Release Engineering Team</a>
|
||||
<<a href="mailto:re@">re@</a>></h3>
|
||||
|
||||
<p>The Primary Release Engineering Team is responsible for setting and
|
||||
publishing release schedules for official project releases of FreeBSD,
|
||||
announcing code freezes and maintaining RELENG_* branches, among other
|
||||
things. The <a
|
||||
href="releng/charter.html">release engineering team charter</a>
|
||||
describes the duties and responsibilities of the Primary Release
|
||||
Engineering Team in greater detail.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.mux; <<a href="mailto:mux@">mux@</a>></li>
|
||||
<li>&a.bmah; <<a href="mailto:bmah@">bmah@</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@">hrs@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>>
|
||||
(Lead)</li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
<li>&a.dwhite; <<a href="mailto:dwhite@">dwhite@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-alpha">FreeBSD/alpha Release Engineering Team</a>
|
||||
<<a href="mailto:re-alpha@">re-alpha@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/alpha Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/alpha platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.wilko; <<a href="mailto:wilko@">wilko@</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-amd64">FreeBSD/amd64 Release Engineering Team</a>
|
||||
<<a href="mailto:re-amd64@">re-amd64@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/amd64 Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/amd64 platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.obrien; <<a href="mailto:obrien@">obrien@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-ia64">FreeBSD/ia64 Release Engineering Team</a>
|
||||
<<a href="mailto:re-ia64@">re-ia64@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/ia64 Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/ia64 platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.marcel; <<a href="mailto:marcel@">marcel@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-x86">FreeBSD/i386 Release Engineering Team</a>
|
||||
<<a href="mailto:re-x86@">re-x86@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/i386 Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/i386 platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-pc98">FreeBSD/pc98 Release Engineering Team</a>
|
||||
<<a href="mailto:re-pc98@">re-pc98@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/pc98 Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/pc98 platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.nyan; <<a href="mailto:nyan@">nyan@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-ppc">FreeBSD/ppc Release Engineering Team</a>
|
||||
<<a href="mailto:re-ppc@">re-ppc@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/ppc Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/ppc platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.grehan; <<a href="mailto:grehan@">grehan@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-sparc64">FreeBSD/sparc64 Release Engineering Team</a>
|
||||
<<a href="mailto:re-sparc64@">re-sparc64@</a>></h3>
|
||||
|
||||
<p>The FreeBSD/sparc64 Release Engineering Team is responsible for specific
|
||||
release issues related to the FreeBSD/sparc64 platform.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.jake; <<a href="mailto:jake@">jake@</a>></li>
|
||||
<li>&a.phk; <<a href="mailto:phk@">phk@</a>></li>
|
||||
<li>&a.tmm; <<a href="mailto:tmm@">tmm@</a>></li>
|
||||
<li>&a.obrien; <<a href="mailto:obrien@">obrien@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<h3><a name="t-donations">Donations Team</a>
|
||||
<<a href="mailto:donations@">donations@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Donations Team is responsible for responding to donations
|
||||
offers, establishing donation guidelines and procedures, and coordinating
|
||||
donation offers with the FreeBSD developer community. A more detailed
|
||||
description of the duties of the Donations Team is available on the <a
|
||||
href="donations/">FreeBSD Donations Liasion</a> page.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.wilko; <<a href="mailto:wilko@">wilko@</a>></li>
|
||||
<li>&a.brueffer; <<a href="mailto:brueffer@">brueffer@</a>></li>
|
||||
<li>&a.obrien; <<a href="mailto:obrien@">obrien@</a>></li>
|
||||
<li>&a.trhodes; <<a href="mailto:trhodes@">trhodes@</a>></li>
|
||||
<li>Daniel Seuffert <<a href="mailto:ds@">ds@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-marketing">Marketing Team</a>
|
||||
<<a href="mailto:marketing@">marketing@</a>></h3>
|
||||
|
||||
<p>Press contact, marketing, interviews, information.</p>
|
||||
|
||||
<ul>
|
||||
<li>Steven Beedle <<a
|
||||
href="mailto:steven@zna.com">steven@zna.com</a>></li>
|
||||
<li>Denise Ebery <<a
|
||||
href="mailto:denise@offmyserver.com">denise@offmyserver.com</a>></li>
|
||||
<li>Deb Goodkin <<a href="mailto:deb@">deb@</a>></li>
|
||||
<li>&a.jkoshy; <<a href="mailto:jkoshy@">jkoshy@</a>></li>
|
||||
<li>Dru Lavigne <<a
|
||||
href="mailto:dlavigne6@sympatico.ca">dlavigne6@sympatico.ca</a>></li>
|
||||
<li>&a.mwlucas; <<a href="mailto:mwlucas@">mwlucas@</a>></li>
|
||||
<li>&a.imp; <<a href="mailto:imp@">imp@</a>></li>
|
||||
<li>Kris Moore <<a
|
||||
href="mailto:kris@pcbsd.org">kris@pcbsd.org</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@">murray@</a>></li>
|
||||
<li>Matt Olander <<a href="mailto:matt@">matt@</a>></li>
|
||||
<li>Jeremy C. Reed <<a
|
||||
href="mailto:reed@reedmedia.net">reed@reedmedia.net</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<h3><a name="t-secteam">Security Team</a>
|
||||
<<a href="mailto:secteam@">secteam@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Security Team (headed by the Security Officer) is
|
||||
responsible for keeping the community aware of bugs, exploits and
|
||||
security risks affecting the FreeBSD src and ports trees, and to
|
||||
promote and distribute information needed to safely run FreeBSD
|
||||
systems. Furthermore, it is responsible for resolving software
|
||||
bugs affecting the security of FreeBSD and issuing security
|
||||
advisories. The <a href="security/charter.html">FreeBSD
|
||||
Security Officer Charter</a> describes the duties and
|
||||
responsibilities of the Security Officer in greater detail.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.mnag; <<a href="mailto:mnag@">mnag@</a>></li>
|
||||
<li>&a.remko; <<a href="mailto:remko@">remko@</a>></li>
|
||||
<li>&a.gnn; <<a href="mailto:gnn@">gnn@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>>
|
||||
(Officer Deputy)</li>
|
||||
<li>&a.philip; <<a href="mailto:philip@">philip@</a>></li>
|
||||
<li>&a.cperciva; <<a href="mailto:cperciva@">cperciva@</a>>
|
||||
(Officer)</li>
|
||||
<li>&a.csjp; <<a href="mailto:csjp@">csjp@</a>></li>
|
||||
<li>&a.des; <<a href="mailto:des@">des@</a>></li>
|
||||
<li>&a.nectar; <<a href="mailto:nectar@">nectar@</a>>
|
||||
(Officer Emeritus)</li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>>
|
||||
(Core Team Liasion)</li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<h3><a name="t-core-secretary">Core Team Secretary</a>
|
||||
<<a href="mailto:core-secretary@">core-secretary@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Core Team Secretary is a non-voting member of the Core Team,
|
||||
responsible for documenting the work done by core, keeping track of the
|
||||
core agenda, direct contact with non-core members sending mail to core
|
||||
and to be an the interface to the admin team for
|
||||
committer/account approval. The Core Team Secretary is also responsible
|
||||
for writing and sending out monthly status reports to the FreeBSD
|
||||
Developer community, containing a summary of core's latest decisions and
|
||||
actions.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.joel; <<a href="mailto:joel@">joel@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-portmgr-secretary">Port Management Team Secretary</a>
|
||||
<<a href="mailto:portmgr-secretary@">portmgr-secretary@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Port Management Team Secretary is a non-voting member of the
|
||||
Port Management Team, responsible for documenting the work done by portmgr,
|
||||
keeping track of voting procedures, and to be an interface to the other
|
||||
teams, especially the admin and Core teams. The Port Management Team
|
||||
Secretary is also responsible for writing and sending out monthly status
|
||||
reports to the FreeBSD Developer community, containing a summary of
|
||||
portmgr's latest decisions and actions.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.erwin; <<a href="mailto:erwin@">erwin@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-secteam-secretary">Security Team Secretary</a>
|
||||
<<a href="mailto:secteam-secretary@">secteam-secretary@</a>></h3>
|
||||
|
||||
<p>The FreeBSD Security Team Secretary will make sure someone responds to
|
||||
incoming emails towards the Security Team. He will acknowledge the
|
||||
recievement and keep track of the progress within the Security Team.
|
||||
If needed the Secretary will contact members of the Security Team to
|
||||
let them provide an update on ongoing items. Currently the Security
|
||||
Team Secretary does not handle Security Officer Team items.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.remko; <<a href="mailto:remko@">remko@</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
|
||||
<h3><a name="t-accounts">Accounts Team</a>
|
||||
<<a href="mailto:accounts@">accounts@</a>></h3>
|
||||
|
||||
<p>The Accounts Team is responsible for setting up accounts for new
|
||||
committers in the project. Requests for new accounts will not be
|
||||
acted upon without the proper approval from the appropriate entity.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.markm; <<a href="mailto:markm@">markm@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@">dhw@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-backups">Backups Administrators</a>
|
||||
<<a href="mailto:backups@">backups@</a>></h3>
|
||||
|
||||
<p>The Backups Administrators handles all backups on the FreeBSD cluster.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@">dhw@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-bugmeister">Bugmeisters & GNATS Administrators</a>
|
||||
<<a href="mailto:bugmeister@">bugmeister@</a>></h3>
|
||||
|
||||
<p>The Bugmeisters and GNATS Administrators are responsible for ensuring
|
||||
that the maintenance database is in working order, that the entries are
|
||||
correctly categorised and that there are no invalid entries. They are
|
||||
also responsible for the problem report group.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.ceri; <<a href="mailto:ceri@">ceri@</a>></li>
|
||||
<li>&a.linimon; <<a href="mailto:linimon@">linimon@</a>></li>
|
||||
<li>&a.remko; <<a href="mailto:remko@">remko@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-clusteradm">Cluster Administrators</a>
|
||||
<<a href="mailto:clusteradm@">clusteradm@</a>></h3>
|
||||
|
||||
<p>The Cluster Administrators consists of the people responsible for
|
||||
administrating the machines that the project relies on for its
|
||||
distributed work and communication to be synchronised. It
|
||||
consists mainly of those people who have physical access to the servers.
|
||||
Issues concerning the projects infrastructure or setting up new
|
||||
machines should be directed to the cluster admnistrators.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.billf; <<a href="mailto:billf@">billf@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
<li>&a.ps; <<a href="mailto:ps@">ps@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@">peter@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-dcvs">CVS doc/www Repository Managers</a>
|
||||
<<a href="mailto:dcvs@">dcvs@</a>></h3>
|
||||
|
||||
<p>The CVS doc/www Repository Managers are allowed to directly modify the
|
||||
repository without using the CVS tool. It is their responsibility to
|
||||
ensure that technical problems that arise in the repository are
|
||||
resolved quickly. The CVS source repository managers have the
|
||||
authority to back out commits if this is necessary to resolve a CVS
|
||||
technical problem. Repo-copy requests should be directed to the
|
||||
repository managers.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.joe; <<a href="mailto:joe@">joe@</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@">kuriyama@</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@">markm@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-pcvs">CVS ports Repository Managers</a>
|
||||
<<a href="mailto:pcvs@">pcvs@</a>></h3>
|
||||
|
||||
<p>The CVS ports Repository Managers are allowed to directly modify the
|
||||
repository without using the CVS tool. It is their responsibility to
|
||||
ensure that technical problems that arise in the repository are
|
||||
resolved quickly. The CVS source repository managers have the
|
||||
authority to back out commits if this is necessary to resolve a CVS
|
||||
technical problem. Repo-copy requests should be directed to the
|
||||
repository managers.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.marcus; <<a href="mailto:marcus@">marcus@</a>></li>
|
||||
<li>&a.joe; <<a href="mailto:joe@">joe@</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@">kuriyama@</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@">markm@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-ncvs">CVS src Repository Managers</a>
|
||||
<<a href="mailto:ncvs@">ncvs@</a>></h3>
|
||||
|
||||
<p>The CVS src Repository Managers are allowed to directly modify the
|
||||
repository without using the CVS tool. It is their responsibility to
|
||||
ensure that technical problems that arise in the repository are
|
||||
resolved quickly. The CVS source repository managers have the
|
||||
authority to back out commits if this is necessary to resolve a CVS
|
||||
technical problem. Repo-copy requests should be directed to the
|
||||
repository managers.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.joe; <<a href="mailto:joe@">joe@</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@">kuriyama@</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@">markm@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@">peter@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-cvsup-master">CVSup Mirror Site Coordinators</a>
|
||||
<<a href="mailto:cvsup-master@">cvsup-master@</a>></h3>
|
||||
|
||||
<p>The CVSup Mirror Site Coordinators coordinates all the CVSup
|
||||
mirror site adminstrators to ensure that they are distributing current
|
||||
versions of the software, that they have the capacity to update
|
||||
themselves when major updates are in progress, and making it easy for
|
||||
the general public to find their closest CVSup mirror.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@">kuriyama@</a>></li>
|
||||
<li>&a.jdp; <<a href="mailto:jdp@">jdp@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-dnsadm">DNS Administrators</a>
|
||||
<<a href="mailto:dnsadm@">dnsadm@</a>></h3>
|
||||
|
||||
<p>The DNS Administrators are responsible for managing DNS and related
|
||||
services.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.billf; <<a href="mailto:billf@">billf@</a>></li>
|
||||
<li>&a.dg; <<a href="mailto:dg@">dg@</a>></li>
|
||||
<li>&a.ps; <<a href="mailto:ps@">ps@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@">peter@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-mirror-admin">FTP/WWW Mirror Site Coordinators</a>
|
||||
<<a href="mailto:mirror-admin@">mirror-admin@</a>></h3>
|
||||
|
||||
<p>The FTP/WWW Mirror Site Coordinators coordinates all the FTP/WWW
|
||||
mirror site adminstrators to ensure that they are distributing current
|
||||
versions of the software, that they have the capacity to update
|
||||
themselves when major updates are in progress, and making it easy for
|
||||
the general public to find their closest FTP/WWW mirror.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@">kuriyama@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-perforce-admin">Perforce Repository Administrators</a>
|
||||
<<a href="mailto:perforce-admin@">perforce-admin@</a>></h3>
|
||||
|
||||
<p>The Perforce Repository Administrators are responsible for
|
||||
administrating the FreeBSD perforce source repository and setting up new
|
||||
perforce accounts. All requests concerning new perforce accounts
|
||||
for non-committers should be directed to the perforce
|
||||
administrators.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.scottl; <<a href="mailto:scottl@">scottl@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.gordon; <<a href="mailto:gordon@">gordon@</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@">rwatson@</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@">peter@</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@">dhw@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-postmaster">Postmaster Team</a>
|
||||
<<a href="mailto:postmaster@">postmaster@</a>></h3>
|
||||
|
||||
<p>The Postmaster Team is responsible for mail being correctly delivered
|
||||
to the committers' email address, ensuring that the mailing lists work,
|
||||
and should take measures against possible disruptions of projects mail
|
||||
services, such as having troll-, spam- and virus-filters.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.jmb; <<a href="mailto:jmb@">jmb@</a>></li>
|
||||
<li>&a.brd; <<a href="mailto:brd@">brd@</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@">dhw@</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-refadm">Reference Systems Administrators</a>
|
||||
<<a href="mailto:refadm@">refadm@</a>></h3>
|
||||
|
||||
<p>The Reference Systems Administrators are responsible for administrating,
|
||||
upgrading and maintaining the reference systems in the FreeBSD cluster.
|
||||
These systems are available to all FreeBSD committers.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.jake; <<a href="mailto:jake@">jake@</a>></li>
|
||||
<li>&a.billf; <<a href="mailto:billf@">billf@</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@">markm@</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@">simon@</a>></li>
|
||||
<li>&a.obrien; <<a href="mailto:obrien@">obrien@</a>></li>
|
||||
<li>&a.ps; <<a href="mailto:ps@">ps@</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@">kensmith@</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@">peter@</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@">dhw@</a>></li>
|
||||
</ul>
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: www/share/sgml/navibar.ent,v 1.4 2006/10/14 16:33:56 marcus Exp $ -->
|
||||
<!-- $FreeBSD: www/share/sgml/navibar.ent,v 1.5 2006/10/14 20:21:27 marcus Exp $ -->
|
||||
|
||||
<!ENTITY % navinclude.about "IGNORE">
|
||||
<![ %navinclude.about; [
|
||||
|
|
@ -13,6 +13,7 @@
|
|||
<li><a href="&base;/internet.html">Internetworking</a></li>
|
||||
<li><a href="&base;/advocacy/">Advocacy</a></li>
|
||||
<li><a href="&base;/marketing/">Marketing</a></li>
|
||||
<li><a href="&base;/administration.html">Administration</a></li>
|
||||
<li><a href="&base;/news/newsflash.html">News</a></li>
|
||||
<li><a href="&base;/events/events.html">Events</a></li>
|
||||
<li><a href="&base;/news/press.html">Press</a></li>
|
||||
|
|
|
|||
Loading…
Reference in a new issue