In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/107813b01928a8dad7ac6980549e277a9d99f8cd?hp=4dc304e02d3569a2fbb0907ff3c68656236a547e>
- Log ----------------------------------------------------------------- commit 107813b01928a8dad7ac6980549e277a9d99f8cd Merge: a101a77 4dc304e Author: Jesse Vincent <je...@bestpractical.com> Date: Tue Aug 16 10:53:53 2011 +0300 Merge branch 'blead' of ssh://perl5.git.perl.org/perl into blead * 'blead' of ssh://perl5.git.perl.org/perl: [perl #97076] Fix mad+threads bareword strict exemption perldelta update Two AUTHORS fixes Remove OPpENTERSUB_NOMOD from B::Concise Remove OPpENTERSUB_NOMOD. Propagate lvalue context only to children of list ops which are not in void context. Fix tabbing and trailing whitespace from commit f1d35e3443 and bump IO::Socket version. Use the exception set in select (connect()) to early return when remote end is busy or in non existing port generic perldelta entry for prototype changes &CORE::not and &CORE::getprotobynumber Give not and getprotobynumber listop prototypes Document and test $; prototype syntax Move checking of CV to GV assigned (OPpASSIGN_CV_TO_GV) from the peephole optimizer to scalarvoid commit a101a7707032ceb93f21246e0d9644ed65b44b17 Author: Jesse Vincent <je...@bestpractical.com> Date: Tue Aug 16 10:46:33 2011 +0300 Restore (and slightly update) documentation about The Rules and the structure of Perl 5 governance removed during the major refactoring of perlhack.pod in 04c692a854b61dfae1266e29468ce4fb51c80512. M pod/perlpolicy.pod commit 25f3a13c1eee8f4e7f933ca19d6eab5a3617424b Author: Jesse Vincent <je...@bestpractical.com> Date: Tue Aug 16 10:46:12 2011 +0300 Add another explicit synonym for the porters. M pod/perlhack.pod ----------------------------------------------------------------------- Summary of changes: pod/perlhack.pod | 2 +- pod/perlpolicy.pod | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 52 insertions(+), 1 deletions(-) diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 1bf2b88..60e2b31 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -95,7 +95,7 @@ please add it. This will help the porters fix the bug. The perl5-porters (p5p) mailing list is where the Perl standard distribution is maintained and developed. The people who maintain Perl -are also referred to as the "Perl 5 Porters", or just the "porters". +are also referred to as the "Perl 5 Porters", "p5p" or just the "porters". A searchable archive of the list is available at L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/>. There is diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod index 2341414..7dd4ad2 100644 --- a/pod/perlpolicy.pod +++ b/pod/perlpolicy.pod @@ -8,6 +8,57 @@ This document is the master document which records all written policies about how the Perl 5 Porters collectively develop and maintain the Perl core. +=head1 GOVERNANCE + +=head2 Perl 5 Porters + +Subscribers to perl5-porters (the porters themselves) come in several flavours. +Some are quiet curious lurkers, who rarely pitch in and instead watch +the ongoing development to ensure they're forewarned of new changes or +features in Perl. Some are representatives of vendors, who are there +to make sure that Perl continues to compile and work on their +platforms. Some patch any reported bug that they know how to fix, +some are actively patching their pet area (threads, Win32, the regexp +-engine), while others seem to do nothing but complain. In other +words, it's your usual mix of technical people. + +Over this group of porters presides Larry Wall. He has the final word +in what does and does not change in any of the Perl programming languages. +These days, Larry spends most of his time on Perl 6, while Perl 5 is +shepherded by a "pumpking", a porter responsible for deciding what +goes into each release and ensuring that releases happen on a regular +basis. + +Larry sees Perl development along the lines of the US government: +there's the Legislature (the porters), the Executive branch (the +-pumpking), and the Supreme Court (Larry). The legislature can +discuss and submit patches to the executive branch all they like, but +the executive branch is free to veto them. Rarely, the Supreme Court +will side with the executive branch over the legislature, or the +legislature over the executive branch. Mostly, however, the +legislature and the executive branch are supposed to get along and +work out their differences without impeachment or court cases. + +You might sometimes see reference to Rule 1 and Rule 2. Larry's power +as Supreme Court is expressed in The Rules: + +=over 4 + +=item 1 + +Larry is always by definition right about how Perl should behave. +This means he has final veto power on the core functionality. + +=item 2 + +Larry is allowed to change his mind about any matter at a later date, +regardless of whether he previously invoked Rule 1. + +=back + +Got that? Larry is always right, even when he was wrong. It's rare +to see either Rule exercised, but they are often alluded to. + =head1 MAINTENANCE AND SUPPORT Perl 5 is developed by a community, not a corporate entity. Every change -- Perl5 Master Repository