This isn't directly core's doing, nor problem, but I am attempting to raise awareness of the situation because it seems nobody is aware or talking about it. **** rt.cpan.org, the bugtracker used by nearly 80% of all CPAN modules [1], is going to be shut down on 1st March this year [2]; 41 days from when I write this email. **** I am rather concerned about this, as there doesn't appear to be any sort of co-ordinated bailout plan or migration of the *huge amount* of CPAN modules this is about to affect. I am furthermore concerned at the total lack of discussion or response that has so far been generated; aside from Karen Etheridge I haven't seen any noise of upset being generated at all. Nor am I aware of any sort of effort to handle what will become a huge outage of a major component of the CPAN ecosystem. I personally have 189 modules in need of migration - somehow. As yet I have no clue what I am going to do about it. Existing bugs need to be moved somewhere else (and I have no clue how I'm going to fix up URLs that currently point to those, in code comments, documentation, blog posts, ... anywhere else), and a new for users to report new bugs needs to exist. Of special note are the numerous "in progress" tickets I have across my distributions, containing ongoing discussions about design issues and the like. To say that I am "concerned" is an understatement; I am fairly close to panicing about this. I am quite sure I am but the smallest tip of the iceberg here. Every time I mention it on Freenode's #perl or irc.perl.org's #p5p there are always new folks who were totally unaware of this fact. This is going to hit lots of people in a very hard surprise. I am therefore interested to know if a) Perl5 Porters officially, and b) Individual CPAN authors who happen to subscribe to the perl5-porters mailing list have any sort of response to this; any kind of mass-migration plan or thoughts on continuing the service. 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. 1: Add the "known to be RT" and "unknown" categories of https://cpan.rocks/; because metacpan.org defaults to RT in the latter case. 2: https://log.perl.org/2020/12/rtcpanorg-sunset.html -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/Thread Next