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.
  • Imagine for a moment, that you had access to all the metadata in or on CPAN.

    That is was trivially easy with almost no work, to relate authors, dists, modules, dependencies, testing failures, kwalitee, mirrors, RT bug reports, and all the other metrics for CPAN.

    The data is currently sitting in the CPAN index, in CPANTS data, in CPAN Tests data, all over the place, scaterred on 4 sites, and accessible sometimes only through the modules and APIs for those specific systems.

    You can access it, but you really have to work at it.

    I want easy access to the lot.

    I'm encouraged by a study about the browsers wars that concluded that for browsers, the easy of procurement and installation was TWICE as importing as the quality of the browser itself.

    So I quite simply want all of the CPAN Metadata, available as one or a few DBIx::Class classes, wrapped around SQLite databases that live at stable, known, URIs.

    I want to be able to do something like...

    my $author = CPAN::Meta::Author->find( 'ADAMK' )->modules;

    Or write some 10 line functions to answer questions like

    "Which CPAN authors have the highest per-distribution bug counts"

    "Who wrote the code for all the modules my application is recursively using"

    And so on.