During YAPC::Europe in Birmingham I did a (rather short and un-hackish) hackathon. Slides are available here.
I added a few new metrics:
This resulted in quite some movement in the CPANTS game...
I've also changed the display of the author pages, optional metrics (is_prereq and has_example) are now visually seperated from the core metrics.
The site http://cpants.perl.org is still not very stable due to a Catalyst/DBIx::Class-Bug (or more likely a bug in my usage of them).
Oh, and if you want to join the fun and help a bit, here's a (probably incomplete) list of tasks:
But you should also add 'demo' and 'demos' to the list of examples directories.
For that matter, I'm not so sure about the 'at least one *.pl requirement'. It may very well be a non-perl demo, aka site code like
Yes, I'm biased [cpan.org], and that
1) Document/discuss possible future metrics on the Perl-QA wiki [yi.org]
2) For each metric, document the aspect of Quality that is being judged and how the Kwalitee metric is a good proxy for it, and/or possible other proxies. For example, consider the software goal of "Good documentation". Currently that metric follows the following chain of proxy metrics:
Good documentation => 100% POD coverage => has t/.*pod.*coverage.* file
A better proxy might be for CPANTS to run Pod::Cover
consistent_newlines - proposed by Adam Kennedy on Perl-QA in April
Was that consistent newlines per file, or per dist? Some dists have legit reason to have some files native line endings and some files w/ non-0native line endings. I've done it in Handel. Some things just don't work in windows unless the file has *nix line endings, like __DATA__ vs. __END__ in some situations.
Per file. That's important to prevent Module::Signature breakage.