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.
  • First, I'm glad to see you doing this sort of thing. Automated CPAN analysis is good to have. I'd like to correct a few notes on the Phalanx 100, though. First, consider why the Phalanx 100 was created. The Phalanx project was an attempt to increase test coverage in the most-used modules on CPAN, so that Ponie would have a good test base to work with. The Phalanx 100 was created by analysis of CPAN download logs for a one-month period from one mirror. We figured that would be a good enough estimate of "most-used." The only human editing was creating the "special testing squad" of modules, since this was ultimately a testing project, and to remove two or three very specific modules that we judged to be too out there for people to work on. I'm glad that people have found use from the Phalanx 100, although it hasn't been updated in years. But I'm also not surprised that it doesn't suit your purposes. It's kinda like Frank says to Janet about Rocky, "I didn't make him... for YOU," and the audience says "But she gets him anywaaaaay."
    --

    --
    xoa

    • At the time that the Phalanx 100 was created, my specific beef was that it didn't appear to factor in dependencies.

      So while we got a list of 100 modules, they weren't ACTUALLY the most 100 used, just the 100 most in some other sense.

      I do, however, appreciate that they were based on usage data, as opposed to dependency data. And I totally plan to start factoring that into some of the indexes, once I've got the basic naive ones working.

      • I guess I take issue with your "beef" because it was never intended for your use. We didn't make any assertions as to how the data should be used, so it's not fair for you to say it's not what you want.

        Our feeling on dependencies was that dependencies would have to get downloaded, too, and so those downloads would show that traffic. So you get dependencies in that data, but not weighted by the number of other modules that use the dependency. A single-use dependency would get as much weight as, say, HTM

        --

        --
        xoa