one guy was feeling down, because his dist had had an outstanding PR since Sept last year, so not expecting his PR to be done. Now his PR has been merged along with the previous one, and a release done. Result!

I’ve got data for the number of RT bugs outstanding, every day for the last couple of years. It’s basically a slowly increasing line. I’m *really* hoping we might see a noticeable drop as the result of PRC fixes.

reneeb: once I’ve tuned (ok, finished) the scoring of dists, I’ll publish a page with the scoring for all dists, so people can bitch about which ones are “wrong”, and then we tune the list together. Hopefully over time we’ll get the PR crew focussed on more “more valuable” dists. But breadth first isn’t bad either. Every dist has things that can be done.

reneeb: I'm thinking.. imagine I sit down with 5 others for a month and put in real effort into let's say improve documentation for an important module. another team works on bug fixes and so on.. next month you go for refactoring..

dolmen: I did briefly wonder whether it should include non-CPAN perl github repos, but decided that would make things more complicated, and there’s plenty to do with CPAN. Why not put it on CPAN: App-github-keygen?