Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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 .xsp ot .tt pages that requires no pl file; but they're examples non the less.

      Yes, I'm biased [cpan.org], and that .pl file is going away now that I'm using DBIC. :-)
    • And "samples".
  • Cool!

    Some ideas:

    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.