diff options
Diffstat (limited to 'website/content/en/administration.adoc')
| -rw-r--r-- | website/content/en/administration.adoc | 161 |
1 files changed, 89 insertions, 72 deletions
diff --git a/website/content/en/administration.adoc b/website/content/en/administration.adoc index 3ab9cf8e29..0c49e3ec76 100644 --- a/website/content/en/administration.adoc +++ b/website/content/en/administration.adoc @@ -20,11 +20,11 @@ This page lists teams, groups and individuals within the FreeBSD project with de * Project Management ** <<t-core, Core Team>> ** <<t-doceng, Documentation Engineering Team>> -** <<t-portmgr, Port Management Team>> +** <<t-portmgr, Ports Management Team>> ** <<t-ports-secteam, Ports Security Team>> +** <<t-pkgmgr, Packages Management 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>> @@ -32,14 +32,15 @@ This page lists teams, groups and individuals within the FreeBSD project with de * Secretaries ** <<t-core-secretary, Core Team Secretary>> ** <<t-doceng-secretary, Documentation Engineering Team Secretary>> -** <<t-portmgr-secretary, Port Management Team Secretary>> +** <<t-portmgr-secretary, Ports Management Team Secretary>> * Internal Administration ** <<t-accounts, Accounts Team>> ** <<t-backups, Backup Administrators>> -** <<t-bugmeister, Bugmeisters>> +** <<t-bugmeister, Bugmeister>> ** <<t-clusteradm, Cluster Administrators>> ** <<t-dnsadm, DNS Administrators>> ** <<t-forum-admins, Forum Administrators>> +** <<t-git, Git Administrators>> ** <<t-github-automation, GitHub Repository Mirror>> ** <<t-jenkins-admin, Jenkins Continuous Integration Testing Administrators>> ** <<t-mirror-admin, FTP/WWW Mirror Site Coordinators>> @@ -57,15 +58,15 @@ This page lists teams, groups and individuals within the FreeBSD project with de 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) +* {bapt} (Security Team Liaison) +* {bcr} (Foundation Liaison) +* {emaste} (Release Engineering Team Liaison) +* {grog} +* {jhb} (CI Team Liaison) +* {lwhsu} (Documentation Engineering Team Liaison) +* {manu} (Ports Management Team Liaison) +* {tcberner} (Cluster Administrators Team Liaison) +* {0mp} (Bugmeister Team Liaison) [[t-doceng]] == FreeBSD Documentation Engineering Team <doceng@FreeBSD.org> @@ -79,23 +80,21 @@ The https://www.freebsd.org/internal/doceng/[doceng team charter] describes the * {dbaio} * {bcr} * {hrs} -* {ryusuke} -* {0mp} (Secretary) +* {fernape} (Secretary) [[t-portmgr]] -== FreeBSD Port Management Team <portmgr@FreeBSD.org> +== FreeBSD Ports 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. +The primary responsibility of the FreeBSD Ports 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. +The https://www.freebsd.org/portmgr/charter/[portmgr team charter] describes the duties and responsibilities of the Ports Management Team in greater detail. -* {antoine} -* {bapt} (Core Team Liaison) -* {bdrewery} (Release Engineering Team Liaison) +* {bapt} +* {bofh} * {mat} (Cluster Administration Team Liaison) -* {rene} (Secretary) -* {swills} -* {tcberner} +* {pizzamig} +* {rene} +* {tcberner} (Secretary) ''' @@ -103,7 +102,7 @@ The https://www.freebsd.org/portmgr/charter/[portmgr team charter] describes the == 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]. +More details are available on the https://wiki.freebsd.org/PortsSecteam[Wiki page]. * {fluffy} * {joneum} @@ -111,34 +110,33 @@ More details are available on the https://wiki.freebsd.org/ports-secteam[Wiki pa ''' +[[t-pkgmgr]] +== FreeBSD Packages Management Team <pkgmgr@FreeBSD.org> + +The primary responsibility of the FreeBSD Packages Management Team is to assure the ports tree remains functional, this includes running test builds of proposed changes, reverting/fixing broken commits that break the builds, maintain the automated package building cluster, and make the resulting packages available for download by FreeBSD users. + +* {antoine} +* {bdrewery} + +''' + [[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} * {blackend} +* {karels} (Deputy Lead) * {delphij} -* {cperciva} (Deputy Lead) - -[[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} - -''' +* {cperciva} (Lead) [[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. +The 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 at link:https://www.freebsd.org/donations/[FreeBSD Donations Liaison]. * {gahr} * {bhughes} @@ -152,13 +150,13 @@ Furthermore, it is responsible for resolving software bugs affecting the securit The FreeBSD Security Officer Charter describes the duties and responsibilities of the Security Officer in greater detail. * {gordon} (Officer) +* {bapt} (Core Team Liaison) * {delphij} (Officer Emeritus, Release Engineering Team Liaison) * {des} (Officer Emeritus) * {gjb} (Cluster Administrators Team Liaison) * {emaste} (Officer Deputy) -* {bz} -* {gnn} * {markj} +* {oshogbo} * {philip} [[t-vendor]] @@ -175,22 +173,22 @@ Email sent to Vendor Relations is forwarded to the FreeBSD Core Team in addition 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} +* {carlavilla} [[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} +* {fernape} [[t-portmgr-secretary]] -== Port Management Team Secretary <portmgr-secretary@FreeBSD.org> +== Ports 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. +The FreeBSD Ports Management Team Secretary is a non-voting member of the Ports 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 Ports 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} +* {tcberner} ''' @@ -203,7 +201,7 @@ 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. +Email sent to the Accounts Team is handled by the Cluster Administrators. [[t-backups]] == Backups Administrators <backups@> @@ -213,42 +211,42 @@ 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. +Email sent to the Backups Team is handled by the Cluster Administrators. [[t-bugmeister]] -== Bugmeisters <bugmeister@FreeBSD.org> +== Bugmeister <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. +The Bugmeister Team is 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} +* {linimon} +* {mva} +* {0mp} [[t-clusteradm]] -== Cluster Administrators <admins@> +== Cluster Administrators <clusteradm@> //// 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. +The Cluster Administrators are responsible for maintaining the machines and services that the project relies on for its distributed work and communication. +Issues concerning the project's infrastructure or setting up new machines or services 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} +* {bofh} +* {dbaio} * {dhw} -* {gavin} * {gjb} * {lwhsu} * {peter} * {philip} -* {sbruno} -* {simon} * {zi} (Lead) +Please consider using one of the more specific aliases (e.g. accounts@, dnsadm@, mirror-admin@,...) or https://bugs.freebsd.org/submit/[opening a bug report] to report problems with the cluster infrastructure. Select "Services" and then "Core Infrastructure". + [[t-dnsadm]] == DNS Administrators <dnsadm@> //// @@ -257,7 +255,7 @@ 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. +Email sent to the DNS Administrators handled by the Cluster Administrators. [[t-forum-admins]] == FreeBSD Forum Administrators <forum-admins@FreeBSD.org> @@ -269,6 +267,18 @@ The Forum Administrators maintain the FreeBSD Project's Internet forum, located * {dutchdaemon} * {lme} +[[t-git]] +== Git Administrators <gitadm@> +//// +admins mail aliases intentionally left incomplete +//// + +The FreeBSD Git Administrators are responsible for maintaining the health of the Git repositories. + +Email to the Git Administrators is handled by the Cluster Administrators. + +Please https://bugs.freebsd.org/submit/[open a bug report] to report problems with the Git repositories. Select "Services" and then "Core Infrastructure". + [[t-github-automation]] == Repository Automated Mirroring to GitHub Coordinators <github-automation@FreeBSD.org> @@ -290,18 +300,19 @@ This includes maintaining the Jenkins instance and the jobs that run builds and * {brd} * {brooks} * {lwhsu} -* {markj} (Core Team Liaison) -* {seanc} * {swills} [[t-mirror-admin]] -== FTP/WWW Mirror Site Coordinators <mirror-admin@FreeBSD.org> +== FTP/WWW Mirror Site Coordinators <mirror-admin@> +//// +admins mail aliases intentionally left incomplete +//// 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: +Email to the Mirror Site Coordinators is handled by the Cluster Administrators. -* {kuriyama} +Please https://bugs.freebsd.org/submit/[open a bug report] to report problems with the mirror infrastructure. Select "Services" and then "FTP/WWW Sites & Mirrors". [[t-phabric-admin]] == Phabricator Code Review Application Administrators <phabric-admin@FreeBSD.org> @@ -315,7 +326,6 @@ The Phabricator Administrators are responsible for maintaining the FreeBSD's ins * {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". @@ -325,19 +335,25 @@ For any problems regarding Phabricator, please https://bugs.freebsd.org/submit/[ 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. +* {bapt} * {krion} * {ler} * {philip} * {pi} -* {rea} +* {vsevolod} * {zi} [[t-subversion]] == Subversion Administrators <svnadm@> +//// +admins mail aliases intentionally left incomplete +//// + +The FreeBSD Subversion Administrators are responsible for maintaining the health of the Subversion repositories. -The FreeBSD Subversion team is responsible for maintaining the health of the Subversion Repositories. +Email to the Subversion Administrators is handled by the Cluster Administrators. -Email to the Subversion Administration team is currently forwarded to the Cluster Administrators. +Please https://bugs.freebsd.org/submit/[open a bug report] to report problems with the Subversion repositories. Select "Services" and then "Core Infrastructure". [[t-webmaster]] == Webmaster Team <webmaster@FreeBSD.org> @@ -354,5 +370,6 @@ Email to the Webmaster Team is currently forwarded to the Documentation Engineer 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. +* {bofh} * {linimon} * {koobs} |