Debian Codegraph @

upstream/opensuse-tumbleweed/man1/perlpolicy.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 "PERLPOLICY 1"
61 .TH PERLPOLICY 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 perlpolicy \- Various and sundry policies and commitments related to the Perl core
68 .SH DESCRIPTION
69 .IX Header "DESCRIPTION"
70 This document is the master document which records all written
71 policies about how the Perl 5 Porters collectively develop and maintain
72 the Perl core.
73 .SH GOVERNANCE
74 .IX Header "GOVERNANCE"
75 .SS "Perl 5 Porters"
76 .IX Subsection "Perl 5 Porters"
77 Subscribers to perl5\-porters (the porters themselves) come in several flavours.
78 Some are quiet curious lurkers, who rarely pitch in and instead watch
79 the ongoing development to ensure they\*(Aqre forewarned of new changes or
80 features in Perl. Some are representatives of vendors, who are there
81 to make sure that Perl continues to compile and work on their
82 platforms. Some patch any reported bug that they know how to fix,
83 some are actively patching their pet area (threads, Win32, the regexp
84 \&\-engine), while others seem to do nothing but complain. In other
85 words, it\*(Aqs your usual mix of technical people.
86 .PP
87 Among these people are the core Perl team. These are trusted volunteers
88 involved in the ongoing development of the Perl language and interpreter.
89 They are not required to be language developers or committers.
90 .PP
91 Over this group of porters presides Larry Wall. He has the final word
92 in what does and does not change in any of the Perl programming languages.
93 These days, Larry spends most of his time on Raku, while Perl 5 is
94 shepherded by a steering council of porters responsible for deciding what
95 goes into each release and ensuring that releases happen on a regular
96 basis.
97 .PP
98 Larry sees Perl development along the lines of the US government:
99 there\*(Aqs the Legislature (the porters, represented by the core team), the
100 Executive branch (the steering council), and the Supreme Court (Larry).
101 The legislature can discuss and submit patches to the executive branch
102 all they like, but the executive branch is free to veto them. Rarely,
103 the Supreme Court will side with the executive branch over the
104 legislature, or the legislature over the executive branch. Mostly,
105 however, the legislature and the executive branch are supposed to get
106 along and work out their differences without impeachment or court cases.
107 .PP
108 You might sometimes see reference to Rule 1 and Rule 2. Larry\*(Aqs power
109 as Supreme Court is expressed in The Rules:
110 .IP 1. 4
111 Larry is always by definition right about how Perl should behave.
112 This means he has final veto power on the core functionality.
113 .IP 2. 4
114 Larry is allowed to change his mind about any matter at a later date,
115 regardless of whether he previously invoked Rule 1.
116 .PP
117 Got that? Larry is always right, even when he was wrong. It\*(Aqs rare
118 to see either Rule exercised, but they are often alluded to.
119 .PP
120 For the specifics on how the members of the core team and steering
121 council are elected or rotated, consult perlgov, which spells it all
122 out in detail.
123 .SH "MAINTENANCE AND SUPPORT"
124 .IX Header "MAINTENANCE AND SUPPORT"
125 Perl 5 is developed by a community, not a corporate entity. Every change
126 contributed to the Perl core is the result of a donation. Typically, these
127 donations are contributions of code or time by individual members of our
128 community. On occasion, these donations come in the form of corporate
129 or organizational sponsorship of a particular individual or project.
130 .PP
131 As a volunteer organization, the commitments we make are heavily dependent
132 on the goodwill and hard work of individuals who have no obligation to
133 contribute to Perl.
134 .PP
135 That being said, we value Perl\*(Aqs stability and security and have long
136 had an unwritten covenant with the broader Perl community to support
137 and maintain releases of Perl.
138 .PP
139 This document codifies the support and maintenance commitments that
140 the Perl community should expect from Perl\*(Aqs developers:
141 .IP \(bu 4
142 We "officially" support the two most recent stable release series. 5.38.x
143 and earlier are now out of support. As of the release of 5.44.0, we will
144 "officially" end support for Perl 5.40.x, other than providing security
145 updates as described below.
146 .IP \(bu 4
147 To the best of our ability, we will attempt to fix critical issues
148 in the two most recent stable 5.x release series. Fixes for the
149 current release series take precedence over fixes for the previous
150 release series.
151 .IP \(bu 4
152 To the best of our ability, we will provide "critical" security patches
153 / releases for any major version of Perl whose 5.x.0 release was within
154 the past three years. We can only commit to providing these for the
155 most recent .y release in any 5.x.y series.
156 .IP \(bu 4
157 We will not provide security updates or bug fixes for development
158 releases of Perl.
159 .IP \(bu 4
160 We encourage vendors to ship the most recent supported release of
161 Perl at the time of their code freeze.
162 .IP \(bu 4
163 As a vendor, you may have a requirement to backport security fixes
164 beyond our 3 year support commitment. We can provide limited support and
165 advice to you as you do so and, where possible will try to apply
166 those patches to the relevant \-maint branches in git, though we may or
167 may not choose to make numbered releases or "official" patches
168 available. See "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec
169 for details on how to begin that process.
170 .SH "BACKWARD COMPATIBILITY AND DEPRECATION"
171 .IX Header "BACKWARD COMPATIBILITY AND DEPRECATION"
172 Our community has a long\-held belief that backward\-compatibility is a
173 virtue, even when the functionality in question is a design flaw.
174 .PP
175 We would all love to unmake some mistakes we\*(Aqve made over the past
176 decades. Living with every design error we\*(Aqve ever made can lead
177 to painful stagnation. Unwinding our mistakes is very, very
178 difficult. Doing so without actively harming our users is
179 nearly impossible.
180 .PP
181 Lately, ignoring or actively opposing compatibility with earlier versions
182 of Perl has come into vogue. Sometimes, a change is proposed which
183 wants to usurp syntax which previously had another meaning. Sometimes,
184 a change wants to improve previously\-crazy semantics.
185 .PP
186 Down this road lies madness.
187 .PP
188 Requiring end\-user programmers to change just a few language constructs,
189 even language constructs which no well\-educated developer would ever
190 intentionally use is tantamount to saying "you should not upgrade to
191 a new release of Perl unless you have 100% test coverage and can do a
192 full manual audit of your codebase." If we were to have tools capable of
193 reliably upgrading Perl source code from one version of Perl to another,
194 this concern could be significantly mitigated.
195 .PP
196 We want to ensure that Perl continues to grow and flourish in the coming
197 years and decades, but not at the expense of our user community.
198 .PP
199 Existing syntax and semantics should only be marked for destruction in
200 very limited circumstances. If they are believed to be very rarely used,
201 stand in the way of actual improvement to the Perl language or perl
202 interpreter, and if affected code can be easily updated to continue
203 working, they may be considered for removal. When in doubt, caution
204 dictates that we will favor backward compatibility. When a feature is
205 deprecated, a statement of reasoning describing the decision process
206 will be posted, and a link to it will be provided in the relevant
207 perldelta documents.
208 .PP
209 Using a lexical pragma to enable or disable legacy behavior should be
210 considered when appropriate, and in the absence of any pragma legacy
211 behavior should be enabled. Which backward\-incompatible changes are
212 controlled implicitly by a \*(Aquse v5.x.y\*(Aq is a decision which should be
213 made by the steering council in consultation with the community.
214 .PP
215 Historically, we\*(Aqve held ourselves to a far higher standard than
216 backward\-compatibility \-\- bugward\-compatibility. Any accident of
217 implementation or unintentional side\-effect of running some bit of code
218 has been considered to be a feature of the language to be defended with
219 the same zeal as any other feature or functionality. No matter how
220 frustrating these unintentional features may be to us as we continue
221 to improve Perl, these unintentional features often deserve our
222 protection. It is very important that existing software written in
223 Perl continue to work correctly. If end\-user developers have adopted a
224 bug as a feature, we need to treat it as such.
225 .PP
226 New syntax and semantics which don\*(Aqt break existing language constructs
227 and syntax have a much lower bar. They merely need to prove themselves
228 to be useful, elegant, well designed, and well tested. In most cases,
229 these additions will be marked as \fIexperimental\fR for some time. See
230 below for more on that.
231 .SS Terminology
232 .IX Subsection "Terminology"
233 To make sure we\*(Aqre talking about the same thing when we discuss the removal
234 of features or functionality from the Perl core, we have specific definitions
235 for a few words and phrases.
236 .IP experimental 4
237 .IX Item "experimental"
238 If something in the Perl core is marked as \fBexperimental\fR, we may change
239 its behaviour, deprecate or remove it without notice. While we\*(Aqll always
240 do our best to smooth the transition path for users of experimental
241 features, you should contact the perl5\-porters mailinglist if you find
242 an experimental feature useful and want to help shape its future.
243 .Sp
244 Experimental features must be experimental in two stable releases before being
245 marked non\-experimental. Experimental features will only have their
246 experimental status revoked when they no longer have any design\-changing bugs
247 open against them and when they have remained unchanged in behavior for the
248 entire length of a development cycle. In other words, a feature present in
249 v5.20.0 may be marked no longer experimental in v5.22.0 if and only if its
250 behavior is unchanged throughout all of v5.21.
251 .IP deprecated 4
252 .IX Item "deprecated"
253 If something in the Perl core is marked as \fBdeprecated\fR, we may remove it
254 from the core in the future, though we might not. Generally, backward
255 incompatible changes will have deprecation warnings for two release
256 cycles before being removed, but may be removed after just one cycle if
257 the risk seems quite low or the benefits quite high.
258 .Sp
259 As of
260 Perl 5.12, deprecated features and modules warn the user as they\*(Aqre used.
261 When a module is deprecated, it will also be made available on CPAN.
262 Installing it from CPAN will silence deprecation warnings for that module.
263 .Sp
264 If you use a deprecated feature or module and believe that its removal from
265 the Perl core would be a mistake, please contact the perl5\-porters
266 mailinglist and plead your case. We don\*(Aqt deprecate things without a good
267 reason, but sometimes there\*(Aqs a counterargument we haven\*(Aqt considered.
268 Historically, we did not distinguish between "deprecated" and "discouraged"
269 features.
270 .IP discouraged 4
271 .IX Item "discouraged"
272 From time to time, we may mark language constructs and features which we
273 consider to have been mistakes as \fBdiscouraged\fR. Discouraged features
274 aren\*(Aqt currently candidates for removal, but
275 we may later deprecate them if they\*(Aqre found to stand in the way of a
276 significant improvement to the Perl core.
277 .IP removed 4
278 .IX Item "removed"
279 Once a feature, construct or module has been marked as deprecated, we
280 may remove it from the Perl core. Unsurprisingly,
281 we say we\*(Aqve \fBremoved\fR these things. When a module is removed, it will
282 no longer ship with Perl, but will continue to be available on CPAN.
283 .SH "MAINTENANCE BRANCHES"
284 .IX Header "MAINTENANCE BRANCHES"
285 New releases of maintenance branches should only contain changes that fall into
286 one of the "acceptable" categories set out below, but must not contain any
287 changes that fall into one of the "unacceptable" categories. (For example, a
288 fix for a crashing bug must not be included if it breaks binary compatibility.)
289 .PP
290 It is not necessary to include every change meeting these criteria, and in
291 general the focus should be on addressing security issues, crashing bugs,
292 regressions and serious installation issues. The temptation to include a
293 plethora of minor changes that don\*(Aqt affect the installation or execution of
294 perl (e.g. spelling corrections in documentation) should be resisted in order
295 to reduce the overall risk of overlooking something. The intention is to
296 create maintenance releases which are both worthwhile and which users can have
297 full confidence in the stability of. (A secondary concern is to avoid burning
298 out the maint\-release manager or overwhelming other committers voting on
299 changes to be included (see "Getting changes into a maint branch"
300 below).)
301 .PP
302 The following types of change may be considered acceptable, as long as they do
303 not also fall into any of the "unacceptable" categories set out below:
304 .IP \(bu 4
305 Patches that fix CVEs or security issues. These changes should
306 be passed using the security reporting mechanism rather than applied
307 directly; see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec.
308 .IP \(bu 4
309 Patches that fix crashing bugs, assertion failures and
310 memory corruption but which do not otherwise change perl\*(Aqs
311 functionality or negatively impact performance.
312 .IP \(bu 4
313 Patches that fix regressions in perl\*(Aqs behavior relative to previous
314 releases, no matter how old the regression, since some people may
315 upgrade from very old versions of perl to the latest version.
316 .IP \(bu 4
317 Patches that fix bugs in features that were new in the corresponding 5.x.0
318 stable release.
319 .IP \(bu 4
320 Patches that fix anything which prevents or seriously impacts the build
321 or installation of perl.
322 .IP \(bu 4
323 Portability fixes, such as changes to Configure and the files in
324 the hints/ folder.
325 .IP \(bu 4
326 Minimal patches that fix platform\-specific test failures.
327 .IP \(bu 4
328 Documentation updates that correct factual errors, explain significant
329 bugs or deficiencies in the current implementation, or fix broken markup.
330 .IP \(bu 4
331 Updates to dual\-life modules should consist of minimal patches to
332 fix crashing bugs or security issues (as above). Any changes made to
333 dual\-life modules for which CPAN is canonical should be coordinated with
334 the upstream author.
335 .PP
336 The following types of change are NOT acceptable:
337 .IP \(bu 4
338 Patches that break binary compatibility. (Please talk to the steering
339 council.)
340 .IP \(bu 4
341 Patches that add or remove features.
342 .IP \(bu 4
343 Patches that add new warnings or errors or deprecate features.
344 .IP \(bu 4
345 Ports of Perl to a new platform, architecture or OS release that
346 involve changes to the implementation.
347 .IP \(bu 4
348 New versions of dual\-life modules should NOT be imported into maint.
349 Those belong in the next stable series.
350 .PP
351 If there is any question about whether a given patch might merit
352 inclusion in a maint release, then it almost certainly should not
353 be included.
354 .SS "Getting changes into a maint branch"
355 .IX Subsection "Getting changes into a maint branch"
356 Historically, only the single\-person project manager cherry\-picked
357 changes from bleadperl into maintperl. This has scaling problems. At
358 the same time, maintenance branches of stable versions of Perl need to
359 be treated with great care. To that end, as of Perl 5.12, we have a new
360 process for maint branches.
361 .PP
362 Any committer may cherry\-pick any commit from blead to a maint branch by
363 first adding an entry to the relevant voting file in the maint\-votes branch
364 announcing the commit as a candidate for back\-porting, and then waiting for
365 at least two other committers to add their votes in support of this (i.e. a
366 total of at least three votes is required before a commit may be back\-ported).
367 .PP
368 Most of the work involved in both rounding up a suitable set of candidate
369 commits and cherry\-picking those for which three votes have been cast will
370 be done by the maint branch release manager, but anyone else is free to add
371 other proposals if they\*(Aqre keen to ensure certain fixes don\*(Aqt get overlooked
372 or fear they already have been.
373 .PP
374 Other voting mechanisms may also be used instead (e.g. sending mail to
375 perl5\-porters and at least two other committers responding to the list
376 giving their assent), as long as the same number of votes is gathered in a
377 transparent manner. Specifically, proposals of which changes to cherry\-pick
378 must be visible to everyone on perl5\-porters so that the views of everyone
379 interested may be heard.
380 .PP
381 It is not necessary for voting to be held on cherry\-picking perldelta
382 entries associated with changes that have already been cherry\-picked, nor
383 for the maint\-release manager to obtain votes on changes required by the
384 \&\fIPorting/release_managers_guide.pod\fR where such changes can be applied by
385 the means of cherry\-picking from blead.
386 .SH "CONTRIBUTED MODULES"
387 .IX Header "CONTRIBUTED MODULES"
388 .SS "A Social Contract about Artistic Control"
389 .IX Subsection "A Social Contract about Artistic Control"
390 What follows is a statement about artistic control, defined as the ability
391 of authors of packages to guide the future of their code and maintain
392 control over their work. It is a recognition that authors should have
393 control over their work, and that it is a responsibility of the rest of
394 the Perl community to ensure that they retain this control. It is an
395 attempt to document the standards to which we, as Perl developers, intend
396 to hold ourselves. It is an attempt to write down rough guidelines about
397 the respect we owe each other as Perl developers.
398 .PP
399 This statement is not a legal contract. This statement is not a legal
400 document in any way, shape, or form. Perl is distributed under the GNU
401 Public License and under the Artistic License; those are the precise legal
402 terms. This statement isn\*(Aqt about the law or licenses. It\*(Aqs about
403 community, mutual respect, trust, and good\-faith cooperation.
404 .PP
405 We recognize that the Perl core, defined as the software distributed with
406 the heart of Perl itself, is a joint project on the part of all of us.
407 From time to time, a script, module, or set of modules (hereafter referred
408 to simply as a "module") will prove so widely useful and/or so integral to
409 the correct functioning of Perl itself that it should be distributed with
410 the Perl core. This should never be done without the author\*(Aqs explicit
411 consent, and a clear recognition on all parts that this means the module
412 is being distributed under the same terms as Perl itself. A module author
413 should realize that inclusion of a module into the Perl core will
414 necessarily mean some loss of control over it, since changes may
415 occasionally have to be made on short notice or for consistency with the
416 rest of Perl.
417 .PP
418 Once a module has been included in the Perl core, however, everyone
419 involved in maintaining Perl should be aware that the module is still the
420 property of the original author unless the original author explicitly
421 gives up their ownership of it. In particular:
422 .IP \(bu 4
423 The version of the module in the Perl core should still be considered the
424 work of the original author. All patches, bug reports, and so
425 forth should be fed back to them. Their development directions
426 should be respected whenever possible.
427 .IP \(bu 4
428 Patches may be applied by the steering council without the explicit
429 cooperation of the module author if and only if they are very minor,
430 time\-critical in some fashion (such as urgent security fixes), or if
431 the module author cannot be reached. Those patches must still be
432 given back to the author when possible, and if the author decides on
433 an alternate fix in their version, that fix should be strongly
434 preferred unless there is a serious problem with it. Any changes not
435 endorsed by the author should be marked as such, and the contributor
436 of the change acknowledged.
437 .IP \(bu 4
438 The version of the module distributed with Perl should, whenever
439 possible, be the latest version of the module as distributed by the
440 author (the latest non\-beta version in the case of public Perl
441 releases), although the steering council may hold off on upgrading the
442 version of the module distributed with Perl to the latest version
443 until the latest version has had sufficient testing.
444 .PP
445 In other words, the author of a module should be considered to have final
446 say on modifications to their module whenever possible (bearing in mind
447 that it\*(Aqs expected that everyone involved will work together and arrive at
448 reasonable compromises when there are disagreements).
449 .PP
450 As a last resort, however:
451 .PP
452 If the author\*(Aqs vision of the future of their module is sufficiently
453 different from the vision of the steering council and perl5\-porters as a
454 whole so as to cause serious problems for Perl, the steering council may
455 choose to formally fork the version of the module in the Perl core from the
456 one maintained by the author. This should not be done lightly and
457 should \fBalways\fR if at all possible be done only after direct input
458 from Larry. If this is done, it must then be made explicit in the
459 module as distributed with the Perl core that it is a forked version and
460 that while it is based on the original author\*(Aqs work, it is no longer
461 maintained by them. This must be noted in both the documentation and
462 in the comments in the source of the module.
463 .PP
464 Again, this should be a last resort only. Ideally, this should never
465 happen, and every possible effort at cooperation and compromise should be
466 made before doing this. If it does prove necessary to fork a module for
467 the overall health of Perl, proper credit must be given to the original
468 author in perpetuity and the decision should be constantly re\-evaluated to
469 see if a remerging of the two branches is possible down the road.
470 .PP
471 In all dealings with contributed modules, everyone maintaining Perl should
472 keep in mind that the code belongs to the original author, that they may
473 not be on perl5\-porters at any given time, and that a patch is not
474 official unless it has been integrated into the author\*(Aqs copy of the
475 module. To aid with this, and with points #1, #2, and #3 above, contact
476 information for the authors of all contributed modules should be kept with
477 the Perl distribution.
478 .PP
479 Finally, the Perl community as a whole recognizes that respect for
480 ownership of code, respect for artistic control, proper credit, and active
481 effort to prevent unintentional code skew or communication gaps is vital
482 to the health of the community and Perl itself. Members of a community
483 should not normally have to resort to rules and laws to deal with each
484 other, and this document, although it contains rules so as to be clear, is
485 about an attitude and general approach. The first step in any dispute
486 should be open communication, respect for opposing views, and an attempt
487 at a compromise. In nearly every circumstance nothing more will be
488 necessary, and certainly no more drastic measure should be used until
489 every avenue of communication and discussion has failed.
490 .SH DOCUMENTATION
491 .IX Header "DOCUMENTATION"
492 Perl\*(Aqs documentation is an important resource for our users. It\*(Aqs
493 incredibly important for Perl\*(Aqs documentation to be reasonably coherent
494 and to accurately reflect the current implementation.
495 .PP
496 Just as P5P collectively maintains the codebase, we collectively
497 maintain the documentation. Writing a particular bit of documentation
498 doesn\*(Aqt give an author control of the future of that documentation.
499 At the same time, just as source code changes should match the style
500 of their surrounding blocks, so should documentation changes.
501 .PP
502 Examples in documentation should be illustrative of the concept
503 they\*(Aqre explaining. Sometimes, the best way to show how a
504 language feature works is with a small program the reader can
505 run without modification. More often, examples will consist
506 of a snippet of code containing only the "important" bits.
507 The definition of "important" varies from snippet to snippet.
508 Sometimes it\*(Aqs important to declare \f(CW\*(C`use strict\*(C'\fR and \f(CW\*(C`use warnings\*(C'\fR,
509 initialize all variables and fully catch every error condition.
510 More often than not, though, those things obscure the lesson
511 the example was intended to teach.
512 .PP
513 As Perl is developed by a global team of volunteers, our
514 documentation often contains spellings which look funny
515 to \fIsomebody\fR. Choice of American/British/Other spellings
516 is left as an exercise for the author of each bit of
517 documentation. When patching documentation, try to emulate
518 the documentation around you, rather than changing the existing
519 prose.
520 .PP
521 In general, documentation should describe what Perl does "now" rather
522 than what it used to do. It\*(Aqs perfectly reasonable to include notes
523 in documentation about how behaviour has changed from previous releases,
524 but, with very few exceptions, documentation isn\*(Aqt "dual\-life" \-\-
525 it doesn\*(Aqt need to fully describe how all old versions used to work.
526 .SH "STANDARDS OF CONDUCT"
527 .IX Header "STANDARDS OF CONDUCT"
528 The official forum for the development of perl is the perl5\-porters mailing
529 list, mentioned above, and its bugtracker at GitHub. Posting to the
530 list and the bugtracker is not a right: all participants in discussion are
531 expected to adhere to a standard of conduct.
532 .IP \(bu 4
533 Always be civil.
534 .IP \(bu 4
535 Heed the moderators.
536 .PP
537 Civility is simple: stick to the facts while avoiding demeaning remarks,
538 belittling other individuals, sarcasm, or a presumption of bad faith. It is
539 not enough to be factual. You must also be civil. Responding in kind to
540 incivility is not acceptable. If you relay otherwise\-unposted comments to
541 the list from a third party, you take responsibility for the content of
542 those comments, and you must therefore ensure that they are civil.
543 .PP
544 While civility is required, kindness is encouraged; if you have any doubt about
545 whether you are being civil, simply ask yourself, "Am I being kind?" and aspire
546 to that.
547 .PP
548 If the list moderators tell you that you are not being civil, carefully
549 consider how your words have appeared before responding in any way. Were they
550 kind? You may protest, but repeated protest in the face of a repeatedly
551 reaffirmed decision is not acceptable. Repeatedly protesting about the
552 moderators\*(Aq decisions regarding a third party is also unacceptable, as is
553 continuing to initiate off\-list contact with the moderators about their
554 decisions.
555 .PP
556 Unacceptable behavior will result in a public and clearly identified
557 warning. A second instance of unacceptable behavior from the same
558 individual will result in removal from the mailing list and GitHub issue
559 tracker, for a period of one calendar month. The rationale for this is to
560 provide an opportunity for the person to change the way they act.
561 .PP
562 After the time\-limited ban has been lifted, a third instance of
563 unacceptable behavior will result in a further public warning. A fourth
564 or subsequent instance will result in an indefinite ban. The rationale
565 is that, in the face of an apparent refusal to change behavior, we must
566 protect other community members from future unacceptable actions. The
567 moderators may choose to lift an indefinite ban if the person in
568 question affirms they will not transgress again.
569 .PP
570 Removals, like warnings, are public.
571 .PP
572 The list of moderators will be public knowledge. At present, it is:
573 Karen Etheridge, Neil Bowers, Nicholas Clark, Ricardo Signes, Todd Rinaldo.
574 .SH CREDITS
575 .IX Header "CREDITS"
576 "Social Contract about Contributed Modules" originally by Russ Allbery <[email protected]> and the perl5\-porters.