On Sun, 24 Jan 2021 12:42:54 +0100, Sawyer X <xsawyerx@gmail.com> wrote:
>
> On 1/20/21 11:34 PM, Eric Herman wrote:
>> On 1/20/21 4:25 AM, Joel Roth wrote:
>>>> On 1/19/21 11:44 PM, Paul "LeoNerd" Evans wrote:
>>>
>>>>> To emphasise again: in 41 days time the bug tracker used by nearly 80%
>>>>> of all of CPAN is going to be shut down and become unavailable for
>>>>> either historic or newly-reported bugs. We *need* to find a
>>>>> solution in
>>>>> that time.
>>>
>>> On Wed, Jan 20, 2021 at 12:27:47AM +0100, Sawyer X wrote:
>>>> This is infrastructure maintained by NOC volunteers. What would you
>>>> suggest
>>>> Perl 5 Porters do?
>>>
>>> Can we estimate what the cost would be to *hire* someone
>>> to administer the existing system?
>>>
>>> Perhaps donations could support this resource until we have
>>> a smooth path forward? I, for one, would contribute.
>>>
>>> Can the Perl Foundation receive funds for this purpose?
>>> I think many in the community would pony up to help.
>>
>>
>> Indeed. If there is a straight-forward solution which involves putting
>> in a reasonably amount of money, it's not a problem, it's an expense.
>> I, too, will donate.
>
>
> This assumes on a major benefit to this expenditure. I personally doubt
> the benefit outweighs the cost.
Requests for data on this have been made multiple times by various people and outright rejected.
I cite:
rjbs:
>>>>>> The question of rt.cpan.org's continued operation is an ongoing one.
rob:
>>>>> Depends who you ask.
ether:
>>>> Could you elaborate on this point please?
rob:
>>> I'd really rather not. The analysis of the data from the volunteers running it is that it is (past) time to turn it down. If someone else is going to step up and run an equivalent service, they're welcome to. There's not really a discussion to have.
ether:
>> No, I'm sorry, we *do* need to have this conversation, so we can identify what resources and/or volunteers we need to find should we want to keep the service running.
>>If *you* don't want to be involved in running the service, that's fine, but you cannot prevent anyone else from doing so, or even knowing what would be involved so they can decide if they want to.
>>Thousands of widely-used perl modules still use rt.cpan.org as their issue tracker, and turning off this service in less than three months will have a huge impact on the ecosystem and also the optics of Perl's viability, so I want to get a good understanding of what the issues are and what the tradeoffs would be of the various paths forward.
>>Could you please share your analysis?
rob:
> *never responded*
--
With regards,
Christian Walde
>
> On 1/20/21 11:34 PM, Eric Herman wrote:
>> On 1/20/21 4:25 AM, Joel Roth wrote:
>>>> On 1/19/21 11:44 PM, Paul "LeoNerd" Evans wrote:
>>>
>>>>> To emphasise again: in 41 days time the bug tracker used by nearly 80%
>>>>> of all of CPAN is going to be shut down and become unavailable for
>>>>> either historic or newly-reported bugs. We *need* to find a
>>>>> solution in
>>>>> that time.
>>>
>>> On Wed, Jan 20, 2021 at 12:27:47AM +0100, Sawyer X wrote:
>>>> This is infrastructure maintained by NOC volunteers. What would you
>>>> suggest
>>>> Perl 5 Porters do?
>>>
>>> Can we estimate what the cost would be to *hire* someone
>>> to administer the existing system?
>>>
>>> Perhaps donations could support this resource until we have
>>> a smooth path forward? I, for one, would contribute.
>>>
>>> Can the Perl Foundation receive funds for this purpose?
>>> I think many in the community would pony up to help.
>>
>>
>> Indeed. If there is a straight-forward solution which involves putting
>> in a reasonably amount of money, it's not a problem, it's an expense.
>> I, too, will donate.
>
>
> This assumes on a major benefit to this expenditure. I personally doubt
> the benefit outweighs the cost.
Requests for data on this have been made multiple times by various people and outright rejected.
I cite:
rjbs:
>>>>>> The question of rt.cpan.org's continued operation is an ongoing one.
rob:
>>>>> Depends who you ask.
ether:
>>>> Could you elaborate on this point please?
rob:
>>> I'd really rather not. The analysis of the data from the volunteers running it is that it is (past) time to turn it down. If someone else is going to step up and run an equivalent service, they're welcome to. There's not really a discussion to have.
ether:
>> No, I'm sorry, we *do* need to have this conversation, so we can identify what resources and/or volunteers we need to find should we want to keep the service running.
>>If *you* don't want to be involved in running the service, that's fine, but you cannot prevent anyone else from doing so, or even knowing what would be involved so they can decide if they want to.
>>Thousands of widely-used perl modules still use rt.cpan.org as their issue tracker, and turning off this service in less than three months will have a huge impact on the ecosystem and also the optics of Perl's viability, so I want to get a good understanding of what the issues are and what the tradeoffs would be of the various paths forward.
>>Could you please share your analysis?
rob:
> *never responded*
--
With regards,
Christian Walde