My job is editor, not programmer. Also novelist -- but again, not programmer. Certainly not CPAN programmer.

Paying attention is not my job. Releasing software I've written under a free and open license does not instill in me the obligation to jump whenever a user snaps his or her fingers.

I may do so because I take the quality and utility of my software seriously, but do not mistake that for anything which may instill in you any sort of entitlement. That is an excellent way not to get what you want from me.

Then CPAN Testers reports should come with login instructions so that I can resurrect decade-old skills and perform system administration to fix broken installations and configurations -- oh, and as you say, a truly *modern* reporting system should publish these logins and passwords publicly in syndication feeds.

However, by what possible logic can you conclude that the appropriate way to get that bug fixed is to report it to people who, given all of the information detected automatically, *do not* maintain CPAN.pm?

"Oh," perhaps you think, "it's easy for them to read the reports and diagnose the problem remotely on machines they have never seen before, did not configure, and cannot probe -- and it's so easy for them to file a bug in the right place!" If you don't think that, precisely what *do* you think to produce such a bold assertion that it is Shlomi's job to install and reconfigure a new version of CPAN.pm for a CPAN Tester -- or for that matter, everyone with a misconfigured version of CPAN.pm which contains this bug?

It's not my "job" to fix bugs in *my own* distributions. I do it because I care about quality and, contrary to what appears to be near- universal belief around here, I care that people can use my code.