Changeset View
Changeset View
Standalone View
Standalone View
en_US.ISO8859-1/htdocs/administration.xml
| Show First 20 Lines • Show All 84 Lines • ▼ Show 20 Lines | <html xmlns="http://www.w3.org/1999/xhtml"> | ||||
| <p>The FreeBSD Core Team constitutes the project's "Board of Directors", | <p>The FreeBSD Core Team constitutes the project's "Board of Directors", | ||||
| responsible for deciding the project's overall goals and direction as | responsible for deciding the project's overall goals and direction as | ||||
| well as managing specific areas of the FreeBSD project landscape. The | well as managing specific areas of the FreeBSD project landscape. The | ||||
| Core Team is elected by the active developers in the project.</p> | Core Team is elected by the active developers in the project.</p> | ||||
| <ul> | <ul> | ||||
| <li>&a.allanjude.email; (Clusteradm Liaison)</li> | <li>&a.allanjude.email; (Clusteradm Liaison)</li> | ||||
| <li>&a.bapt.email; (Portmgr and CI-team Liaison)</li> | <li>&a.bcr.email; (Foundation Liaison)</li> | ||||
| <li>&a.bcr.email;</li> | <li>&a.brooks.email; (Security Team Liaison)</li> | ||||
| <li>&a.benno.email; (Code-of-Conduct Committee and Security Team Liaison)</li> | <li>&a.hrs.email; (Doceng Team Liaison)</li> | ||||
| <li>&a.emaste.email;</li> | <li>&a.imp.email; (Code-of-Conduct Committee Liaison)</li> | ||||
| <li>&a.gnn.email;</li> | <li>&a.jeff.email;</li> | ||||
| <li>&a.hrs.email; (Doceng and Release Engineering Team Liaison)</li> | <li>&a.jhb.email; (Bugmeister and Release Engineering Team Liaison)</li> | ||||
| <li>&a.jhb.email; (Bugmeister Liaison)</li> | |||||
| <li>&a.kmoore.email;</li> | <li>&a.kmoore.email;</li> | ||||
| <li>&a.seanc.email; (CI and Portmgr Team Liaison)</li> | |||||
| </ul> | </ul> | ||||
matthew: Can we hold off declaring seanc as CI Team liason for now? brooks would be the logical choice… | |||||
Not Done Inline ActionsI will hold off on this until the outcome is clear. jrm: I will hold off on this until the outcome is clear. | |||||
Not Done Inline ActionsWe confirmed this offline and I will be involved with CI. seanc: We confirmed this offline and I will be involved with CI. | |||||
| <h3><a name="t-doceng">FreeBSD Documentation Engineering Team</a> | <h3><a name="t-doceng">FreeBSD Documentation Engineering Team</a> | ||||
| <<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>></h3> | <<a href="mailto:doceng@FreeBSD.org">doceng@FreeBSD.org</a>></h3> | ||||
| <p>The FreeBSD Documentation Engineering Team is responsible for | <p>The FreeBSD Documentation Engineering Team is responsible for | ||||
| defining and following up documentation goals for the committers | defining and following up documentation goals for the committers | ||||
| in the Documentation project. The <a | in the Documentation project. The <a | ||||
| href="internal/doceng.html">doceng team charter</a> | href="internal/doceng.html">doceng team charter</a> | ||||
| Show All 16 Lines | <p>The primary responsibility of the FreeBSD Port Management Team is to | ||||
| collection that is functional, stable, up-to-date and full-featured. | collection that is functional, stable, up-to-date and full-featured. | ||||
| Its secondary responsibility is to coordinate among the committers | Its secondary responsibility is to coordinate among the committers | ||||
| and developers who work on it. The <a | and developers who work on it. The <a | ||||
| href="portmgr/charter.html">portmgr team charter</a> | href="portmgr/charter.html">portmgr team charter</a> | ||||
| describes the duties and responsibilities of the Port Management | describes the duties and responsibilities of the Port Management | ||||
| Team in greater detail.</p> | Team in greater detail.</p> | ||||
| <ul> | <ul> | ||||
| <li>&a.mat.email; (Cluster Administration Team Liaison)</li> | <li>&a.adamw.email;</li> | ||||
| <li>&a.antoine.email;</li> | <li>&a.antoine.email;</li> | ||||
| <li>&a.bapt.email; (Core Team Liaison)</li> | <li>&a.bapt.email; (Core Team Liaison)</li> | ||||
| <li>&a.bdrewery.email; (Release Engineering Team Liaison)</li> | <li>&a.bdrewery.email; (Release Engineering Team Liaison)</li> | ||||
| <li>&a.feld.email;</li> | <li>&a.feld.email;</li> | ||||
| <li>&a.mat.email; (Cluster Administration Team Liaison)</li> | |||||
| <li>&a.rene.email; (Secretary)</li> | <li>&a.rene.email; (Secretary)</li> | ||||
| <li>&a.swills.email;</li> | <li>&a.swills.email;</li> | ||||
| <li>&a.adamw.email;</li> | |||||
| </ul> | </ul> | ||||
| <hr/> | <hr/> | ||||
| <h3><a name="t-re">Primary Release Engineering Team</a> | <h3><a name="t-re">Primary Release Engineering Team</a> | ||||
| <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>></h3> | <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>></h3> | ||||
| <p>The Primary Release Engineering Team is responsible for setting and | <p>The Primary Release Engineering Team is responsible for setting and | ||||
| ▲ Show 20 Lines • Show All 110 Lines • ▼ Show 20 Lines | <p>Vendor Relations is responsible for handling email | ||||
| to the &os; Foundation.</p> | to the &os; Foundation.</p> | ||||
| <hr/> | <hr/> | ||||
| <h3><a name="t-core-secretary">Core Team Secretary</a> | <h3><a name="t-core-secretary">Core Team Secretary</a> | ||||
| <<a href="mailto:core-secretary@FreeBSD.org">core-secretary@FreeBSD.org</a>></h3> | <<a href="mailto:core-secretary@FreeBSD.org">core-secretary@FreeBSD.org</a>></h3> | ||||
| <p>The &os; Core Team Secretary is a non-voting member of the Core Team, | <p>The &os; Core Team Secretary is a non-voting member of the Core Team, | ||||
| responsible for documenting the work done by core, keeping track of the | responsible for documenting the work done by core, keeping track of the core | ||||
| core agenda, direct contact with non-core members sending mail to core | agenda, contacting non-core members on behalf of core, sending mail to core, | ||||
| and to be an the interface to the admin team for | and interfacing with the admin team for committer/account approval. The Core | ||||
| committer/account approval. The Core Team Secretary is also responsible | Team Secretary is also responsible for writing and sending out monthly status | ||||
| for writing and sending out monthly status reports to the &os; | reports to the &os; Developer community, containing a summary of core's latest | ||||
| Developer community, containing a summary of core's latest decisions and | decisions and actions.</p> | ||||
| actions.</p> | |||||
| <ul> | <ul> | ||||
| <li>&a.matthew.email;</li> | <li>&a.jrm.email;</li> | ||||
| </ul> | </ul> | ||||
| <h3><a name="t-portmgr-secretary">Port Management Team Secretary</a> | <h3><a name="t-portmgr-secretary">Port Management Team Secretary</a> | ||||
| <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>></h3> | <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>></h3> | ||||
| <p>The FreeBSD Port Management Team Secretary is a non-voting member of the | <p>The FreeBSD Port Management Team Secretary is a non-voting member of the | ||||
| Port Management Team, responsible for documenting the work done by portmgr, | Port Management Team, responsible for documenting the work done by portmgr, | ||||
| keeping track of voting procedures, and to be an interface to the other | keeping track of voting procedures, and to be an interface to the other | ||||
| ▲ Show 20 Lines • Show All 231 Lines • Show Last 20 Lines | |||||
Can we hold off declaring seanc as CI Team liason for now? brooks would be the logical choice here, but he's travelling at the moment. If we can wait until he's had a chance to reply before deciding anything.