Remove administration.sgml, incorrectly copied back into the repo with
r39796. Submitted by: ryusuke
This commit is contained in:
Glen Barber
parent
6059052018
commit
b3df6c4acf
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39847
1 changed files with 0 additions and 499 deletions
|
|
@ -1,499 +0,0 @@
|
|||
<?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/doc/share/sgml/xhtml10-freebsd.dtd" [
|
||||
<!ENTITY title "FreeBSD Project Administration and Management">
|
||||
]>
|
||||
|
||||
<html xmlns="http://www.w3.org/1999/xhtml">
|
||||
<head>
|
||||
<title>&title;</title>
|
||||
|
||||
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
|
||||
</head>
|
||||
|
||||
<body class="navinclude.about">
|
||||
|
||||
<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-builder">Builders 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>
|
||||
<li><a href="#t-vendor">Vendor Relations</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-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-webmaster">Webmaster Team</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<hr/>
|
||||
|
||||
<h3><a name="t-core">FreeBSD Core Team</a>
|
||||
<<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</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.tabthorpe; <<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>></li>
|
||||
<li>&a.gavin; <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>></li>
|
||||
<li>&a.jhb; <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>></li>
|
||||
<li>&a.kib; <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>></li>
|
||||
<li>&a.theraven; <<a href="mailto:theraven@FreeBSD.org">theraven@FreeBSD.org</a>></li>
|
||||
<li>&a.attilio; <<a href="mailto:attilio@FreeBSD.org">attilio@FreeBSD.org</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></li>
|
||||
<li>&a.miwi; <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-doceng">FreeBSD Documentation Engineering Team</a>
|
||||
<<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</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.gjb; <<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>></li>
|
||||
<li>&a.blackend; <<a href="mailto:blackend@FreeBSD.org">blackend@FreeBSD.org</a>></li>
|
||||
<li>&a.gabor; <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-portmgr">FreeBSD Port Management Team</a>
|
||||
<<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</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.tabthorpe; <<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>></li>
|
||||
<li>&a.marcus; <<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>></li>
|
||||
<li>&a.bapt; <<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>></li>
|
||||
<li>&a.beat; <<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>></li>
|
||||
<li>&a.erwin; <<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>></li>
|
||||
<li>&a.linimon; <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>></li>
|
||||
<li>&a.pav; <<a href="mailto:pav@FreeBSD.org">pav@FreeBSD.org</a>></li>
|
||||
<li>&a.itetcu; <<a href="mailto:itetcu@FreeBSD.org">itetcu@FreeBSD.org</a>></li>
|
||||
<li>&a.miwi; <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr/>
|
||||
|
||||
<h3><a name="t-re">Primary Release Engineering Team</a>
|
||||
<<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</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 <code>RELENG_*</code> 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.kib; <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>></li>
|
||||
<li>&a.blackend; <<a href="mailto:blackend@FreeBSD.org">blackend@FreeBSD.org</a>></li>
|
||||
<li>&a.jpaetzel; <<a href="mailto:jpaetzel@FreeBSD.org">jpaetzel@FreeBSD.org</a>></li>
|
||||
<li>&a.hrs; <<a href="mailto:hrs@FreeBSD.org">hrs@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>>
|
||||
(Lead)</li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-re-builder">Builders Release Engineering Team</a>
|
||||
<<a href="mailto:re-builder@FreeBSD.org">re-builder@FreeBSD.org</a>></h3>
|
||||
|
||||
<p>The builders release engineering team is responsible
|
||||
for building and packaging FreeBSD releases on the various supported
|
||||
platforms.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.marcel; <<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>></li>
|
||||
<li>&a.nyan; <<a href="mailto:nyan@FreeBSD.org">nyan@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr/>
|
||||
|
||||
<h3><a name="t-donations">Donations Team</a>
|
||||
<<a href="mailto:donations@FreeBSD.org">donations@FreeBSD.org</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 Liaison</a> page.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.gjb; <<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>></li>
|
||||
<li>&a.wilko; <<a href="mailto:wilko@FreeBSD.org">wilko@FreeBSD.org</a>></li>
|
||||
<li>&a.gahr; <<a href="mailto:gahr@FreeBSD.org">gahr@FreeBSD.org</a>></li>
|
||||
<li>&a.pgollucci; <<a href="mailto:pgolluci@FreeBSD.org">pgolluci@FreeBSD.org</a>></li>
|
||||
<li>&a.skreuzer; <<a href="mailto:skreuzer@FreeBSD.org">skreuzer@FreeBSD.org</a>></li>
|
||||
<li>&a.obrien; <<a href="mailto:obrien@FreeBSD.org">obrien@FreeBSD.org</a>></li>
|
||||
<li>&a.trhodes; <<a href="mailto:trhodes@FreeBSD.org">trhodes@FreeBSD.org</a>></li>
|
||||
<li>Daniel Seuffert <<a href="mailto:ds@FreeBSD.org">ds@FreeBSD.org</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-marketing">Marketing Team</a>
|
||||
<<a href="mailto:marketing@FreeBSD.org">marketing@FreeBSD.org</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@ixsystems.com">denise@ixsystems.com</a>></li>
|
||||
<li>Deb Goodkin <<a href="mailto:deb@FreeBSD.org">deb@FreeBSD.org</a>></li>
|
||||
<li>&a.jkoshy; <<a href="mailto:jkoshy@FreeBSD.org">jkoshy@FreeBSD.org</a>></li>
|
||||
<li>Dru Lavigne <<a
|
||||
href="mailto:dlavigne6@sympatico.ca">dlavigne6@sympatico.ca</a>></li>
|
||||
<li>&a.mwlucas; <<a href="mailto:mwlucas@FreeBSD.org">mwlucas@FreeBSD.org</a>></li>
|
||||
<li>&a.imp; <<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>></li>
|
||||
<li>Kris Moore <<a
|
||||
href="mailto:kris@pcbsd.org">kris@pcbsd.org</a>></li>
|
||||
<li>&a.murray; <<a href="mailto:murray@FreeBSD.org">murray@FreeBSD.org</a>></li>
|
||||
<li>Matt Olander <<a href="mailto:matt@FreeBSD.org">matt@FreeBSD.org</a>></li>
|
||||
<li>Jeremy C. Reed <<a
|
||||
href="mailto:reed@reedmedia.net">reed@reedmedia.net</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<h3><a name="t-secteam">Security Team</a>
|
||||
<<a href="mailto:secteam@FreeBSD.org">secteam@FreeBSD.org</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.bz; <<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>></li>
|
||||
<li>&a.cperciva; <<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>></li>
|
||||
<li>&a.csjp; <<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>></li>
|
||||
<li>&a.delphij; <<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>></li>
|
||||
<li>&a.miwi; <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>></li>
|
||||
<li>&a.philip; <<a href="mailto:philip@FreeBSD.org">philip@FreeBSD.org</a>></li>
|
||||
<li>&a.qingli; <<a href="mailto:qingli@FreeBSD.org">qingli@FreeBSD.org</a>></li>
|
||||
<li>&a.remko; <<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>>
|
||||
(Officer)</li>
|
||||
<li>&a.stas; <<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-vendor">Vendor Relations</a>
|
||||
<<a href="mailto:vendor-relations@FreeBSD.org">vendor-relations@FreeBSD.org</a>></h3>
|
||||
|
||||
<p>Vendor Relations is responsible for handling email
|
||||
from hardware and software vendors. Email sent to Vendor
|
||||
Relations is forwarded to the &os; Core Team in addition
|
||||
to the &os; Foundation.</p>
|
||||
|
||||
<hr/>
|
||||
|
||||
<h3><a name="t-core-secretary">Core Team Secretary</a>
|
||||
<<a href="mailto:core-secretary@FreeBSD.org">core-secretary@FreeBSD.org</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.pgj; <<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-portmgr-secretary">Port Management Team Secretary</a>
|
||||
<<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</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.tabthorpe; <<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-secteam-secretary">Security Team Secretary</a>
|
||||
<<a href="mailto:secteam-secretary@FreeBSD.org">secteam-secretary@FreeBSD.org</a>></h3>
|
||||
|
||||
<p>The FreeBSD Security Team Secretary will make sure someone responds to
|
||||
incoming emails towards the Security Team. He will acknowledge
|
||||
receipt 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@FreeBSD.org">remko@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<hr/>
|
||||
|
||||
<h3><a name="t-accounts">Accounts Team</a>
|
||||
<!-- admins mail aliases intentionally left incomplete -->
|
||||
<accounts@></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@FreeBSD.org">markm@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-backups">Backups Administrators</a>
|
||||
<!-- admins mail aliases intentionally left incomplete -->
|
||||
<backups@></h3>
|
||||
|
||||
<p>The Backups Administrators handle all backups on the FreeBSD cluster.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-bugmeister">Bugmeisters & GNATS Administrators</a>
|
||||
<<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</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.eadler; < <a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>></li>
|
||||
<li>&a.gavin; <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>></li>
|
||||
<li>&a.gonzo; <<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>></li>
|
||||
<li>&a.linimon; <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-clusteradm">Cluster Administrators</a>
|
||||
<!-- admins mail aliases intentionally left incomplete -->
|
||||
<clusteradm@></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 administrators.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.brd; <<a href="mailto:brd@FreeBSD.org">brd@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
<li>&a.ps; <<a href="mailto:ps@FreeBSD.org">ps@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-pcvs">CVS ports Repository Managers</a>
|
||||
<<a href="mailto:pcvs@FreeBSD.org">pcvs@FreeBSD.org</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 ports 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@FreeBSD.org">marcus@FreeBSD.org</a>></li>
|
||||
<li>&a.joe; <<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-ncvs">CVS src Repository Managers</a>
|
||||
<<a href="mailto:ncvs@FreeBSD.org">ncvs@FreeBSD.org</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@FreeBSD.org">joe@FreeBSD.org</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>></li>
|
||||
<li>&a.markm; <<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-cvsup-master">CVSup Mirror Site Coordinators</a>
|
||||
<<a href="mailto:cvsup-master@FreeBSD.org">cvsup-master@FreeBSD.org</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@FreeBSD.org">kuriyama@FreeBSD.org</a>></li>
|
||||
<li>&a.jdp; <<a href="mailto:jdp@FreeBSD.org">jdp@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-dnsadm">DNS Administrators</a>
|
||||
<!-- admins mail aliases intentionally left incomplete -->
|
||||
<dnsadm@></h3>
|
||||
|
||||
<p>The DNS Administrators are responsible for managing DNS and related
|
||||
services.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.dg; <<a href="mailto:dg@FreeBSD.org">dg@FreeBSD.org</a>></li>
|
||||
<li>&a.ps; <<a href="mailto:ps@FreeBSD.org">ps@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-mirror-admin">FTP/WWW Mirror Site Coordinators</a>
|
||||
<<a href="mailto:mirror-admin@FreeBSD.org">mirror-admin@FreeBSD.org</a>></h3>
|
||||
|
||||
<p>The FTP/WWW Mirror Site Coordinators coordinate 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@FreeBSD.org">kuriyama@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-perforce-admin">Perforce Repository Administrators</a>
|
||||
<<a href="mailto:perforce-admin@FreeBSD.org">perforce-admin@FreeBSD.org</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@FreeBSD.org">scottl@FreeBSD.org</a>></li>
|
||||
<li>&a.kensmith; <<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>></li>
|
||||
<li>&a.gordon; <<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>></li>
|
||||
<li>&a.rwatson; <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>></li>
|
||||
<li>&a.peter; <<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-postmaster">Postmaster Team</a>
|
||||
<<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</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 project mail
|
||||
services, such as having troll-, spam- and virus-filters.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.jmb; <<a href="mailto:jmb@FreeBSD.org">jmb@FreeBSD.org</a>></li>
|
||||
<li>&a.brd; <<a href="mailto:brd@FreeBSD.org">brd@FreeBSD.org</a>></li>
|
||||
<li>&a.sahil; <<a href="mailto:sahil@FreeBSD.org">sahil@FreeBSD.org</a>></li>
|
||||
<li>&a.dhw; <<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
<h3><a name="t-webmaster">Webmaster Team</a>
|
||||
<<a href="mailto:webmaster@FreeBSD.org">webmaster@FreeBSD.org</a>></h3>
|
||||
|
||||
<p>The FreeBSD Webmaster Team is responsible for keeping the main FreeBSD web
|
||||
sites up and running. This means web server configuration, CGI scripts,
|
||||
fulltext and mailing list search. Anything web related, technical stuff
|
||||
belongs to the scope of the Webmaster Team, excluding bugs in the
|
||||
documentation.</p>
|
||||
|
||||
<ul>
|
||||
<li>&a.nik; <<a href="mailto:nik@FreeBSD.org">nik@FreeBSD.org</a>></li>
|
||||
<li>&a.kuriyama; <<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>></li>
|
||||
<li>&a.simon; <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>></li>
|
||||
<li>&a.jesusr; <<a href="mailto:jesusr@FreeBSD.org">jesusr@FreeBSD.org</a>></li>
|
||||
<li>&a.wosch; <<a href="mailto:wosch@FreeBSD.org">wosch@FreeBSD.org</a>></li>
|
||||
</ul>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in a new issue