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
- Release Engineering
- Teams
- Secretaries
- Internal Administration
- Accounts Team
- Backup Administrators
- Bugmeisters
- Cluster Administrators
- DNS Administrators
- Forum Administrators
- GitHub Repository Mirror
- Jenkins Continuous Integration Testing Administrators
- FTP/WWW Mirror Site Coordinators
- Phabricator Code Review Administration
- Postmaster Team
- Subversion Administrators
- Webmaster Team
- Wiki Admin Team
FreeBSD Core Team <[email protected]>
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.
- Baptiste Daroussin <[email protected]> (Clusteradm Liaison)
- Ed Maste <[email protected]> (GIT Transition WG and Security Team Liason)
- George V. Neville-Neil <[email protected]> (Foundation Liaison)
- Hiroki Sato <[email protected]> (Code-of-Conduct Committee Liaison)
- Kyle Evans <[email protected]> (Portmgr Team Liaison)
- Mark Johnston <[email protected]> (Bugmeister and CI Team Liaison)
- Scott Long <[email protected]> (Release Engineering Team Liaison)
- Sean Chittenden <[email protected]> (Doceng Team Liaison)
- Warner Losh <[email protected]> (GIT Transition WG Liaison)
FreeBSD Documentation Engineering Team <[email protected]>
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 describes the duties and responsibilities of the Documentation Engineering Team in greater detail.
- Glen Barber <[email protected]>
- Warren Block <[email protected]>
- Marc Fonvieille <[email protected]>
- G�bor K�vesd�n <[email protected]>
- Benedict Reuschling <[email protected]>
- Hiroki Sato <[email protected]>
- Ryusuke SUZUKI <[email protected]>
- Mateusz Piotrowski <[email protected]> (Secretary)
FreeBSD Port Management Team <[email protected]>
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 describes the duties and responsibilities of the Port Management Team in greater detail.
- Adam Weinberger <[email protected]>
- Antoine Brodin <[email protected]>
- Baptiste Daroussin <[email protected]> (Core Team Liaison)
- Bryan Drewery <[email protected]> (Release Engineering Team Liaison)
- Mathieu Arnold <[email protected]> (Cluster Administration Team Liaison)
- Ren� Ladan <[email protected]> (Secretary)
- Steve Wills <[email protected]>
FreeBSD Ports Security Team <[email protected]>
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 Wiki page.
- Dima Panov <[email protected]>
- Jochen Neumeister <[email protected]>
- Thomas Zander <[email protected]>
Primary Release Engineering Team <[email protected]>
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
describes the duties and responsibilities of the Primary Release
Engineering Team in greater detail.
- Glen Barber <[email protected]> (Lead)
- Konstantin Belousov <[email protected]>
- Bryan Drewery <[email protected]>
- Marc Fonvieille <[email protected]>
- Xin Li <[email protected]>
- Colin Percival <[email protected]> (Deputy Lead)
- Hiroki Sato <[email protected]>
- Gleb Smirnoff <[email protected]>
Builders Release Engineering Team <[email protected]>
The builders release engineering team is responsible for building and packaging FreeBSD releases on the various supported platforms.
- Marcel Moolenaar <[email protected]>
- Yoshihiro Takahashi <[email protected]>
- Nathan Whitehorn <[email protected]>
Donations Team <[email protected]>
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 page.
- Pietro Cerutti <[email protected]>
- Bradley T. Hughes <[email protected]>
- Adriaan de Groot <[email protected]>
Security Team <[email protected]>
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 Tetlow <[email protected]> (Officer)
- Xin Li <[email protected]> (Officer Emeritus, Release Engineering Team Liaison)
- Dag-Erling Sm�rgrav <[email protected]> (Officer Emeritus)
- Glen Barber <[email protected]> (Cluster Administrators Team Liaison)
- Ed Maste <[email protected]> (Officer Deputy)
- Bjoern A. Zeeb <[email protected]>
- George V. Neville-Neil <[email protected]>
- Mark Johnston <[email protected]>
- Philip Paeps <[email protected]>
Vendor Relations <[email protected]>
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 <[email protected]>
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.
- Muhammad Moinur Rahman <[email protected]>
Documentation Engineering Team Secretary <[email protected]>
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.
- Mateusz Piotrowski <[email protected]>
Port Management Team Secretary <[email protected]>
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.
- Ren� Ladan <[email protected]>
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 the Cluster Administrators.
Backups Administrators <backups@>
The Backups Administrators handle all backups on the FreeBSD cluster.
Email sent to the Backups Team is currently forwarded to the Cluster Administrators.
Bugmeisters <[email protected]>
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.
- Eitan Adler <[email protected]>
- Marcus von Appen <[email protected]>
- Gavin Atkinson <[email protected]>
- Kubilay Kocak <[email protected]>
- Oleksandr Tymoshenko <[email protected]>
Cluster Administrators <admins@>
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 cluster administration charter in greater detail.
- Allan Jude <[email protected]>
- Brad Davis <[email protected]>
- David Wolfskill <[email protected]>
- Gavin Atkinson <[email protected]>
- Glen Barber <[email protected]>
- Li-Wen Hsu <[email protected]>
- Peter Wemm <[email protected]>
- Sean Bruno <[email protected]>
- Simon L. B. Nielsen <[email protected]>
- Ryan Steinmetz <[email protected]>�(Lead)
DNS Administrators <dnsadm@>
The DNS Administrators are responsible for managing DNS and related services.
E-mail to the DNS Administrators is currently forwarded to the Cluster Administrators.
FreeBSD Forum Administrators <[email protected]>
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.
- Brad Davis <[email protected]>
- Daniel Geržo <[email protected]>
- Ben C. O. Grimm <[email protected]>
- Lars Engels <[email protected]>
- Warren Block <[email protected]>
Repository Automated Mirroring to GitHub Coordinators <[email protected]>
The GitHub Automation team oversees the export of FreeBSD source code repository content to the read-only repository instances on GitHub
- Kubilay Kocak <[email protected]>
- Marcus von Appen <[email protected]>
- Bartek Rutkowski <[email protected]>
- Craig Rodrigues <[email protected]>
- Ulrich Sp�rlein <[email protected]>
Jenkins Continuous Integration Testing Administrators <[email protected]>
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.
- Baptiste Daroussin <[email protected]>
- Brad Davis <[email protected]>
- Brooks Davis <[email protected]>
- Li-Wen Hsu <[email protected]>
- Mark Johnston <[email protected]> (Core Team Liaison)
- Sean Chittenden <[email protected]>
- Steve Wills <[email protected]>
FTP/WWW Mirror Site Coordinators <[email protected]>
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:
- Jun Kuriyama <[email protected]>
Phabricator Code Review Application Administrators <[email protected]>
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/
- Allan Jude <[email protected]>
- Muhammad Moinur Rahman <[email protected]>
- Eitan Adler <[email protected]>
- Ed Maste <[email protected]>
- Jonathan T. Looney <[email protected]>
- Li-Wen Hsu <[email protected]>
- Mathieu Arnold <[email protected]>
- Martin Wilke <[email protected]>
- Kurt Jaeger <[email protected]>
For any problems regarding Phabricator, please open a bug report and select "Services" and then "Code Review".
Postmaster Team <[email protected]>
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.
- Kirill Ponomarew <[email protected]>
- Larry Rosenman <[email protected]>
- Philip Paeps <[email protected]>
- Kurt Jaeger <[email protected]>
- Eygene Ryabinkin <[email protected]>
- Ryan Steinmetz <[email protected]>
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.
Webmaster Team <[email protected]>
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:
- Wolfram Schneider <[email protected]>
Wiki Admin Team <[email protected]>
The FreeBSD Wiki Team is responsible for keeping the FreeBSD Wiki site up and running. They also shape the overall design and content structure.
- Gavin Atkinson <[email protected]>
- Mark Linimon <[email protected]>
- David Chisnall <[email protected]>
- Kubilay Kocak <[email protected]>