<?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>
<li><a href="#t-ports-secteam">Ports Security 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-doceng-secretary">Documentation Engineering
Team Secretary</a></li>
<li><a href="#t-portmgr-secretary">Port Management 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</a></li>
<li><a href="#t-clusteradm">Cluster Administrators</a></li>
<li><a href="#t-dnsadm">DNS Administrators</a></li>
<li><a href="#t-forum-admins">Forum Administrators</a></li>
<li><a href="#t-github-automation">GitHub Repository Mirror</a></li>
<li><a href="#t-jenkins-admin">Jenkins Continuous Integration
Testing Administrators</a></li>
<li><a href="#t-mirror-admin">FTP/WWW Mirror Site
Coordinators</a></li>
<li><a href="#t-phabric-admin">Phabricator Code Review
Administration</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>
<li><a href="#t-wiki">Wiki Admin 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.bapt.email; (Clusteradm Liaison)</li>
<li>&a.emaste.email; (GIT Transition WG and Security Team Liason)</li>
<li>&a.gnn.email; (Foundation Liaison)</li>
<li>&a.hrs.email; (Code-of-Conduct Committee Liaison)</li>
<li>&a.kevans.email; (Portmgr Team Liaison)</li>
<li>&a.markj.email; (Bugmeister and CI Team Liaison)</li>
<li>&a.scottl.email; (Release Engineering Team Liaison)</li>
<li>&a.seanc.email; (Doceng Team Liaison)</li>
<li>&a.imp.email; (GIT Transition WG Liaison)</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.bcr.email;</li>
<li>&a.hrs.email;</li>
<li>&a.ryusuke.email;</li>
<li>&a.0mp.email; (Secretary)</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.adamw.email;</li>
<li>&a.antoine.email;</li>
<li>&a.bapt.email; (Core Team Liaison)</li>
<li>&a.bdrewery.email; (Release Engineering Team Liaison)</li>
<li>&a.mat.email; (Cluster Administration Team Liaison)</li>
<li>&a.rene.email; (Secretary)</li>
<li>&a.swills.email;</li>
</ul>
<hr/>
<h3><a name="t-ports-secteam">FreeBSD Ports Security Team</a>
<<a href="mailto:ports-secteam@FreeBSD.org">ports-secteam@FreeBSD.org</a>></h3>
<p>The primary responsibility of the FreeBSD Port Security Team is
to provide rapid response to security incidents that affects the
FreeBSD ports collection and protect the FreeBSD user community
by keeping the community informed of bugs, exploits, popular
attacks, and other risks. More details are available on the
<a href="https://wiki.freebsd.org/ports-secteam">Wiki</a>
page.</p>
<ul>
<li>&a.fluffy.email;</li>
<li>&a.joneum.email;</li>
<li>&a.riggs.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.bdrewery.email;</li>
<li>&a.blackend.email;</li>
<li>&a.delphij.email;</li>
<li>&a.cperciva.email; (Deputy Lead)</li>
<li>&a.hrs.email;</li>
<li>&a.glebius.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.gahr.email;</li>
<li>&a.bhughes.email;</li>
<li>&a.adridg.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>Anne Dickison <<a
href="mailto:anne@freebsdfoundation.org">anne@freebsdfoundation.org</a>></li>
<li>&a.deb.email;</li>
<li>&a.dru.email;</li>
<li>&a.gnn.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.randi.email;</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.gordon.email; (Officer)</li>
<li>&a.delphij.email; (Officer Emeritus, Release Engineering Team
Liaison)</li>
<li>&a.des.email; (Officer Emeritus)</li>
<li>&a.gjb.email; (Cluster Administrators Team Liaison)</li>
<li>&a.emaste.email; (Officer Deputy)</li>
<li>&a.bz.email;</li>
<li>&a.gnn.email;</li>
<li>&a.markj.email;</li>
<li>&a.philip.email;</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 &os; 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, contacting non-core members on behalf of core, sending mail to core,
and interfacing with the admin team for committer/account approval. The Core
Team Secretary is also responsible for writing and sending out monthly status
reports to the &os; Developer community, containing a summary of core's latest
decisions and actions.</p>
<ul>
<li>&a.bofh.email;</li>
</ul>
<h3><a name="t-doceng-secretary">Documentation Engineering Team Secretary</a>
<<a href="mailto:doceng-secretary@FreeBSD.org">doceng-secretary@FreeBSD.org</a>></h3>
<p>The FreeBSD Documentation Engineering Team Secretary is a non-voting
member of the Documentation Engineering Team, responsible for documenting
the work done by doceng, keeping track of voting procedures, and to be an
interface to the other teams, especially the admin and Core teams.</p>
<ul>
<li>&a.0mp.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.rene.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>
<p>Email sent to the Accounts Team is currently forwarded to the <a
href="#t-clusteradm">Cluster Administrators</a>.</p>
<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>
<p>Email sent to the Backups Team is currently forwarded to the <a
href="#t-clusteradm">Cluster Administrators</a>.</p>
<h3><a name="t-bugmeister">Bugmeisters</a>
<<a href="mailto:bugmeister@FreeBSD.org">bugmeister@FreeBSD.org</a>></h3>
<p>The Bugmeisters are responsible for ensuring that the problem report
software is in working order, that the entries are correctly categorised
and that there are no invalid entries.</p>
<ul>
<li>&a.eadler.email;</li>
<li>&a.mva.email;</li>
<li>&a.gavin.email;</li>
<li>&a.koobs.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
maintaing the machines and services that the project relies on for its
distributed work and communication. Issues concerning the projects
infrastructure or setting up new machines should be directed to them.
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.allanjude.email;</li>
<li>&a.brd.email;</li>
<li>&a.dhw.email;</li>
<li>&a.gavin.email;</li>
<li>&a.gjb.email;</li>
<li>&a.lwhsu.email;</li>
<li>&a.peter.email;</li>
<li>&a.sbruno.email;</li>
<li>&a.simon.email;</li>
<li>&a.zi.email; (Lead)</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>
<p>E-mail to the DNS Administrators is currently forwarded to the <a
href="#t-clusteradm">Cluster Administrators</a>.</p>
<h3><a name="t-forum-admins">&os; Forum Administrators</a>
<<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>></h3>
<p>The Forum Administrators maintain the &os; Project's Internet forum,
located at <a href="https://forums.freebsd.org/">https://forums.freebsd.org/</a>
and lead the group of moderators who work to ensure the relevance and quality of
the forum's content.</p>
<ul>
<li>&a.brd.email;</li>
<li>&a.danger.email;</li>
<li>&a.dutchdaemon.email;</li>
<li>&a.lme.email;</li>
<li>&a.wblock.email;</li>
</ul>
<h3><a name="t-github-automation">Repository Automated Mirroring to GitHub
Coordinators</a> <<a href="mailto:github-automation@FreeBSD.org"
>github-automation@FreeBSD.org</a>></h3>
<p>The GitHub Automation team oversees the export of &os; source
code repository content to the read-only repository instances on
GitHub</p>
<ul>
<li>&a.koobs.email;</li>
<li>&a.mva.email;</li>
<li>&a.robak.email;</li>
<li>&a.rodrigc.email;</li>
<li>&a.uqs.email;</li>
</ul>
<h3><a name="t-jenkins-admin">Jenkins Continuous Integration Testing
Administrators</a> <<a href="mailto:jenkins-admin@FreeBSD.org"
>jenkins-admin@FreeBSD.org</a>></h3>
<p>The Jenkins Administrators maintain the Continuous Integration and
testing infrastructure for The &os; Project. This includes maintaining
the Jenkins instance and the jobs that run builds and execute tests.</p>
<ul>
<li>&a.bapt.email;</li>
<li>&a.brd.email;</li>
<li>&a.brooks.email;</li>
<li>&a.lwhsu.email;</li>
<li>&a.markj.email; (Core Team Liaison)</li>
<li>&a.seanc.email;</li>
<li>&a.swills.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 administrators 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>
<p>E-mail to the Mirror Site Coordinators is currently forwarded to
the <a href="#t-clusteradm">Cluster Administrators</a> with the
addition of:</p>
<ul>
<li>&a.kuriyama.email;</li>
</ul>
<h3><a name="t-phabric-admin">Phabricator Code Review Application
Administrators</a> <<a href="mailto:phabric-admin@FreeBSD.org"
>phabric-admin@FreeBSD.org</a>></h3>
<p>The Phabricator Administrators are responsible for maintaining the &os;'s
instance of the Phabricator on-line code review tool located at
<a href="https://reviews.freebsd.org/">https://reviews.freebsd.org/</a></p>
<ul>
<li>&a.allanjude.email;</li>
<li>&a.bofh.email;</li>
<li>&a.eadler.email;</li>
<li>&a.emaste.email;</li>
<li>&a.jtl.email;</li>
<li>&a.lwhsu.email;</li>
<li>&a.mat.email;</li>
<li>&a.miwi.email;</li>
<li>&a.pi.email;</li>
</ul>
<p>For any problems regarding Phabricator, please <a
href="https://bugs.freebsd.org/submit/">open a bug report</a>
and select "Services" and then "Code Review".</p>
<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.krion.email;</li>
<li>&a.ler.email;</li>
<li>&a.philip.email;</li>
<li>&a.pi.email;</li>
<li>&a.rea.email;</li>
<li>&a.zi.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>
<p>Email to the Subversion Administration team is currently
forwarded to the <a href="#t-clusteradm">Cluster Administrators</a>.</p>
<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>
<p>Email to the Webmaster Team is currently forwarded to the <a
href="#t-doceng">Documentation Engineering</a> team with the
addition of:</p>
<ul>
<li>&a.wosch.email;</li>
</ul>
<h3><a name="t-wiki">Wiki Admin Team</a>
<<a href="mailto:wiki-admin@FreeBSD.org">wiki-admin@FreeBSD.org</a>></h3>
<p>The FreeBSD Wiki Team is responsible for keeping the FreeBSD
<a href="https://wiki.FreeBSD.org/">Wiki</a>
site up and running. They also shape the overall design and
content structure.</p>
<ul>
<li>&a.gavin.email;</li>
<li>&a.linimon.email;</li>
<li>&a.theraven.email;</li>
<li>&a.koobs.email;</li>
</ul>
</body>
</html>
