Debian Codegraph @

upstream/fedora-44/man1/perlgov.1

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