Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

It has often been said that CPAN is Perl's 'killer app'. The biggest problem with CPAN however is finding what you want. is a fantastic tool for finding stuff but here's an idea for making it even 'fantasticer'...

When you click through to the main page for a distribution (eg: LWP) you get one link for CPAN Testers and another link for CPAN Request Tracker. Wouldn't it be great if there was another link called something like 'Discuss this module' that linked through to Perl Monks?

For this to work well, modifications would be required on both the search.cpan end and the PM end. On the PM side, the best idea would probably be to create a new section called 'CPAN Discussions' (perhaps some clever person could translate this to fit better with the monastery metaphor).

If someone followed a link to discuss the LWP distribution, the node they reached could include:

  • Links to reviews
  • Links to tutorials
  • Links to general comments
  • Links to version-specific comments
  • Links to relevant newsgroups, mailing lists, web sites ... (Edit: added)

Anyone could post replies to the main node in the standard PM style (eg: to say "this module is obselete, check out module 'XXX' instead"). When posting a reply, they could check a box to indicate whether their comment applied to a specific version of the distribution. A common use of replies would be to link through to relevant existing nodes.

I'm thinking that the link from might look something like:

But I have no idea how hard it would be to hack this into the Everything engine.

What do people think?

Update: Apparently Gabor thinks it's a good idea

In reply to comments/discussion by grantm

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (9)
    As of 2018-06-18 18:07 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (110 votes). Check out past polls.