Front page | perl.perl5.porters |
Postings from March 2021
Re: [DISCUSS] The future of mod_perl
From: B. Estrade
March 22, 2021 22:56
Re: [DISCUSS] The future of mod_perl
Message ID: firstname.lastname@example.org
On 3/22/21 4:32 PM, Todd Rinaldo wrote:
> I don't really feel like this is commentary on Perl at all. For me, this
> is a commentary on mod_perl which most people now have better tools to
> run perl in a web server. I tip my hat to mod_perl. It did an amazing
> job for its time. I we should thank all the people who kept it going and
> then focus our time on the Perl frameworks that we love and actively use.
You can't separate mod_perl from any talk about Apache. It is to Apache
httpd, what Dancer2 or Mojo are to PSGI (or, starman, in the flesh). So
it's probably more an indication of an existential crisis of Apache
httpd's than anything else. Idk, seems like this is just about mod_perl
and not mod_perl2?
> Put another way: Would we be discussing having TPF revive Maypole if
> someone declared the project to be dead? For me the answer would be no
> because there are other active projects in the space that do a similar job.
ASF also has this "Attic" thing for dead projects, but there are
bureaucratic rules regarding its placement there.
So there are *usable* procedures for putting, preventing, and also
moving out a project from the Attic. Anyone interested in preserving
mod_perl should consult it and contact the folks on the mailing list
that seem to be willing to help keep it up.
Coupled with the apparent interest there and here, seems like a
semi-organized effort can avoid banishment to the Attic - or at least
break it out if unsuccessful.
>> On Mar 19, 2021, at 1:53 PM, Dean Hamstead <email@example.com
>> <mailto:firstname.lastname@example.org>> wrote:
>> There has been some discussion about this in #marketing on TPF slack.
>> Some points i would like to share, pasted and tweaked.
>> - In my view is that mod_perl is still a key part of the ecosystem and
>> if it becomes unmaintained it will be the signal to decision makers to
>> retire whatever perl code is still in use, especially non strategic code.
>> - Whilst using it for your application is out of vogue, mod_perl
>> exposes all sorts of the internals of apache to perl, its still great
>> for custom logging, custom aaa, even custom protocols if youre inclined.
>> - We don't seem to have good signal as to how widely mod_perl is used
>> and for what. Debian's popcon may give us some indication, but given
>> CentOS is the most popular OS for perl it's indicative only. This is
>> something the marketing committee should tackle but i mention it here
>> as part of a wider problem of low signal
>> - To me it seems like a good opportunity for TPF to take on a key
>> project and start to develop the model of supporting more than one
>> perl related initiative. Either by taking it from apache or by working
>> with apache to fundraise and put human resources on to it
>> On 2021-03-19 07:55, Ricardo Signes wrote:
>>> On Wed, Mar 17, 2021, at 6:14 PM, James E Keenan wrote:
>>> The Perl 5 Porters are responsible for maintaining and advancing the
>>> Perl 5 core distribution. mod_perl does not ship with the core
>>> distribution. It's maintained upstream on CPAN. It's README is
>>> here: https://metacpan.org/source/SHAY/mod_perl-2.0.11/README
>>> ...nonetheless, p5p is a good bet for a place that could contain many
>>> people who are both interested and capable of helping take over
>>> maintainership of mod_perl, which has long been an important vehicle
>>> for getting perl code deployed. Although I don't want perl5-porters
>>> to be general-perl-announce, this seems like a good exception.