In perl.git, the branch blead has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/17c80487b48847f88d152c5ea537f4fd68291fb3?hp=4594cf53ef3c9cfccc60be21374c2dec84f891ef>
- Log -----------------------------------------------------------------
commit 17c80487b48847f88d152c5ea537f4fd68291fb3
Author: Ricardo Signes <r...@cpan.org>
Date: Mon Jul 7 13:58:26 2014 -0400
add the standards of conduct to perlpolicy
-----------------------------------------------------------------------
Summary of changes:
pod/perlpolicy.pod | 43 +++++++++++++++++++++++++++++++++++++++----
1 file changed, 39 insertions(+), 4 deletions(-)
diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 8120cd8..988d95d 100644
--- a/pod/perlpolicy.pod
+++ b/pod/perlpolicy.pod
@@ -260,7 +260,7 @@ acceptable.
=item *
Acceptable documentation updates are those that correct factual errors,
-explain significant bugs or deficiencies in the current implementation,
+explain significant bugs or deficiencies in the current implementation,
or fix broken markup.
=item *
@@ -271,7 +271,7 @@ are not acceptable.
=item *
Patches that fix crashing bugs that do not otherwise change Perl's
-functionality or negatively impact performance are acceptable.
+functionality or negatively impact performance are acceptable.
=item *
@@ -286,7 +286,7 @@ releases are acceptable.
=item *
-Updates to dual-life modules should consist of minimal patches to
+Updates to dual-life modules should consist of minimal patches to
fix crashing or security issues (as above).
=item *
@@ -323,7 +323,7 @@ maint branches.
Any committer may cherry-pick any commit from blead to a maint branch if
they send mail to perl5-porters announcing their intent to cherry-pick
-a specific commit along with a rationale for doing so and at least two
+a specific commit along with a rationale for doing so and at least two
other committers respond to the list giving their assent. (This policy
applies to current and former pumpkings, as well as other committers.)
@@ -482,6 +482,41 @@ in documentation about how behaviour has changed from
previous releases,
but, with very few exceptions, documentation isn't "dual-life" --
it doesn't need to fully describe how all old versions used to work.
+=head1 STANDARDS OF CONDUCT
+
+The official forum for the development of perl is the perl5-porters mailing
+list, mentioned above, and its bugtracker at rt.perl.org. All participants in
+discussion there are expected to adhere to a standard of conduct.
+
+=over 4
+
+=item *
+
+Always be civil.
+
+=item *
+
+Heed the moderators.
+
+=back
+
+Civility is simple: stick to the facts while avoiding demeaning remarks and
+sarcasm. It is not enough to be factual. You must also be civil. Responding
+in kind to incivility is not acceptable.
+
+If the list moderators tell you that you are not being civil, carefully
+consider how your words have appeared before responding in any way. You may
+protest, but repeated protest in the face of a repeatedly reaffirmed decision
+is not acceptable.
+
+Unacceptable behavior will result in a public and clearly identified warning.
+Repeated unacceptable behavior will result in removal from the mailing list.
+The first removal is for one month. Subsequent removals will double in length.
+After six months with no warning, a user's ban length is reset. Removals, like
+warnings, are public.
+
+The list of moderators will be public knowledge. At present, it is: Ricardo
+Signes.
=head1 CREDITS
--
Perl5 Master Repository
