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.
  • I welcome your thoughts. How can we capture the good part of the module list (the human filtering), and remove the obsoleted infrastructure?

    CPAN is pretty special, but it isn't unique. How do other sites solve this?
    Looking at CTAN [ctan.org] (on which CPAN was originally based), I see they allow browsing of the entire site contents, as well as search interfaces through several interfaces, including Google. So here's suggestion number 1:
    * Add a Google search!

    What else? I'm not sure. Maybe something like DMOZ [dmoz.org], but specific to CPAN. Personally, I don't buy the "one man decides on which module is good and which isn't" system. If it's properly tested and has all the required files (README, MANIFEST, etc.), it should be listed. After all, one man's dross is another's gold... :-)
    So suggestion number 2 is:
    * Use the "open directory" method, where everyone who wants to becomes an editor.

    I'm sure there are other sites out there who could serve as good examples. Perhaps a Wiki based site, with module specific pages?

    I don't know what would work- it depends to large extent on how the community would get involved. I do however agree that the current interface needs to change, just as I agree that it would be smart not to break anything before making sure we have a replacement ready to take its place...