=============================================
FreeBSD Project Administration and Management
=============================================

.. raw:: html

   <div id="containerwrap">

.. raw:: html

   <div id="container">

.. raw:: html

   <div id="content">

.. raw:: html

   <div id="sidewrap">

.. raw:: html

   <div id="sidenav">

Section Navigation
------------------

-  `About <./about.html>`__
-  `Features <./features.html>`__
-  `Applications <./applications.html>`__
-  `Advocacy <./advocacy/>`__
-  `Marketing <./marketing/>`__
-  `Administration <./administration.html>`__
-  `News <./news/newsflash.html>`__
-  `Events <./events/events.html>`__
-  `Press <./news/press.html>`__
-  `Multimedia <./multimedia/multimedia.html>`__
-  `Artwork <./art.html>`__
-  `Logo <./logo.html>`__
-  `Donations <./donations/>`__
-  `Legal Notices <./copyright/>`__
-  `Privacy Policy <./privacy.html>`__

.. raw:: html

   </div>

.. raw:: html

   </div>

.. raw:: html

   <div id="contentwrap">

FreeBSD Project Administration and Management
=============================================

Introduction
------------

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.

-  Project Management

   -  `Core Team <#t-core>`__
   -  `Documentation Engineering Team <#t-doceng>`__
   -  `Port Management Team <#t-portmgr>`__

-  Release Engineering

   -  `Primary Release Engineering Team <#t-re>`__
   -  `Builders Release Engineering Team <#t-re-builder>`__

-  Teams

   -  `Donations Team <#t-donations>`__
   -  `Marketing Team <#t-marketing>`__
   -  `Security Team <#t-secteam>`__
   -  `Vendor Relations <#t-vendor>`__

-  Secretaries

   -  `Core Team Secretary <#t-core-secretary>`__
   -  `Port Management Team Secretary <#t-portmgr-secretary>`__
   -  `Security Team Secretary <#t-secteam-secretary>`__

-  Internal Administration

   -  `Accounts Team <#t-accounts>`__
   -  `Backup Administrators <#t-backups>`__
   -  `Bugmeisters <#t-bugmeister>`__
   -  `Cluster Administrators <#t-clusteradm>`__
   -  `DNS Administrators <#t-dnsadm>`__
   -  `Forum Administrators <#t-forum-admins>`__
   -  `GitHub Repository Mirror <#t-github-automation>`__
   -  `Jenkins Continuous Integration Testing
      Administrators <#t-jenkins-admin>`__
   -  `FTP/WWW Mirror Site Coordinators <#t-mirror-admin>`__
   -  `Perforce Repository Administrators <#t-perforce-admin>`__
   -  `Phabricator Code Review Administration <#t-phabric-admin>`__
   -  `Postmaster Team <#t-postmaster>`__
   -  `Subversion Administrators <#t-subversion>`__
   -  `Webmaster Team <#t-webmaster>`__

--------------

FreeBSD Core Team <core@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Gavin Atkinson <gavin@FreeBSD.org\ >
-  David Chisnall <theraven@FreeBSD.org\ >
-  Baptiste Daroussin <bapt@FreeBSD.org\ >
-  Ed Maste <emaste@FreeBSD.org\ >
-  George V. Neville-Neil <gnn@FreeBSD.org\ >
-  Hiroki Sato <hrs@FreeBSD.org\ >
-  Gleb Smirnoff <glebius@FreeBSD.org\ >
-  Robert Watson <rwatson@FreeBSD.org\ >
-  Peter Wemm <peter@FreeBSD.org\ >

FreeBSD Documentation Engineering Team <doceng@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The FreeBSD Documentation Engineering Team is responsible for defining
and following up documentation goals for the committers in the
Documentation project. The `doceng team
charter <internal/doceng.html>`__ describes the duties and
responsibilities of the Documentation Engineering Team in greater
detail.

-  Glen Barber <gjb@FreeBSD.org\ >
-  Warren Block <wblock@FreeBSD.org\ >
-  Marc Fonvieille <blackend@FreeBSD.org\ >
-  G?bor K?vesd?n <gabor@FreeBSD.org\ >
-  Hiroki Sato <hrs@FreeBSD.org\ >

FreeBSD Port Management Team <portmgr@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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 `portmgr team
charter <portmgr/charter.html>`__ describes the duties and
responsibilities of the Port Management Team in greater detail.

-  Mathieu Arnold <mat@FreeBSD.org\ >
-  Antoine Brodin <antoine@FreeBSD.org\ >
-  Baptiste Daroussin <bapt@FreeBSD.org\ > (Core Team Liaison)
-  Bryan Drewery <bdrewery@FreeBSD.org\ > (Release Engineering Team
   Liaison)
-  Erwin Lansing <erwin@FreeBSD.org\ > (Cluster Administration Team
   Liaison)
-  Steve Wills <swills@FreeBSD.org\ >

--------------

Primary Release Engineering Team <re@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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 `release engineering team
charter <releng/charter.html>`__ describes the duties and
responsibilities of the Primary Release Engineering Team in greater
detail.

-  Glen Barber <gjb@FreeBSD.org\ > (Lead)
-  Konstantin Belousov <kib@FreeBSD.org\ >
-  Marc Fonvieille <blackend@FreeBSD.org\ >
-  Xin Li <delphij@FreeBSD.org\ >
-  Remko Lodder <remko@FreeBSD.org\ > (Security Team Liaison)
-  Craig Rodrigues <rodrigc@FreeBSD.org\ >
-  Hiroki Sato <hrs@FreeBSD.org\ >
-  Gleb Smirnoff <glebius@FreeBSD.org\ >
-  Marius Strobl <marius@FreeBSD.org\ >
-  Robert Watson <rwatson@FreeBSD.org\ >

Builders Release Engineering Team <re-builders@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The builders release engineering team is responsible for building and
packaging FreeBSD releases on the various supported platforms.

-  Marcel Moolenaar <marcel@FreeBSD.org\ >
-  Yoshihiro Takahashi <nyan@FreeBSD.org\ >
-  Nathan Whitehorn <nwhitehorn@FreeBSD.org\ >

--------------

Donations Team <donations@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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 `FreeBSD Donations Liaison <donations/>`__ page.

-  Glen Barber <gjb@FreeBSD.org\ >
-  Pietro Cerutti <gahr@FreeBSD.org\ >
-  Philip M. Gollucci <pgollucci@FreeBSD.org\ >
-  Steven Kreuzer <skreuzer@FreeBSD.org\ >
-  David O'Brien <obrien@FreeBSD.org\ >
-  Tom Rhodes <trhodes@FreeBSD.org\ >
-  Daniel Seuffert <ds@FreeBSD.org\ >
-  Robert Watson <rwatson@FreeBSD.org\ >

Marketing Team <marketing@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Press contact, marketing, interviews, information.

-  Steven Beedle <steven@zna.com\ >
-  Anne Dickison <anne@freebsdfoundation.org\ >
-  Deb Goodkin <deb@FreeBSD.org\ >
-  Dru Lavigne <dru@FreeBSD.org\ >
-  George V. Neville-Neil <gnn@FreeBSD.org\ >
-  Michael W. Lucas <mwlucas@FreeBSD.org\ >
-  Warner Losh <imp@FreeBSD.org\ >
-  Kris Moore <kmoore@FreeBSD.org\ >
-  Murray Stokely <murray@FreeBSD.org\ >
-  Matt Olander <matt@FreeBSD.org\ >
-  Jeremy C. Reed <reed@reedmedia.net\ >
-  Randi Harper <randi@FreeBSD.org\ >
-  Robert Watson <rwatson@FreeBSD.org\ >

Security Team <secteam@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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 `FreeBSD
Security Officer Charter <security/charter.html>`__ describes the duties
and responsibilities of the Security Officer in greater detail.

-  Ben Laurie <benl@FreeBSD.org\ >
-  Colin Percival <cperciva@FreeBSD.org\ > (Officer Emeritus)
-  Christian S.J. Peron <csjp@FreeBSD.org\ >
-  Xin Li <delphij@FreeBSD.org\ > (Officer)
-  Dag-Erling C. Sm?rgrav <des@FreeBSD.org\ > (Officer Emeritus)
-  Gavin Atkinson <gavin@FreeBSD.org\ > (Core Team Liaison)
-  Glen Barber <gjb@FreeBSD.org\ > (Cluster Administrators Team Liaison)
-  Gleb Smirnoff <glebius@FreeBSD.org\ > (Officer Deputy)
-  Warner Losh <imp@FreeBSD.org\ > (Officer Emeritus)
-  Jonathan Anderson <jonathan@FreeBSD.org\ >
-  Philip Paeps <philip@FreeBSD.org\ >
-  Qing Li <qingli@FreeBSD.org\ >
-  Remko Lodder <remko@FreeBSD.org\ > (Secretary)
-  Robert Watson <rwatson@FreeBSD.org\ > (Officer Emeritus)
-  Simon L. B. Nielsen <simon@FreeBSD.org\ > (Officer Emeritus)
-  Stanislav Sedov <stas@FreeBSD.org\ >
-  Edward Tomasz Napierala <trasz@FreeBSD.org\ >

Vendor Relations <vendor-relations@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Vendor Relations is responsible for handling email from hardware and
software vendors. Email sent to Vendor Relations is forwarded to the
FreeBSD?Core Team in addition to the FreeBSD?Foundation.

--------------

Core Team Secretary <core-secretary@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Matthew Seaman <matthew@FreeBSD.org\ >

Port Management Team Secretary <portmgr-secretary@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Frederic Culot <culot@FreeBSD.org\ >

Security Team Secretary <secteam-secretary@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Remko Lodder <remko@FreeBSD.org\ >

--------------

Accounts Team <accounts@>
~~~~~~~~~~~~~~~~~~~~~~~~~

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.

Email sent to the Accounts Team is currently forwarded to `Cluster
Administration <#t-clusteradm>`__.

Backups Administrators <backups@>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Backups Administrators handle all backups on the FreeBSD cluster.

Email sent to the Backups Team is currently forwarded to `Cluster
Administration <#t-clusteradm>`__.

Bugmeisters <bugmeister@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Bugmeisters 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.

-  Eitan Adler <eadler@FreeBSD.org\ >
-  Marcus von Appen <mva@FreeBSD.org\ >
-  Gavin Atkinson <gavin@FreeBSD.org\ >
-  Kubilay Kocak <koobs@FreeBSD.org\ >
-  Oleksandr Tymoshenko <gonzo@FreeBSD.org\ >

Cluster Administrators <admins@>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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 `cluster administration charter <internal/clusteradm.html>`__ in
greater detail.

-  David Wolfskill <dhw@FreeBSD.org\ >
-  Gavin Atkinson <gavin@FreeBSD.org\ >
-  Glen Barber <gjb@FreeBSD.org\ >
-  Hiren Panchasara <hiren@FreeBSD.org\ >
-  Peter Wemm <peter@FreeBSD.org\ > (Lead)
-  Sean Bruno <sbruno@FreeBSD.org\ >
-  Simon L. B. Nielsen <simon@FreeBSD.org\ >
-  Ryan Steinmetz <zi@FreeBSD.org\ >

DNS Administrators <dnsadm@>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The DNS Administrators are responsible for managing DNS and related
services.

E-mail to the DNS Administrators is currently forwarded to `Cluster
Administration <#t-clusteradm>`__.

FreeBSD Forum Administrators <forum-admins@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Forum Administrators maintain the FreeBSD Project's web forum site,
located at https://forums.freebsd.org/ and lead the group of moderators
who work to ensure the relevance and quality of forum content.

-  Brad Davis <brd@FreeBSD.org\ >
-  Daniel Geržo <danger@FreeBSD.org\ >
-  Ben C. O. Grimm <dutchdaemon@FreeBSD.org\ >
-  Lars Engels <lme@FreeBSD.org\ >
-  Warren Block <wblock@FreeBSD.org\ >

Repository Automated Mirroring to GitHub Coordinators <github-automation@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The GitHub Automation team oversees the export of FreeBSD source code
repository content to the read-only repository instances on GitHub

-  Kubilay Kocak <koobs@FreeBSD.org\ >
-  Marcus von Appen <mva@FreeBSD.org\ >
-  Bartek Rutkowski <robak@FreeBSD.org\ >
-  Craig Rodrigues <rodrigc@FreeBSD.org\ >
-  Ulrich Sp?rlein <uqs@FreeBSD.org\ >

Jenkins Continuous Integration Testing Administrators <jenkins-admin@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Jenkins Administrators run continuous build and integration tests
against the HEAD revision of the FreeBSD Source Code.

-  Ahmed Kamal <email.ahmedkamal@googlemail.com\ >
-  Julio Merino <jmmv@FreeBSD.org\ >
-  Li-Wen Hsu <lwhsu@FreeBSD.org\ >
-  Craig Rodrigues <rodrigc@FreeBSD.org\ >
-  Steve Wills <swills@FreeBSD.org\ >

FTP/WWW Mirror Site Coordinators <mirror-admin@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

E-mail to the Mirror Site Coordinators is currently forwarded to the
`Cluster Administration <#t-clusteradm>`__ team with the addition of:

-  Jun Kuriyama <kuriyama@FreeBSD.org\ >

Perforce Repository Administrators <perforce-admin@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Justin T. Gibbs <gibbs@FreeBSD.org\ >
-  Gordon Tetlow <gordon@FreeBSD.org\ >
-  Robert Watson <rwatson@FreeBSD.org\ >
-  Peter Wemm <peter@FreeBSD.org\ >

Phabricator Code Review Application Administrators <phabric-admin@FreeBSD.org;>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Phabricator Administrators are responsible for maintaining the
FreeBSD's instance of the Phabricator on-line code review tool located
at https://reviews.freebsd.org/

-  Eitan Adler <eadler@FreeBSD.org\ >
-  Ed Maste <emaste@FreeBSD.org\ >
-  Li-Wen Hsu <lwhsu@FreeBSD.org\ >
-  Mathieu Arnold <mat@FreeBSD.org\ >
-  Bartek Rutkowski <robak@FreeBSD.org\ >
-  Rui Paulo <rpaulo@FreeBSD.org\ >

Postmaster Team <postmaster@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.

-  Florian Smeets <flo@FreeBSD.org\ > (Lead)
-  Sahil Tandon <sahil@FreeBSD.org\ >
-  David Wolfskill <dhw@FreeBSD.org\ >
-  Philippe Audeoud <jadawin@FreeBSD.org\ >
-  Brad Davis <brd@FreeBSD.org\ >

Subversion Administrators <svnadm@>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The FreeBSD Subversion team is responsible for maintaining the health of
the Subversion Repositories.

Email to the Subversion Administration team is currently forwarded to
`Cluster Administration <#t-clusteradm>`__.

Webmaster Team <webmaster@FreeBSD.org\ >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The FreeBSD Webmaster Team is appointed by FreeBSD 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.

Email to the Webmaster Team is currently forwarded to the `Documentation
Engineering <#t-doceng>`__ team with the addition of:

-  Wolfram Schneider <wosch@FreeBSD.org\ >

.. raw:: html

   </div>

.. raw:: html

   </div>

.. raw:: html

   <div id="footer">

.. raw:: html

   </div>

.. raw:: html

   </div>

.. raw:: html

   </div>