Non code parts of Perl including the perlfaq and some of the Perl community infrastructure are available on github here for people wanting to do drive by fixes:
Probably this should be more widely known. Unfortunately I think some of these repos are old forked copies? For example the PAUSE and YAPC repos. I'm not sure why that is. Its not clearly documented how it all works exactly.
He's talking about migration of Perl's ticket system (RT) to GitHub Issues.
Fortunately, he did not say RT is overkill for 90% of projects using it; that would not be correct. Projects using RT tend to be using it because it's not overkill for them, they need it.
In fact, I agree with his opinion that RT is likely overkill for 90% of projects.
My point is that Perl is not among the 90% that RT would be overkill for.
His overall comment's conclusion is mistaken, because for Perl, moving from RT to GitHub issues would be "a downgrade". GitHub Issues are not "just right" for a complex project like Perl that actively uses the metadata capabilities of a ticket tracking system like RT.
https://github.com/perl-doc-cats
Probably this should be more widely known. Unfortunately I think some of these repos are old forked copies? For example the PAUSE and YAPC repos. I'm not sure why that is. Its not clearly documented how it all works exactly.