0aa9205b79
to rotate another re@ member into this role. Update the administration page to reflect I will now wear the Release Engineering Team Lead hat. Many thanks to Ken for his many years in this role, and his continued service as an active member on the re@ team. Approved by: core Sponsored by: The FreeBSD Foundation
492 lines
18 KiB
XML
492 lines
18 KiB
XML
<?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/share/xml/xhtml10-freebsd.dtd" [
|
|
<!ENTITY title "FreeBSD Project Administration and Management">
|
|
]>
|
|
|
|
<!-- NOTE: If any alias listed on this page is modified in the
|
|
/etc/aliases on the FreeBSD project's mail server,
|
|
then this page must be updated. -->
|
|
|
|
<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-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-subversion">Subversion Administrators</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.email; (Donations Team, Port Management Team Liaison)</li>
|
|
<li>&a.gavin.email; (Security Team Liaison)</li>
|
|
<li>&a.jhb.email;</li>
|
|
<li>&a.kib.email;</li>
|
|
<li>&a.theraven.email; (&os; Foundation Liaison)</li>
|
|
<li>&a.hrs.email;</li>
|
|
<li>&a.peter.email;</li>
|
|
<li>&a.miwi.email;</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.email;</li>
|
|
<li>&a.wblock.email;</li>
|
|
<li>&a.blackend.email;</li>
|
|
<li>&a.gabor.email;</li>
|
|
<li>&a.hrs.email;</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.email; (Core Team Liaison)</li>
|
|
<li>&a.mat.email;</li>
|
|
<li>&a.antoine.email;</li>
|
|
<li>&a.bapt.email;</li>
|
|
<li>&a.bdrewery.email; (Release Engineering Team Liaison)</li>
|
|
<li>&a.decke.email;</li>
|
|
<li>&a.erwin.email; (Cluster Administration Team Liaison)</li>
|
|
<li>&a.miwi.email;</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.gjb.email; (Lead)</li>
|
|
<li>&a.kib.email;</li>
|
|
<li>&a.joel.email;</li>
|
|
<li>&a.blackend.email;</li>
|
|
<li>&a.skreuzer.email;</li>
|
|
<li>&a.delphij.email;</li>
|
|
<li>&a.jpaetzel.email;</li>
|
|
<li>&a.rodrigc.email;</li>
|
|
<li>&a.hrs.email;</li>
|
|
<li>&a.glebius.email;</li>
|
|
<li>&a.kensmith.email;</li>
|
|
<li>&a.marius.email;</li>
|
|
</ul>
|
|
|
|
<h3><a name="t-re-builder">Builders Release Engineering Team</a>
|
|
<<a href="mailto:re-builders@FreeBSD.org">re-builders@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.email;</li>
|
|
<li>&a.nyan.email;</li>
|
|
<li>&a.nwhitehorn.email;</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.tabthorpe.email; (Core Team Liaison)</li>
|
|
<li>&a.gjb.email;</li>
|
|
<li>&a.gahr.email;</li>
|
|
<li>&a.pgollucci.email;</li>
|
|
<li>&a.skreuzer.email;</li>
|
|
<li>&a.obrien.email;</li>
|
|
<li>&a.trhodes.email;</li>
|
|
<li>&a.ds.email;</li>
|
|
<li>&a.rwatson.email;</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>&a.deb.email;</li>
|
|
<li>&a.jkoshy.email;</li>
|
|
<li>&a.dru.email;</li>
|
|
<li>&a.mwlucas.email;</li>
|
|
<li>&a.imp.email;</li>
|
|
<li>&a.kmoore.email;</li>
|
|
<li>&a.murray.email;</li>
|
|
<li>&a.matt.email;</li>
|
|
<li>Jeremy C. Reed <<a
|
|
href="mailto:reed@reedmedia.net">reed@reedmedia.net</a>></li>
|
|
<li>&a.rwatson.email;</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.benl.email;</li>
|
|
<li>&a.cperciva.email; (Officer Emeritus)</li>
|
|
<li>&a.csjp.email;</li>
|
|
<li>&a.delphij.email; (Officer Deputy)</li>
|
|
<li>&a.des.email; (Officer)</li>
|
|
<li>&a.gavin.email; (Core Team Liaison)</li>
|
|
<li>&a.jonathan.email;</li>
|
|
<li>&a.philip.email;</li>
|
|
<li>&a.qingli.email;</li>
|
|
<li>&a.remko.email;</li>
|
|
<li>&a.rwatson.email;</li>
|
|
<li>&a.simon.email; (Officer Emeritus)</li>
|
|
<li>&a.stas.email;</li>
|
|
<li>&a.trasz.email; (Secretary)</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.email;</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.email;</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.trasz.email;</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.simon.email;</li>
|
|
<li>&a.dhw.email;</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.email;</li>
|
|
<li>&a.dhw.email;</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.email;</li>
|
|
<li>&a.gavin.email;</li>
|
|
<li>&a.gonzo.email;</li>
|
|
</ul>
|
|
|
|
<h3><a name="t-clusteradm">Cluster Administrators</a>
|
|
<!-- admins mail aliases intentionally left incomplete -->
|
|
<admins@></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. This
|
|
team is led by the lead cluster administrator whose duties and
|
|
responsbilities are described in the <a
|
|
href="internal/clusteradm.html">cluster administration charter</a>
|
|
in greater detail.</p>
|
|
|
|
<ul>
|
|
<li>&a.bhaga.email;</li>
|
|
<li>&a.brd.email;</li>
|
|
<li>&a.bz.email;</li>
|
|
<li>&a.gavin.email;</li>
|
|
<li>&a.gjb.email;</li>
|
|
<li>&a.kensmith.email;</li>
|
|
<li>&a.peter.email; (Lead)</li>
|
|
<li>&a.sbruno.email;</li>
|
|
<li>&a.simon.email;</li>
|
|
<li>&a.zi.email;</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.email;</li>
|
|
<li>&a.kensmith.email;</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.gjb.email;</li>
|
|
<li>&a.brd.email;</li>
|
|
<li>&a.simon.email;</li>
|
|
<li>&a.zi.email;</li>
|
|
<li>&a.peter.email;</li>
|
|
<li>&a.bz.email;</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.brd.email;</li>
|
|
<li>&a.kuriyama.email;</li>
|
|
<li>&a.simon.email;</li>
|
|
<li>&a.kensmith.email;</li>
|
|
<li>&a.bz.email;</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.gibbs.email;</li>
|
|
<li>&a.kensmith.email;</li>
|
|
<li>&a.gordon.email;</li>
|
|
<li>&a.rwatson.email;</li>
|
|
<li>&a.peter.email;</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.email;</li>
|
|
<li>&a.brd.email;</li>
|
|
<li>&a.flo.email;</li>
|
|
<li>&a.sahil.email;</li>
|
|
<li>&a.dhw.email;</li>
|
|
</ul>
|
|
|
|
<h3><a name="t-subversion">Subversion Administrators</a> <svnadm@></h3>
|
|
|
|
<p>The FreeBSD Subversion team is responsible for maintaining the health of
|
|
the Subversion Repositories.</p>
|
|
|
|
<ul>
|
|
<li>&a.bz.email;</li>
|
|
<li>&a.peter.email;</li>
|
|
<li>&a.simon.email;</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 appointed by &os; Documentation Engineering Team,
|
|
and 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.gjb.email;</li>
|
|
<li>&a.wblock.email;</li>
|
|
<li>&a.blackend.email;</li>
|
|
<li>&a.gabor.email;</li>
|
|
<li>&a.hrs.email;</li>
|
|
<li>&a.wosch.email;</li>
|
|
</ul>
|
|
|
|
</body>
|
|
</html>
|