Mailing List Archive

On Mar 17, 2021, at 3:40 PM, Sander Striker <striker@apache.org> wrote:
> If you are interested in seeing mod_perl remain an active project, and are able to help maintain and provide oversight, please respond in this thread indicating that you are interested in performing the duties of a PMC member[2].

I am, but I'm not currently a committer, fwiw.

https://github.com/esabol

Regards,
Ed


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

All,

I would certainly hate to see mod_perl no longer being maintained. I use
it as a front-end for a library cataloging system that is very much
alive, in-use and updated with recent HTML, CSS and JavaScript features.
Rewriting this front-end in some other language would be a huge
undertaking and would not provide much benefit because Apache + Perl +
mod_perl not only do the job but do it extremely well.

While I don't understand what type of time commitment would be required,
I would be happy to add my name to the bottom of any list should others
have a strong desire to hold such a position.

Best,

Geoff Mottram

On 3/17/2021 3:40 PM, Sander Striker wrote:
> Dear community members,
>
> As projects mature, they will naturally reach a point where activity
> reduces to a level such that the project is no longer sustainable.  At
> Apache, projects reach this stage when there are not at least 3 active
> PMC members providing oversight. Projects that reach this stage are
> usually placed in the Attic [1] or absorbed by another Apache project
> willing to manage its releases.
>
> If you are interested in seeing mod_perl remain an active project, and
> are able to help maintain and provide oversight, please respond in this
> thread indicating that you are interested in performing the duties of a
> PMC member[2].
>
> Cheers,
>
> Sander Striker
> Director, The Apache Software Foundation
>
> [1] https://attic.apache.org/ <https://attic.apache.org/>
> [2] https://www.apache.org/dev/pmc.html
> <https://www.apache.org/dev/pmc.html>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

On Wed, 17 Mar 2021 at 19:40, Sander Striker <striker@apache.org> wrote:
>
> Dear community members,
>
> As projects mature, they will naturally reach a point where activity reduces to a level such that the project is no longer sustainable. At Apache, projects reach this stage when there are not at least 3 active PMC members providing oversight. Projects that reach this stage are usually placed in the Attic [1] or absorbed by another Apache project willing to manage its releases.
>
> If you are interested in seeing mod_perl remain an active project, and are able to help maintain and provide oversight, please respond in this thread indicating that you are interested in performing the duties of a PMC member[2].
>

I confirm again that I am still here and willing to participate and
sustain oversight of mod_perl as required.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

The projects current state is that no new development happening. This
isn't to say that new development shouldn't happen, but it isn't. Apache
and Perl both continue to move forward, and we are pretty lucky that the
design that Stas, Phillipe, Geoff, etc built mod_perl 2 under is
resilient enough to continue to despite the changes that both of these
projects have made.

So, if the goal of the PMC is to maintain the status quo, then there is
essentially no time required, aside from someone needing to file a
report every few months saying that nothing has happened, and there were
no releases. Things can only remain that way as long as there are no
security problems that affect mod_perl, and neither Apache or Perl do
anything that really breaks mod_perl.

Adam

On 3/17/2021 6:10 PM, Geoff Mottram wrote:
> All,
>
> I would certainly hate to see mod_perl no longer being maintained. I use
> it as a front-end for a library cataloging system that is very much
> alive, in-use and updated with recent HTML, CSS and JavaScript features.
> Rewriting this front-end in some other language would be a huge
> undertaking and would not provide much benefit because Apache + Perl +
> mod_perl not only do the job but do it extremely well.
>
> While I don't understand what type of time commitment would be required,
> I would be happy to add my name to the bottom of any list should others
> have a strong desire to hold such a position.
>
> Best,
>
> Geoff Mottram
>
> On 3/17/2021 3:40 PM, Sander Striker wrote:
>> Dear community members,
>>
>> As projects mature, they will naturally reach a point where activity
>> reduces to a level such that the project is no longer sustainable.  At
>> Apache, projects reach this stage when there are not at least 3 active
>> PMC members providing oversight. Projects that reach this stage are
>> usually placed in the Attic [1] or absorbed by another Apache project
>> willing to manage its releases.
>>
>> If you are interested in seeing mod_perl remain an active project, and
>> are able to help maintain and provide oversight, please respond in
>> this thread indicating that you are interested in performing the
>> duties of a PMC member[2].
>>
>> Cheers,
>>
>> Sander Striker
>> Director, The Apache Software Foundation
>>
>> [1] https://attic.apache.org/ <https://attic.apache.org/>
>> [2] https://www.apache.org/dev/pmc.html
>> <https://www.apache.org/dev/pmc.html>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

The projects current state is that no new development happening. This
isn't to say that new development shouldn't happen, but it isn't. Apache
and Perl both continue to move forward, and we are pretty lucky that the
design that Stas, Phillipe, Geoff, etc built mod_perl 2 under is
resilient enough to continue to despite the changes that both of these
projects have made.

So, if the goal of the PMC is to maintain the status quo, then there is
essentially no time required, aside from someone needing to file a
report every few months saying that nothing has happened, and there were
no releases. Things can only remain that way as long as there are no
security problems that affect mod_perl, and neither Apache or Perl do
anything that really breaks mod_perl.

Adam

On 3/17/2021 6:10 PM, Geoff Mottram wrote:
> All,
>
> I would certainly hate to see mod_perl no longer being maintained. I use
> it as a front-end for a library cataloging system that is very much
> alive, in-use and updated with recent HTML, CSS and JavaScript features.
> Rewriting this front-end in some other language would be a huge
> undertaking and would not provide much benefit because Apache + Perl +
> mod_perl not only do the job but do it extremely well.
>
> While I don't understand what type of time commitment would be required,
> I would be happy to add my name to the bottom of any list should others
> have a strong desire to hold such a position.
>
> Best,
>
> Geoff Mottram
>
> On 3/17/2021 3:40 PM, Sander Striker wrote:
>> Dear community members,
>>
>> As projects mature, they will naturally reach a point where activity
>> reduces to a level such that the project is no longer sustainable.  At
>> Apache, projects reach this stage when there are not at least 3 active
>> PMC members providing oversight. Projects that reach this stage are
>> usually placed in the Attic [1] or absorbed by another Apache project
>> willing to manage its releases.
>>
>> If you are interested in seeing mod_perl remain an active project, and
>> are able to help maintain and provide oversight, please respond in
>> this thread indicating that you are interested in performing the
>> duties of a PMC member[2].
>>
>> Cheers,
>>
>> Sander Striker
>> Director, The Apache Software Foundation
>>
>> [1] https://attic.apache.org/ <https://attic.apache.org/>
>> [2] https://www.apache.org/dev/pmc.html
>> <https://www.apache.org/dev/pmc.html>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org

I am also still around and keeping an eye on things, maybe from afar a little, but still here and invested.

For myself, I find that one of the challenges in filing board reports is having to effectively report more or less nothing of value, on a schedule that’s just long and infrequent enough to keep overlooking it, basically.

Sent from the depths of my mind on an iPhone

> On Mar 17, 2021, at 15:40, Sander Striker <striker@apache.org> wrote:
>

> ?
> Dear community members,
>
> As projects mature, they will naturally reach a point where activity reduces to a level such that the project is no longer sustainable. At Apache, projects reach this stage when there are not at least 3 active PMC members providing oversight. Projects that reach this stage are usually placed in the Attic [1] or absorbed by another Apache project willing to manage its releases.
>
> If you are interested in seeing mod_perl remain an active project, and are able to help maintain and provide oversight, please respond in this thread indicating that you are interested in performing the duties of a PMC member[2].
>
> Cheers,
>
> Sander Striker
> Director, The Apache Software Foundation
>
> [1] https://attic.apache.org/
> [2] https://www.apache.org/dev/pmc.html
>