path: root/website/content/en/administration.adoc

---
title: "FreeBSD Project Administration and Management"
sidenav: about
---

include::shared/authors.adoc[]

////
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.
////

= 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
** <<t-core, Core Team>>
** <<t-doceng, Documentation Engineering Team>>
** <<t-portmgr, Port Management Team>>
** <<t-ports-secteam, Ports Security Team>>
* Release Engineering
** <<t-re, Primary Release Engineering Team>>
** <<t-re-builder, Builders Release Engineering Team>>
* Teams
** <<t-donations, Donations Team>>
** <<t-secteam, Security Team>>
** <<t-vendor, Vendor Relations>>
* Secretaries
** <<t-core-secretary, Core Team Secretary>>
** <<t-doceng-secretary, Documentation Engineering Team Secretary>>
** <<t-portmgr-secretary, Port Management Team Secretary>>
* Internal Administration
** <<t-accounts, Accounts Team>>
** <<t-backups, Backup Administrators>>
** <<t-bugmeister, Bugmeisters>>
** <<t-clusteradm, Cluster Administrators>>
** <<t-dnsadm, DNS Administrators>>
** <<t-forum-admins, Forum Administrators>>
** <<t-github-automation, GitHub Repository Mirror>>
** <<t-jenkins-admin, Jenkins Continuous Integration Testing Administrators>>
** <<t-mirror-admin, FTP/WWW Mirror Site Coordinators>>
** <<t-phabric-admin, Phabricator Code Review Administration>>
** <<t-postmaster, Postmaster Team>>
** <<t-subversion, Subversion Administrators>>
** <<t-webmaster, Webmaster Team>>
** <<t-wiki, Wiki Admin Team>>

'''

[[t-core]]
== 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.

* {bapt} (Clusteradm Liaison)
* {emaste} (GIT Transition WG and Security Team Liason)
* {gnn} (Foundation Liaison)
* {hrs} (Code-of-Conduct Committee Liaison)
* {kevans} (Portmgr Team Liaison)
* {markj} (Bugmeister and CI Team Liaison)
* {scottl} (Release Engineering Team Liaison)
* {seanc} (Doceng Team Liaison)
* {imp} (GIT Transition WG Liaison)

[[t-doceng]]
== 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 https://www.freebsd.org/internal/doceng/[doceng team charter] describes the duties and responsibilities of the Documentation Engineering Team in greater detail.

* {gjb}
* {wblock}
* {blackend}
* {gabor}
* {bcr}
* {hrs}
* {ryusuke}
* {0mp} (Secretary)

[[t-portmgr]]
== 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 https://www.freebsd.org/portmgr/charter/[portmgr team charter] describes the duties and responsibilities of the Port Management Team in greater detail.

* {adamw}
* {antoine}
* {bapt} (Core Team Liaison)
* {bdrewery} (Release Engineering Team Liaison)
* {mat} (Cluster Administration Team Liaison)
* {rene} (Secretary)
* {swills}

'''

[[t-ports-secteam]]
== FreeBSD Ports Security Team <ports-secteam@FreeBSD.org>

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 https://wiki.freebsd.org/ports-secteam[Wiki page].

* {fluffy}
* {joneum}
* {riggs}

'''

[[t-re]]
== 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 https://www.freebsd.org/releng/charter/[release engineering team charter] describes the duties and responsibilities of the Primary Release Engineering Team in greater detail.

* {gjb} (Lead)
* {kib}
* {bdrewery}
* {blackend}
* {delphij}
* {cperciva} (Deputy Lead)
* {hrs}
* {glebius}

[[t-re-builder]]
== 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}
* {nyan}
* {nwhitehorn}

'''

[[t-donations]]
== 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 https://www.freebsd.org/donations/[FreeBSD Donations Liaison] page.

* {gahr}
* {bhughes}
* {adridg}

[[t-secteam]]
== 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 describes the duties and responsibilities of the Security Officer in greater detail.

* {gordon} (Officer)
* {delphij} (Officer Emeritus, Release Engineering Team Liaison)
* {des} (Officer Emeritus)
* {gjb} (Cluster Administrators Team Liaison)
* {emaste} (Officer Deputy)
* {bz}
* {gnn}
* {markj}
* {philip}

[[t-vendor]]
== 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.

'''

[[t-core-secretary]]
== 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, 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 FreeBSD Developer community, containing a summary of core's latest decisions and actions.

* {bofh}

[[t-doceng-secretary]]
== Documentation Engineering Team Secretary <doceng-secretary@FreeBSD.org>

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.

* {0mp}

[[t-portmgr-secretary]]
== 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.

* {rene}

'''

[[t-accounts]]
== Accounts Team <accounts@>
////
admins mail aliases intentionally left incomplete
////

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 the Cluster Administrators.

[[t-backups]]
== Backups Administrators <backups@>
////
admins mail aliases intentionally left incomplete
////

The Backups Administrators handle all backups on the FreeBSD cluster.

Email sent to the Backups Team is currently forwarded to the Cluster Administrators.

[[t-bugmeister]]
== Bugmeisters <bugmeister@FreeBSD.org>

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.

* {eadler}
* {mva}
* {gavin}
* {koobs}
* {gonzo}

[[t-clusteradm]]
== Cluster Administrators <admins@>
////
admins mail aliases intentionally left incomplete
////

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 https://www.freebsd.org/internal/clusteradm/[cluster administration charter] in greater detail.

* {allanjude}
* {bapt}
* {brd}
* {dhw}
* {gavin}
* {gjb}
* {lwhsu}
* {peter}
* {philip}
* {sbruno}
* {simon}
* {zi} (Lead)

[[t-dnsadm]]
== DNS Administrators <dnsadm@>
////
admins mail aliases intentionally left incomplete
////

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

E-mail to the DNS Administrators is currently forwarded to the Cluster Administrators.

[[t-forum-admins]]
== FreeBSD Forum Administrators <forum-admins@FreeBSD.org>

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

* {brd}
* {danger}
* {dutchdaemon}
* {lme}
* {wblock}

[[t-github-automation]]
== 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

* {koobs}
* {mva}
* {robak}
* {rodrigc}
* {uqs}

[[t-jenkins-admin]]
== Jenkins Continuous Integration Testing Administrators <jenkins-admin@FreeBSD.org>

The Jenkins Administrators maintain the Continuous Integration and testing infrastructure for The FreeBSD Project.
This includes maintaining the Jenkins instance and the jobs that run builds and execute tests.

* {bapt}
* {brd}
* {brooks}
* {lwhsu}
* {markj} (Core Team Liaison)
* {seanc}
* {swills}

[[t-mirror-admin]]
== FTP/WWW Mirror Site Coordinators <mirror-admin@FreeBSD.org>

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.

E-mail to the Mirror Site Coordinators is currently forwarded to the Cluster Administrators with the addition of:

* {kuriyama}

[[t-phabric-admin]]
== 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/

* {allanjude}
* {bofh}
* {eadler}
* {emaste}
* {jtl}
* {lwhsu}
* {mat}
* {miwi}
* {pi}

For any problems regarding Phabricator, please https://bugs.freebsd.org/submit/[open a bug report] and select "Services" and then "Code Review".

[[t-postmaster]]
== 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.

* {krion}
* {ler}
* {philip}
* {pi}
* {rea}
* {zi}

[[t-subversion]]
== 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 the Cluster Administrators.

[[t-webmaster]]
== 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 team with the addition of:

* {wosch}

[[t-wiki]]
== Wiki Admin Team <wiki-admin@FreeBSD.org>

The FreeBSD Wiki Team is responsible for keeping the FreeBSD https://wiki.FreeBSD.org/[Wiki] site up and running. They also shape the overall design and content structure.

* {gavin}
* {linimon}
* {theraven}
* {koobs}