RFC: The end of the contributors article [part two]
Joel Dahl
joel at FreeBSD.org
Fri Feb 23 13:50:16 UTC 2007
I've attached the latest version of the new administration page I've
been working on for a while, which will replace some parts of the
contributors article. I received a great deal of feedback last time I
asked for comments, and I think I've addressed pretty much everything.
Anyway, the plan is to add this to the "About" section on the website,
and simply call it "Administration". Removing all the obsolete stuff
from the contributors article would be the next step, along with nuking
all references to them from the website.
Comments?
--
Joel
-------------- next part --------------
&header;
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
+ [1]Core Team
+ [2]Documentation Engineering Team
+ [3]Port Management Team
* Release Engineering
+ [4]Primary Release Engineering Team
+ [5]FreeBSD/alpha Release Engineering Team
+ [6]FreeBSD/amd64 Release Engineering Team
+ [7]FreeBSD/ia64 Release Engineering Team
+ [8]FreeBSD/i386 Release Engineering Team
+ [9]FreeBSD/pc98 Release Engineering Team
+ [10]FreeBSD/ppc Release Engineering Team
+ [11]FreeBSD/sparc64 Release Engineering Team
* Teams
+ [12]Donations Team
+ [13]Marketing Team
+ [14]Security Team
* Secretaries
+ [15]Core Team Secretary
+ [16]Port Management Team Secretary
+ [17]Security Team Secretary
* Internal Administration
+ [18]Accounts Team
+ [19]Backup Administrators
+ [20]Bugmeisters & GNATS Administrators
+ [21]Cluster Administrators
+ [22]CVS doc/www Repository Managers
+ [23]CVS ports Repository Managers
+ [24]CVS src Repository Managers
+ [25]CVSup Mirror Site Coordinators
+ [26]DNS Administrators
+ [27]FTP/WWW Mirror Site Coordinators
+ [28]Perforce Repository Administrators
+ [29]Postmaster Team
+ [30]Ref Administrators
_________________________________________________________________
FreeBSD Core Team <[31]core@>
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.
* &a.wilko; <[32]wilko@>
* &a.brooks; <[33]brooks@>
* &a.keramida; <[34]keramida@>
* &a.imp; <[35]imp@>
* &a.gnn; <[36]gnn@>
* &a.wes; <[37]wes@>
* &a.hrs; <[38]hrs@>
* &a.murray; <[39]murray@>
* &a.rwatson; <[40]rwatson@>
FreeBSD Documentation Engineering Team <[41]doceng@>
The FreeBSD Documentation Engineering Team is responsible for defining
and following up documentation goals for the committers in the
Documentation project. The [42]doceng team charter describes the
duties and responsibilities of the Documentation Engineering Team in
greater detail.
* &a.nik; <[43]nik@>
* &a.blackend; <[44]blackend@>
* &a.hrs; <[45]hrs@>
* &a.murray; <[46]murray@>
FreeBSD Port Management Team <[47]portmgr@>
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 [48]portmgr team charter describes the
duties and responsibilities of the Port Management Team in greater
detail.
* &a.marcus; <[49]marcus@>
* &a.clement; <[50]clement@>
* &a.erwin; <[51]erwin@>
* &a.linimon; <[52]linimon@>
* &a.pav; <[53]pav@>
* &a.kris; <[54]kris@>
* &a.krion; <[55]krion@>
_________________________________________________________________
Primary Release Engineering Team <[56]re@>
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 [57]release engineering team charter describes the duties
and responsibilities of the Primary Release Engineering Team in
greater detail.
* &a.mux; <[58]mux@>
* &a.bmah; <[59]bmah@>
* &a.hrs; <[60]hrs@>
* &a.kensmith; <[61]kensmith@> (Lead)
* &a.murray; <[62]murray@>
* &a.rwatson; <[63]rwatson@>
* &a.dwhite; <[64]dwhite@>
FreeBSD/alpha Release Engineering Team <[65]re-alpha@>
The FreeBSD/alpha Release Engineering Team is responsible for specific
release issues related to the FreeBSD/alpha platform.
* &a.wilko; <[66]wilko@>
* &a.murray; <[67]murray@>
* &a.rwatson; <[68]rwatson@>
FreeBSD/amd64 Release Engineering Team <[69]re-amd64@>
The FreeBSD/amd64 Release Engineering Team is responsible for specific
release issues related to the FreeBSD/amd64 platform.
* &a.obrien; <[70]obrien@>
FreeBSD/ia64 Release Engineering Team <[71]re-ia64@>
The FreeBSD/ia64 Release Engineering Team is responsible for specific
release issues related to the FreeBSD/ia64 platform.
* &a.marcel; <[72]marcel@>
FreeBSD/i386 Release Engineering Team <[73]re-x86@>
The FreeBSD/i386 Release Engineering Team is responsible for specific
release issues related to the FreeBSD/i386 platform.
* &a.murray; <[74]murray@>
* &a.rwatson; <[75]rwatson@>
FreeBSD/pc98 Release Engineering Team <[76]re-pc98@>
The FreeBSD/pc98 Release Engineering Team is responsible for specific
release issues related to the FreeBSD/pc98 platform.
* &a.nyan; <[77]nyan@>
FreeBSD/ppc Release Engineering Team <[78]re-ppc@>
The FreeBSD/ppc Release Engineering Team is responsible for specific
release issues related to the FreeBSD/ppc platform.
* &a.grehan; <[79]grehan@>
FreeBSD/sparc64 Release Engineering Team <[80]re-sparc64@>
The FreeBSD/sparc64 Release Engineering Team is responsible for
specific release issues related to the FreeBSD/sparc64 platform.
* &a.jake; <[81]jake@>
* &a.phk; <[82]phk@>
* &a.tmm; <[83]tmm@>
* &a.obrien; <[84]obrien@>
* &a.kensmith; <[85]kensmith@>
* &a.murray; <[86]murray@>
* &a.rwatson; <[87]rwatson@>
_________________________________________________________________
Donations Team <[88]donations@>
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 [89]FreeBSD Donations Liasion page.
* &a.wilko; <[90]wilko@>
* &a.brueffer; <[91]brueffer@>
* &a.obrien; <[92]obrien@>
* &a.trhodes; <[93]trhodes@>
* Daniel Seuffert <[94]ds@>
* &a.rwatson; <[95]rwatson@>
Marketing Team <[96]marketing@>
Press contact, marketing, interviews, information.
* Steven Beedle <[97]steven at zna.com>
* Denise Ebery <[98]denise at offmyserver.com>
* Deb Goodkin <[99]deb@>
* &a.jkoshy; <[100]jkoshy@>
* Dru Lavigne <[101]dlavigne6 at sympatico.ca>
* &a.mwlucas; <[102]mwlucas@>
* &a.imp; <[103]imp@>
* Kris Moore <[104]kris at pcbsd.org>
* &a.murray; <[105]murray@>
* Matt Olander <[106]matt@>
* Jeremy C. Reed <[107]reed at reedmedia.net>
* &a.rwatson; <[108]rwatson@>
Security Team <[109]secteam@>
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
[110]FreeBSD Security Officer Charter describes the duties and
responsibilities of the Security Officer in greater detail.
* &a.mnag; <[111]mnag@>
* &a.remko; <[112]remko@>
* &a.gnn; <[113]gnn@>
* &a.simon; <[114]simon@> (Officer Deputy)
* &a.philip; <[115]philip@>
* &a.cperciva; <[116]cperciva@> (Officer)
* &a.csjp; <[117]csjp@>
* &a.des; <[118]des@>
* &a.nectar; <[119]nectar@> (Officer Emeritus)
* &a.rwatson; <[120]rwatson@> (Core Team Liasion)
_________________________________________________________________
Core Team Secretary <[121]core-secretary@>
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.
* &a.joel; <[122]joel@>
Port Management Team Secretary <[123]portmgr-secretary@>
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.
* &a.erwin; <[124]erwin@>
Security Team Secretary <[125]secteam-secretary@>
The FreeBSD Security Team Secretary will make sure someone responds to
incoming emails towards the Security Team. He will acknowledge the
recievement 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.
* &a.remko; <[126]remko@>
_________________________________________________________________
Accounts Team <[127]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.
* &a.markm; <[128]markm@>
* &a.simon; <[129]simon@>
* &a.kensmith; <[130]kensmith@>
* &a.dhw; <[131]dhw@>
Backups Administrators <[132]backups@>
The Backups Administrators handles all backups on the FreeBSD cluster.
* &a.simon; <[133]simon@>
* &a.kensmith; <[134]kensmith@>
* &a.dhw; <[135]dhw@>
Bugmeisters & GNATS Administrators <[136]bugmeister@>
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.
* &a.ceri; <[137]ceri@>
* &a.linimon; <[138]linimon@>
Cluster Administrators <[139]clusteradm@>
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 admnistrators.
* &a.billf; <[140]billf@>
* &a.simon; <[141]simon@>
* &a.ps; <[142]ps@>
* &a.kensmith; <[143]kensmith@>
* &a.peter; <[144]peter@>
CVS doc/www Repository Managers <[145]dcvs@>
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 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.
* &a.joe; <[146]joe@>
* &a.kuriyama; <[147]kuriyama@>
* &a.markm; <[148]markm@>
* &a.simon; <[149]simon@>
CVS ports Repository Managers <[150]pcvs@>
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 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.
* &a.marcus; <[151]marcus@>
* &a.joe; <[152]joe@>
* &a.kuriyama; <[153]kuriyama@>
* &a.markm; <[154]markm@>
* &a.simon; <[155]simon@>
CVS src Repository Managers <[156]ncvs@>
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.
* &a.joe; <[157]joe@>
* &a.kuriyama; <[158]kuriyama@>
* &a.markm; <[159]markm@>
* &a.simon; <[160]simon@>
* &a.peter; <[161]peter@>
CVSup Mirror Site Coordinators <[162]cvsup-master@>
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.
* &a.kuriyama; <[163]kuriyama@>
* &a.jdp; <[164]jdp@>
* &a.kensmith; <[165]kensmith@>
DNS Administrators <[166]dnsadm@>
The DNS Administrators are responsible for managing DNS and related
services.
* &a.billf; <[167]billf@>
* &a.dg; <[168]dg@>
* &a.ps; <[169]ps@>
* &a.kensmith; <[170]kensmith@>
* &a.peter; <[171]peter@>
FTP/WWW Mirror Site Coordinators <[172]mirror-admin@>
The FTP/WWW Mirror Site Coordinators coordinates 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.
* &a.kuriyama; <[173]kuriyama@>
* &a.kensmith; <[174]kensmith@>
Perforce Repository Administrators <[175]perforce-admin@>
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.
* &a.scottl; <[176]scottl@>
* &a.kensmith; <[177]kensmith@>
* &a.gordon; <[178]gordon@>
* &a.rwatson; <[179]rwatson@>
* &a.peter; <[180]peter@>
* &a.dhw; <[181]dhw@>
Postmaster Team <[182]postmaster@>
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
projects mail services, such as having troll-, spam- and
virus-filters.
* &a.jmb; <[183]jmb@>
* &a.brd; <[184]brd@>
* &a.dhw; <[185]dhw@>
Reference Systems Administrators <[186]refadm@>
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.
* &a.jake; <[187]jake@>
* &a.billf; <[188]billf@>
* &a.markm; <[189]markm@>
* &a.simon; <[190]simon@>
* &a.obrien; <[191]obrien@>
* &a.ps; <[192]ps@>
* &a.kensmith; <[193]kensmith@>
* &a.peter; <[194]peter@>
* &a.dhw; <[195]dhw@>
&footer;
References
1. file://localhost/tmp/tmpNE7NQT.html#t-core
2. file://localhost/tmp/tmpNE7NQT.html#t-doceng
3. file://localhost/tmp/tmpNE7NQT.html#t-portmgr
4. file://localhost/tmp/tmpNE7NQT.html#t-re
5. file://localhost/tmp/tmpNE7NQT.html#t-re-alpha
6. file://localhost/tmp/tmpNE7NQT.html#t-re-amd64
7. file://localhost/tmp/tmpNE7NQT.html#t-re-ia64
8. file://localhost/tmp/tmpNE7NQT.html#t-re-x86
9. file://localhost/tmp/tmpNE7NQT.html#t-re-pc98
10. file://localhost/tmp/tmpNE7NQT.html#t-re-ppc
11. file://localhost/tmp/tmpNE7NQT.html#t-re-sparc64
12. file://localhost/tmp/tmpNE7NQT.html#t-donations
13. file://localhost/tmp/tmpNE7NQT.html#t-marketing
14. file://localhost/tmp/tmpNE7NQT.html#t-secteam
15. file://localhost/tmp/tmpNE7NQT.html#t-core-secretary
16. file://localhost/tmp/tmpNE7NQT.html#t-portmgr-secretary
17. file://localhost/tmp/tmpNE7NQT.html#t-secteam-secretary
18. file://localhost/tmp/tmpNE7NQT.html#t-accounts
19. file://localhost/tmp/tmpNE7NQT.html#t-backups
20. file://localhost/tmp/tmpNE7NQT.html#t-bugmeister
21. file://localhost/tmp/tmpNE7NQT.html#t-clusteradm
22. file://localhost/tmp/tmpNE7NQT.html#t-dcvs
23. file://localhost/tmp/tmpNE7NQT.html#t-pcvs
24. file://localhost/tmp/tmpNE7NQT.html#t-ncvs
25. file://localhost/tmp/tmpNE7NQT.html#t-cvsup-master
26. file://localhost/tmp/tmpNE7NQT.html#t-dnsadm
27. file://localhost/tmp/tmpNE7NQT.html#t-mirror-admin
28. file://localhost/tmp/tmpNE7NQT.html#t-perforce-admin
29. file://localhost/tmp/tmpNE7NQT.html#t-postmaster
30. file://localhost/tmp/tmpNE7NQT.html#t-refadm
31. mailto:core@
32. mailto:wilko@
33. mailto:brooks@
34. mailto:keramida@
35. mailto:imp@
36. mailto:gnn@
37. mailto:wes@
38. mailto:hrs@
39. mailto:murray@
40. mailto:rwatson@
41. mailto:doceng@
42. file://localhost/internal/doceng.html
43. mailto:nik@
44. mailto:blackend@
45. mailto:hrs@
46. mailto:murray@
47. mailto:portmgr@
48. file://localhost/portmgr/charter.html
49. mailto:marcus@
50. mailto:clement@
51. mailto:erwin@
52. mailto:linimon@
53. mailto:pav@
54. mailto:kris@
55. mailto:krion@
56. mailto:re@
57. file://localhost/releng/charter.html
58. mailto:mux@
59. mailto:bmah@
60. mailto:hrs@
61. mailto:kensmith@
62. mailto:murray@
63. mailto:rwatson@
64. mailto:dwhite@
65. mailto:re-alpha@
66. mailto:wilko@
67. mailto:murray@
68. mailto:rwatson@
69. mailto:re-amd64@
70. mailto:obrien@
71. mailto:re-ia64@
72. mailto:marcel@
73. mailto:re-x86@
74. mailto:murray@
75. mailto:rwatson@
76. mailto:re-pc98@
77. mailto:nyan@
78. mailto:re-ppc@
79. mailto:grehan@
80. mailto:re-sparc64@
81. mailto:jake@
82. mailto:phk@
83. mailto:tmm@
84. mailto:obrien@
85. mailto:kensmith@
86. mailto:murray@
87. mailto:rwatson@
88. mailto:donations@
89. file://localhost/donations/
90. mailto:wilko@
91. mailto:brueffer@
92. mailto:obrien@
93. mailto:trhodes@
94. mailto:ds@
95. mailto:rwatson@
96. mailto:marketing@
97. mailto:steven at zna.com
98. mailto:denise at offmyserver.com
99. mailto:deb@
100. mailto:jkoshy@
101. mailto:dlavigne6 at sympatico.ca
102. mailto:mwlucas@
103. mailto:imp@
104. mailto:kris at pcbsd.org
105. mailto:murray@
106. mailto:matt@
107. mailto:reed at reedmedia.net
108. mailto:rwatson@
109. mailto:secteam@
110. file://localhost/security/charter.html
111. mailto:mnag@
112. mailto:remko@
113. mailto:gnn@
114. mailto:simon@
115. mailto:philip@
116. mailto:cperciva@
117. mailto:csjp@
118. mailto:des@
119. mailto:nectar@
120. mailto:rwatson@
121. mailto:core-secretary@
122. mailto:joel@
123. mailto:portmgr-secretary@
124. mailto:erwin@
125. mailto:secteam-secretary@
126. mailto:remko@
127. mailto:accounts@
128. mailto:markm@
129. mailto:simon@
130. mailto:kensmith@
131. mailto:dhw@
132. mailto:backups@
133. mailto:simon@
134. mailto:kensmith@
135. mailto:dhw@
136. mailto:bugmeister@
137. mailto:ceri@
138. mailto:linimon@
139. mailto:clusteradm@
140. mailto:billf@
141. mailto:simon@
142. mailto:ps@
143. mailto:kensmith@
144. mailto:peter@
145. mailto:dcvs@
146. mailto:joe@
147. mailto:kuriyama@
148. mailto:markm@
149. mailto:simon@
150. mailto:pcvs@
151. mailto:marcus@
152. mailto:joe@
153. mailto:kuriyama@
154. mailto:markm@
155. mailto:simon@
156. mailto:ncvs@
157. mailto:joe@
158. mailto:kuriyama@
159. mailto:markm@
160. mailto:simon@
161. mailto:peter@
162. mailto:cvsup-master@
163. mailto:kuriyama@
164. mailto:jdp@
165. mailto:kensmith@
166. mailto:dnsadm@
167. mailto:billf@
168. mailto:dg@
169. mailto:ps@
170. mailto:kensmith@
171. mailto:peter@
172. mailto:mirror-admin@
173. mailto:kuriyama@
174. mailto:kensmith@
175. mailto:perforce-admin@
176. mailto:scottl@
177. mailto:kensmith@
178. mailto:gordon@
179. mailto:rwatson@
180. mailto:peter@
181. mailto:dhw@
182. mailto:postmaster@
183. mailto:jmb@
184. mailto:brd@
185. mailto:dhw@
186. mailto:refadm@
187. mailto:jake@
188. mailto:billf@
189. mailto:markm@
190. mailto:simon@
191. mailto:obrien@
192. mailto:ps@
193. mailto:kensmith@
194. mailto:peter@
195. mailto:dhw@
More information about the freebsd-doc
mailing list