| 1 |
.\" -*- mode: troff; coding: utf-8 -*- |
| 2 |
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) |
| 3 |
.\" |
| 4 |
.\" Standard preamble: |
| 5 |
.\" ======================================================================== |
| 6 |
.de Sp \" Vertical space (when we can't use .PP) |
| 7 |
.if t .sp .5v |
| 8 |
.if n .sp |
| 9 |
.. |
| 10 |
.de Vb \" Begin verbatim text |
| 11 |
.ft CW |
| 12 |
.nf |
| 13 |
.ne \\$1 |
| 14 |
.. |
| 15 |
.de Ve \" End verbatim text |
| 16 |
.ft R |
| 17 |
.fi |
| 18 |
.. |
| 19 |
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. |
| 20 |
.ie n \{\ |
| 21 |
. ds C` "" |
| 22 |
. ds C' "" |
| 23 |
'br\} |
| 24 |
.el\{\ |
| 25 |
. ds C` |
| 26 |
. ds C' |
| 27 |
'br\} |
| 28 |
.\" |
| 29 |
.\" Escape single quotes in literal strings from groff's Unicode transform. |
| 30 |
.ie \n(.g .ds Aq \(aq |
| 31 |
.el .ds Aq ' |
| 32 |
.\" |
| 33 |
.\" If the F register is >0, we'll generate index entries on stderr for |
| 34 |
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
| 35 |
.\" entries marked with X<> in POD. Of course, you'll have to process the |
| 36 |
.\" output yourself in some meaningful fashion. |
| 37 |
.\" |
| 38 |
.\" Avoid warning from groff about undefined register 'F'. |
| 39 |
.de IX |
| 40 |
.. |
| 41 |
.nr rF 0 |
| 42 |
.if \n(.g .if rF .nr rF 1 |
| 43 |
.if (\n(rF:(\n(.g==0)) \{\ |
| 44 |
. if \nF \{\ |
| 45 |
. de IX |
| 46 |
. tm Index:\\$1\t\\n%\t"\\$2" |
| 47 |
.. |
| 48 |
. if !\nF==2 \{\ |
| 49 |
. nr % 0 |
| 50 |
. nr F 2 |
| 51 |
. \} |
| 52 |
. \} |
| 53 |
.\} |
| 54 |
.rr rF |
| 55 |
.\" ======================================================================== |
| 56 |
.\" |
| 57 |
.IX Title "PERLGOV 1" |
| 58 |
.TH PERLGOV 1 2025-11-16 "perl v5.40.1" "Perl Programmers Reference Guide" |
| 59 |
.\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 60 |
.\" way too many mistakes in technical documents. |
| 61 |
.if n .ad l |
| 62 |
.nh |
| 63 |
.SH NAME |
| 64 |
perlgov \- Perl Rules of Governance |
| 65 |
.SH PREAMBLE |
| 66 |
.IX Header "PREAMBLE" |
| 67 |
We are forming a system of governance for development of the Perl programming |
| 68 |
language. |
| 69 |
.PP |
| 70 |
The scope of governance includes the language definition, its |
| 71 |
implementation, its test suite, its documentation, and the policies and |
| 72 |
procedures by which it is developed and maintained. |
| 73 |
.PP |
| 74 |
The system of governance includes definitions of the groups that will make |
| 75 |
decisions, the rules by which these groups are formed and changed, and the |
| 76 |
enumerated powers and constraints on the activities of these governing |
| 77 |
groups. |
| 78 |
.PP |
| 79 |
In forming a system of governance, we seek to achieve the following goals: |
| 80 |
.IP \(bu 4 |
| 81 |
We want a system that is functional. That means the governing groups may |
| 82 |
decide to undertake large changes, or they may decide to act conservatively, |
| 83 |
but they will act with intent and clear communication rather than fail to reach |
| 84 |
decisions when needed. |
| 85 |
.IP \(bu 4 |
| 86 |
We want a system that is trusted. That means that a reasonable contributor to |
| 87 |
Perl might disagree with decisions made by the governing groups, but will |
| 88 |
accept that they were made in good faith in consultation with relevant |
| 89 |
communities outside the governing groups. |
| 90 |
.IP \(bu 4 |
| 91 |
We want a system that is sustainable. That means it has provisions to |
| 92 |
self-modify, including ways of adding new members to the governing groups, ways |
| 93 |
to survive members becoming inactive, and ways of amending the rules of |
| 94 |
governance themselves if needed. |
| 95 |
.IP \(bu 4 |
| 96 |
We want a system that is transparent. That means that it will prefer policies |
| 97 |
that manage ordinary matters in public, and it will prefer secrecy in a limited |
| 98 |
number of situations. |
| 99 |
.IP \(bu 4 |
| 100 |
We want a system that is respectful. That means that it will establish |
| 101 |
standards of civil discourse that allow for healthy disagreement but avoid |
| 102 |
rancor and hostility in the community for which it is responsible. |
| 103 |
.SH Mandate |
| 104 |
.IX Header "Mandate" |
| 105 |
Perl language governance shall work to: |
| 106 |
.IP \(bu 4 |
| 107 |
Maintain the quality, stability, and continuity of the Perl language and |
| 108 |
interpreter |
| 109 |
.IP \(bu 4 |
| 110 |
Guide the evolution of the Perl language and interpreter |
| 111 |
.IP \(bu 4 |
| 112 |
Establish and oversee the policies, procedures, systems, and mechanisms that |
| 113 |
enable a community of contributors to the Perl language and interpreter |
| 114 |
.IP \(bu 4 |
| 115 |
Encourage discussion and consensus among contributors as preferential to formal |
| 116 |
decision making by governance groups |
| 117 |
.IP \(bu 4 |
| 118 |
Facilitate communication between contributors and external stakeholders in the |
| 119 |
broader Perl ecosystem |
| 120 |
.SH Definitions |
| 121 |
.IX Header "Definitions" |
| 122 |
This document describes three roles involved in governance: |
| 123 |
.IP """Core Team""" 4 |
| 124 |
.IX Item """Core Team""" |
| 125 |
.PD 0 |
| 126 |
.IP """Steering Council""" 4 |
| 127 |
.IX Item """Steering Council""" |
| 128 |
.IP """Vote Administrator""" 4 |
| 129 |
.IX Item """Vote Administrator""" |
| 130 |
.PD |
| 131 |
.PP |
| 132 |
A section on each follows. |
| 133 |
.SS "The Core Team" |
| 134 |
.IX Subsection "The Core Team" |
| 135 |
The Core Team are a group of trusted volunteers involved in the ongoing |
| 136 |
development of the Perl language and interpreter. They are not required to be |
| 137 |
language developers or committers. |
| 138 |
.PP |
| 139 |
References to specific votes are explained in the "Rules for Voting" section. |
| 140 |
.PP |
| 141 |
\fIPowers\fR |
| 142 |
.IX Subsection "Powers" |
| 143 |
.PP |
| 144 |
In addition to their contributions to the Perl language, the Core Team sets |
| 145 |
the rules of Perl governance, decides who participates in what role in |
| 146 |
governance, and delegates substantial decision making power to the Steering |
| 147 |
Council. |
| 148 |
.PP |
| 149 |
Specifically: |
| 150 |
.IP \(bu 4 |
| 151 |
They elect the Steering Council and have the power to remove Steering |
| 152 |
Council members. |
| 153 |
.IP \(bu 4 |
| 154 |
In concert with the Steering Council, they manage Core Team membership. |
| 155 |
.IP \(bu 4 |
| 156 |
In concert with the Steering Council, they have the power to modify the Perl |
| 157 |
Rules of Governance. |
| 158 |
.PP |
| 159 |
The Core Team do not have any authority over parts of the Perl ecosystem |
| 160 |
unrelated to developing and releasing the language itself. These include, but |
| 161 |
are not limited to: |
| 162 |
.IP \(bu 4 |
| 163 |
The Perl Foundation |
| 164 |
.IP \(bu 4 |
| 165 |
CPAN administration and CPAN authors |
| 166 |
.IP \(bu 4 |
| 167 |
perl.org, metacpan.org, and other community-maintained websites and services |
| 168 |
.IP \(bu 4 |
| 169 |
Perl conferences and events, except those organized directly by the Core Team |
| 170 |
.IP \(bu 4 |
| 171 |
Perl-related intellectual property legally owned by third-parties, except as |
| 172 |
allowed by applicable licenses or agreements |
| 173 |
.PP |
| 174 |
\fIMembership\fR |
| 175 |
.IX Subsection "Membership" |
| 176 |
.PP |
| 177 |
The initial Core Team members will be specified when this document is |
| 178 |
first ratified. |
| 179 |
.PP |
| 180 |
Any Core Team member may nominate someone to be added to the Core Team by |
| 181 |
sending the nomination to the Steering Council. The Steering Council must |
| 182 |
approve or reject the nomination. If approved, the Steering Council will |
| 183 |
organize a Membership Change Vote to ratify the addition. |
| 184 |
.PP |
| 185 |
Core Team members should demonstrate: |
| 186 |
.IP \(bu 4 |
| 187 |
A solid track record of being constructive and helpful |
| 188 |
.IP \(bu 4 |
| 189 |
Significant contributions to the project's goals, in any form |
| 190 |
.IP \(bu 4 |
| 191 |
Willingness to dedicate some time to improving Perl |
| 192 |
.PP |
| 193 |
Contributions are not limited to code. Here is an incomplete list of areas |
| 194 |
where contributions may be considered for joining the Core Team: |
| 195 |
.IP \(bu 4 |
| 196 |
Working on community management and outreach |
| 197 |
.IP \(bu 4 |
| 198 |
Providing support on mailing lists, IRC, or other forums |
| 199 |
.IP \(bu 4 |
| 200 |
Triaging tickets |
| 201 |
.IP \(bu 4 |
| 202 |
Writing patches (code, docs, or tests) |
| 203 |
.IP \(bu 4 |
| 204 |
Reviewing patches (code, docs, or tests) |
| 205 |
.IP \(bu 4 |
| 206 |
Participating in design discussions |
| 207 |
.IP \(bu 4 |
| 208 |
Providing expertise in a particular domain (security, i18n, etc.) |
| 209 |
.IP \(bu 4 |
| 210 |
Managing Perl infrastructure (websites, CI, documentation, etc.) |
| 211 |
.IP \(bu 4 |
| 212 |
Maintaining significant projects in the Perl ecosystem |
| 213 |
.IP \(bu 4 |
| 214 |
Creating visual designs |
| 215 |
.PP |
| 216 |
Core Team membership acknowledges sustained and valuable efforts that align |
| 217 |
well with the philosophy and the goals of the Perl project. |
| 218 |
.PP |
| 219 |
Core Team members are expected to act as role models for the community and |
| 220 |
custodians of the project, on behalf of the community and all those who rely |
| 221 |
on Perl. |
| 222 |
.PP |
| 223 |
\fITerm\fR |
| 224 |
.IX Subsection "Term" |
| 225 |
.PP |
| 226 |
Core Team members serve until they are removed. |
| 227 |
.PP |
| 228 |
\fIRemoval\fR |
| 229 |
.IX Subsection "Removal" |
| 230 |
.PP |
| 231 |
Core Team Members may resign their position at any time. |
| 232 |
.PP |
| 233 |
In exceptional circumstances, it may be necessary to remove someone from the |
| 234 |
Core Team against their will, such as for flagrant or repeated violations of a |
| 235 |
Code of Conduct. Any Core Team member may send a recall request to the |
| 236 |
Steering Council naming the individual to be removed. The Steering Council |
| 237 |
must approve or reject the recall request. If approved, the Steering Council |
| 238 |
will organize a Membership Change vote to ratify the removal. |
| 239 |
.PP |
| 240 |
If the removed member is also on the Steering Council, then they are removed |
| 241 |
from the Steering Council as well. |
| 242 |
.PP |
| 243 |
\fIInactivity\fR |
| 244 |
.IX Subsection "Inactivity" |
| 245 |
.PP |
| 246 |
Core Team members who have stopped contributing are encouraged to declare |
| 247 |
themselves "inactive". Inactive members do not nominate or vote. Inactive |
| 248 |
members may declare themselves active at any time, except when a vote has been |
| 249 |
proposed and is not concluded. Eligibility to nominate or vote will be |
| 250 |
determined by the Vote Administrator. |
| 251 |
.PP |
| 252 |
To record and honor their contributions, inactive Core Team members will |
| 253 |
continue to be listed alongside active members. |
| 254 |
.PP |
| 255 |
\fINo Confidence in the Steering Council\fR |
| 256 |
.IX Subsection "No Confidence in the Steering Council" |
| 257 |
.PP |
| 258 |
The Core Team may remove either a single Steering Council member or the entire |
| 259 |
Steering Council via a No Confidence Vote. |
| 260 |
.PP |
| 261 |
A No Confidence Vote is triggered when a Core Team member calls for one |
| 262 |
publicly on an appropriate project communication channel, and another Core |
| 263 |
Team member seconds the proposal. |
| 264 |
.PP |
| 265 |
If a No Confidence Vote removes all Steering Council members, the Vote |
| 266 |
Administrator of the No Confidence Vote will then administer an election |
| 267 |
to select a new Steering Council. |
| 268 |
.PP |
| 269 |
\fIAmending Perl Rules of Governance\fR |
| 270 |
.IX Subsection "Amending Perl Rules of Governance" |
| 271 |
.PP |
| 272 |
Any Core Team member may propose amending the Perl Rules of Governance by |
| 273 |
sending a proposal to the Steering Council. The Steering Council must decide |
| 274 |
to approve or reject the proposal. If approved, the Steering Council will |
| 275 |
organize an Amendment Vote. |
| 276 |
.PP |
| 277 |
\fIRules for Voting\fR |
| 278 |
.IX Subsection "Rules for Voting" |
| 279 |
.PP |
| 280 |
Membership Change, Amendment, and No Confidence Votes require 2/3 of |
| 281 |
participating votes from Core Team members to pass. |
| 282 |
.PP |
| 283 |
A Vote Administrator must be selected following the rules in the "Vote |
| 284 |
Administrator" section. |
| 285 |
.PP |
| 286 |
The vote occurs in two steps: |
| 287 |
.IP 1. 4 |
| 288 |
The Vote Administrator describes the proposal being voted upon. The Core Team |
| 289 |
then may discuss the matter in advance of voting. |
| 290 |
.IP 2. 4 |
| 291 |
Active Core Team members vote in favor or against the proposal. Voting is |
| 292 |
performed anonymously. |
| 293 |
.PP |
| 294 |
For a Membership Change Vote, each phase will last one week. For Amendment and |
| 295 |
No Confidence Votes, each phase will last two weeks. |
| 296 |
.SS "The Steering Council" |
| 297 |
.IX Subsection "The Steering Council" |
| 298 |
The Steering Council is a 3\-person committee, elected by the Core |
| 299 |
Team. Candidates are not required to be members of the Core Team. Non-member |
| 300 |
candidates are added to the Core Team if elected as if by a Membership Change |
| 301 |
Vote. |
| 302 |
.PP |
| 303 |
References to specific elections are explained in the "Rules for Elections" section. |
| 304 |
.PP |
| 305 |
\fIPowers\fR |
| 306 |
.IX Subsection "Powers" |
| 307 |
.PP |
| 308 |
The Steering Council has broad authority to make decisions about the |
| 309 |
development of the Perl language, the interpreter, and all other components, |
| 310 |
systems and processes that result in new releases of the language interpreter. |
| 311 |
.PP |
| 312 |
For example, it can: |
| 313 |
.IP \(bu 4 |
| 314 |
Manage the schedule and process for shipping new releases |
| 315 |
.IP \(bu 4 |
| 316 |
Establish procedures for proposing, discussing and deciding upon changes to the |
| 317 |
language |
| 318 |
.IP \(bu 4 |
| 319 |
Delegate power to individuals on or outside the Steering Council |
| 320 |
.PP |
| 321 |
Decisions of the Steering Council will be made by majority vote of non-vacant |
| 322 |
seats on the council. |
| 323 |
.PP |
| 324 |
The Steering Council should look for ways to use these powers as little as |
| 325 |
possible. Instead of voting, it's better to seek consensus. Instead of ruling |
| 326 |
on individual cases, it's better to define standards and processes that apply |
| 327 |
to all cases. |
| 328 |
.PP |
| 329 |
As with the Core Team, the Steering Council does not have any authority over |
| 330 |
parts of the Perl ecosystem unrelated to developing and releasing the language |
| 331 |
itself. |
| 332 |
.PP |
| 333 |
The Steering Council does not have the power to modify the Perl Rules of |
| 334 |
Governance, except as provided in the section "Amending Perl Rules of |
| 335 |
Governance". |
| 336 |
.PP |
| 337 |
\fITerm\fR |
| 338 |
.IX Subsection "Term" |
| 339 |
.PP |
| 340 |
A new Steering Council will be chosen by a Term Election after each stable |
| 341 |
feature release (that is, change to \f(CW\*(C`PERL_REVISION\*(C'\fR or \f(CW\*(C`PERL_VERSION\*(C'\fR) or |
| 342 |
after two years, whichever comes first. The Term Election will be organized |
| 343 |
within two weeks of the triggering event. The council members will serve until |
| 344 |
the completion of the next Term Election unless they are removed. |
| 345 |
.PP |
| 346 |
\fIRemoval\fR |
| 347 |
.IX Subsection "Removal" |
| 348 |
.PP |
| 349 |
Steering Council members may resign their position at any time. |
| 350 |
.PP |
| 351 |
Whenever there are vacancies on the Steering Council, the council will |
| 352 |
organize a Special Election within one week after the vacancy occurs. If the |
| 353 |
entire Steering Council is ever vacant, a Term Election will be held instead. |
| 354 |
.PP |
| 355 |
The Steering Council may defer the Special Election for up to twelve weeks. |
| 356 |
Their intent to do so must be publicly stated to the Core Team. If any active |
| 357 |
Core Team member objects within one week, the Special Election must be |
| 358 |
organized within two weeks. At any time, the Steering Council may choose to |
| 359 |
cancel the deferment and immediately commence organizing a Special Election. |
| 360 |
.PP |
| 361 |
If a Steering Council member is deceased, or drops out of touch and cannot be |
| 362 |
contacted for a month or longer, then the rest of the council may vote to |
| 363 |
declare their seat vacant. If an absent member returns after such a |
| 364 |
declaration is made, they are not reinstated automatically, but may run in the |
| 365 |
Special Election to fill the vacancy. |
| 366 |
.PP |
| 367 |
Otherwise, Steering Council members may only be removed before the end of |
| 368 |
their term through a No Confidence Vote by the Core Team. |
| 369 |
.PP |
| 370 |
\fIRules for Elections\fR |
| 371 |
.IX Subsection "Rules for Elections" |
| 372 |
.PP |
| 373 |
Term and Special Election are ranked-choice votes to construct an ordered list |
| 374 |
of candidates to fill vacancies in the Steering Council. |
| 375 |
.PP |
| 376 |
A Vote Administrator must be selected following the rules in the "Vote |
| 377 |
Administrator" section. |
| 378 |
.PP |
| 379 |
Both Term and Special Elections occur in two stages: |
| 380 |
.IP 1. 4 |
| 381 |
Candidates advertise their interest in serving. Candidates must be nominated by |
| 382 |
an active Core Team member. Self-nominations are allowed. Nominated candidates |
| 383 |
may share a statement about their candidacy with the Core Team. |
| 384 |
.IP 2. 4 |
| 385 |
If there are no more candidates than open seats, no vote is required. The |
| 386 |
candidates will be declared to have won when the nomination period ends. |
| 387 |
.Sp |
| 388 |
Otherwise, active Core Team Members vote by ranking all candidates. Voting is |
| 389 |
performed anonymously. After voting is complete, candidates are ranked using |
| 390 |
the Condorcet Internet Voting Service's proportional representation mode. If a |
| 391 |
tie occurs, it may be resolved by mutual agreement among the tied candidates, |
| 392 |
or else the tie will be resolved through random selection by the Vote |
| 393 |
Administrator. |
| 394 |
.PP |
| 395 |
Anyone voted off the Core Team is not eligible to be a candidate for Steering |
| 396 |
Council unless re-instated to the Core Team. |
| 397 |
.PP |
| 398 |
For a Term Election, each phase will last two weeks. At the end of the second |
| 399 |
phase, the top three ranked candidates are elected as the new Steering Council. |
| 400 |
.PP |
| 401 |
For a Special Election, each phase will last one week. At the end of the |
| 402 |
second phase, vacancies are filled from the ordered list of candidates until |
| 403 |
no vacancies remain. |
| 404 |
.PP |
| 405 |
The election of the first Steering Council will be a Term Election. Ricardo |
| 406 |
Signes will be the Vote Administrator for the initial Term Election unless he |
| 407 |
is a candidate, in which case he will select a non-candidate administrator to |
| 408 |
replace him. |
| 409 |
.SS "The Vote Administrator" |
| 410 |
.IX Subsection "The Vote Administrator" |
| 411 |
Every election or vote requires a Vote Administrator who manages |
| 412 |
communication, collection of secret ballots, and all other necessary |
| 413 |
activities to complete the voting process. |
| 414 |
.PP |
| 415 |
Unless otherwise specified, the Steering Council selects the Vote |
| 416 |
Administrator. |
| 417 |
.PP |
| 418 |
A Vote Administrator must not be a member of the Steering Council nor a |
| 419 |
candidate or subject of the vote. A Vote Administrator may be a member of the |
| 420 |
Core Team and, if so, may cast a vote while also serving as administrator. If |
| 421 |
the Vote Administrator becomes a candidate during an election vote, they will |
| 422 |
appoint a non-candidate replacement. |
| 423 |
.PP |
| 424 |
If the entire Steering Council is vacant or is the subject of a No Confidence |
| 425 |
Vote, then the Core Team will select a Vote Administrator by consensus. If |
| 426 |
consensus cannot be reached within one week, the President of The Perl |
| 427 |
Foundation will select a Vote Administrator. |
| 428 |
.SH "Steering Council and Core Team Members" |
| 429 |
.IX Header "Steering Council and Core Team Members" |
| 430 |
The list below names the members of the Steering Council and Core Team |
| 431 |
responsible for creating the release of perl with which this document shipped. |
| 432 |
.PP |
| 433 |
Remember, though that if you're reading the copy of this document that was |
| 434 |
installed with perl, it's very likely out of date. Because every new stable |
| 435 |
feature release triggers an election, you're better off looking at the most |
| 436 |
up to date copy of this |
| 437 |
document <https://github.com/Perl/perl5/blob/blead/pod/perlgov.pod>, in the |
| 438 |
\&\fIblead\fR branch of Perl's git repository. Because it's git, you can also see |
| 439 |
how the membership has changed over time. |
| 440 |
.SH "Steering Council Members" |
| 441 |
.IX Header "Steering Council Members" |
| 442 |
.IP \(bu 4 |
| 443 |
Graham Knop |
| 444 |
.IP \(bu 4 |
| 445 |
Paul Evans |
| 446 |
.IP \(bu 4 |
| 447 |
Philippe Bruhat |
| 448 |
.SH "Core Team Members" |
| 449 |
.IX Header "Core Team Members" |
| 450 |
The current members of the Perl Core Team are: |
| 451 |
.SS "Active Members" |
| 452 |
.IX Subsection "Active Members" |
| 453 |
.IP "Chad Granum <[email protected]>" 4 |
| 454 |
.IX Item "Chad Granum <[email protected]>" |
| 455 |
.PD 0 |
| 456 |
.IP "Chris 'BinGOs' Williams <[email protected]>" 4 |
| 457 |
.IX Item "Chris 'BinGOs' Williams <[email protected]>" |
| 458 |
.IP "Craig Berry <[email protected]>" 4 |
| 459 |
.IX Item "Craig Berry <[email protected]>" |
| 460 |
.IP "Dagfinn Ilmari Mannsåker <[email protected]>" 4 |
| 461 |
.IX Item "Dagfinn Ilmari Mannsåker <[email protected]>" |
| 462 |
.IP "David Mitchell <[email protected]>" 4 |
| 463 |
.IX Item "David Mitchell <[email protected]>" |
| 464 |
.IP "Graham Knop <[email protected]>" 4 |
| 465 |
.IX Item "Graham Knop <[email protected]>" |
| 466 |
.IP "H. Merijn Brand <[email protected]>" 4 |
| 467 |
.IX Item "H. Merijn Brand <[email protected]>" |
| 468 |
.IP "Hugo van der Sanden <[email protected]>" 4 |
| 469 |
.IX Item "Hugo van der Sanden <[email protected]>" |
| 470 |
.IP "James E Keenan <[email protected]>" 4 |
| 471 |
.IX Item "James E Keenan <[email protected]>" |
| 472 |
.IP "Karen Etheridge <[email protected]>" 4 |
| 473 |
.IX Item "Karen Etheridge <[email protected]>" |
| 474 |
.IP "Karl Williamson <[email protected]>" 4 |
| 475 |
.IX Item "Karl Williamson <[email protected]>" |
| 476 |
.IP "Leon Timmermans <[email protected]>" 4 |
| 477 |
.IX Item "Leon Timmermans <[email protected]>" |
| 478 |
.IP "Matthew Horsfall <[email protected]>" 4 |
| 479 |
.IX Item "Matthew Horsfall <[email protected]>" |
| 480 |
.IP "Max Maischein <[email protected]>" 4 |
| 481 |
.IX Item "Max Maischein <[email protected]>" |
| 482 |
.IP "Neil Bowers <[email protected]>" 4 |
| 483 |
.IX Item "Neil Bowers <[email protected]>" |
| 484 |
.IP "Nicholas Clark <[email protected]>" 4 |
| 485 |
.IX Item "Nicholas Clark <[email protected]>" |
| 486 |
.IP "Nicolas R <[email protected]>" 4 |
| 487 |
.IX Item "Nicolas R <[email protected]>" |
| 488 |
.IP "Paul ""LeoNerd"" Evans <[email protected]>" 4 |
| 489 |
.IX Item "Paul ""LeoNerd"" Evans <[email protected]>" |
| 490 |
.IP "Philippe ""BooK"" Bruhat <[email protected]>" 4 |
| 491 |
.IX Item "Philippe ""BooK"" Bruhat <[email protected]>" |
| 492 |
.IP "Ricardo Signes <[email protected]>" 4 |
| 493 |
.IX Item "Ricardo Signes <[email protected]>" |
| 494 |
.IP "Steve Hay <[email protected]>" 4 |
| 495 |
.IX Item "Steve Hay <[email protected]>" |
| 496 |
.IP "Stuart Mackintosh <[email protected]>" 4 |
| 497 |
.IX Item "Stuart Mackintosh <[email protected]>" |
| 498 |
.IP "Todd Rinaldo <[email protected]>" 4 |
| 499 |
.IX Item "Todd Rinaldo <[email protected]>" |
| 500 |
.IP "Tony Cook <tony@develop\-help.com>" 4 |
| 501 |
.IX Item "Tony Cook <[email protected]>" |
| 502 |
.IP "Yves Orton <[email protected]>" 4 |
| 503 |
.IX Item "Yves Orton <[email protected]>" |
| 504 |
.PD |
| 505 |
.SS "Inactive Members" |
| 506 |
.IX Subsection "Inactive Members" |
| 507 |
.IP "Abhijit Menon-Sen <[email protected]>" 4 |
| 508 |
.IX Item "Abhijit Menon-Sen <[email protected]>" |
| 509 |
.PD 0 |
| 510 |
.IP "Andy Dougherty <[email protected]>" 4 |
| 511 |
.IX Item "Andy Dougherty <[email protected]>" |
| 512 |
.IP "David Golden <[email protected]>" 4 |
| 513 |
.IX Item "David Golden <[email protected]>" |
| 514 |
.IP "Jan Dubois <[email protected]>" 4 |
| 515 |
.IX Item "Jan Dubois <[email protected]>" |
| 516 |
.IP "Jason McIntosh <[email protected]>" 4 |
| 517 |
.IX Item "Jason McIntosh <[email protected]>" |
| 518 |
.IP "Jesse Vincent <[email protected]>" 4 |
| 519 |
.IX Item "Jesse Vincent <[email protected]>" |