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.
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.
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.
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.
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.
The FreeBSD/amd64 Release Engineering Team is responsible for specific release issues related to the FreeBSD/amd64 platform.
The FreeBSD/ia64 Release Engineering Team is responsible for specific release issues related to the FreeBSD/ia64 platform.
The FreeBSD/i386 Release Engineering Team is responsible for specific release issues related to the FreeBSD/i386 platform.
The FreeBSD/pc98 Release Engineering Team is responsible for specific release issues related to the FreeBSD/pc98 platform.
The FreeBSD/ppc Release Engineering Team is responsible for specific release issues related to the FreeBSD/ppc platform.
The FreeBSD/sparc64 Release Engineering Team is responsible for specific release issues related to the FreeBSD/sparc64 platform.
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.
Press contact, marketing, interviews, information.
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.
Vendor relations.
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.
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.
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.
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.
The Backups Administrators handle all backups on the FreeBSD cluster.
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.
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.
The CVS doc/www Repository Managers are allowed to directly modify the repository without using the CVS tool. It is their responsibility to ensure that technical problems that arise in the repository are resolved quickly. The CVS doc/www repository managers have the authority to back out commits if this is necessary to resolve a CVS technical problem. Repo-copy requests should be directed to the repository managers.
The CVS ports Repository Managers are allowed to directly modify the repository without using the CVS tool. It is their responsibility to ensure that technical problems that arise in the repository are resolved quickly. The CVS ports repository managers have the authority to back out commits if this is necessary to resolve a CVS technical problem. Repo-copy requests should be directed to the repository managers.
The CVS src Repository Managers are allowed to directly modify the repository without using the CVS tool. It is their responsibility to ensure that technical problems that arise in the repository are resolved quickly. The CVS source repository managers have the authority to back out commits if this is necessary to resolve a CVS technical problem. Repo-copy requests should be directed to the repository managers.
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.
The DNS Administrators are responsible for managing DNS and related services.
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.
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.
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.
The Reference Systems Administrators are responsible for administrating, upgrading and maintaining the reference systems in the FreeBSD cluster. These systems are available to all FreeBSD committers.
The FreeBSD Webmaster Team is 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.