I read the list of new submissions to CPAN on a daily basis. I have found it impossible to get authors to add related modules to the SEE ALSO section of their docs. Sometimes they don't respond. Sometimes it is egotism. Sometimes I just don't know. But the bottom line is that there are a lot of modules related to each other that people don't know about.

The ideal solution would be to cobble up a database and render HTML from that , but i am too lazy to do it.

Also, one needs to distinguish between

plain jane lists of modules
Here is my list of modules for lazy loading. It is nothing but a list, with no attempt to feature-compare. Ok, there's a bit of feature-comparison, because I draw a line between modules which only do lazy loading and modules which offer lazy-loading as part of a larger functionality-base.
lists which make comparisons of features
Here is where simonm makes a feature comparison of various DBI wrappers. It is an example of not just blindly listing things, but attempting to make a comparison of them.

We can probably also place choosing a templating system by perrin in this category

Aristotle's A brief survey of the DBI usability layer modules on the CPAN also falls into this category. as well as tphyahoo's survey of surveys of templating systems

reviews based on use cases.
These are usually submitted to the Perl conference or YAPC::NA. They are very useful but time-consuming. for example, I have developed DBIx::Recordset::Playground which gives runnable code sampls for using DBIx::Recordset, but I cant imagine getting the work for 3 or 4 related modules done as well. I was happy in a thread I created long ago to have autarch submit some Alzabo code to compare with how other DBI wrappers would do the same thing.

Concluding, I am mainly interested in a place to develop blind lists and perhaps having the follow-ups relate personal-experience or feature-comparison.

If you notice, there is an ever-growing set of off-site links from search.cpan.org for each module - AnnoCPAN, CPANForum, CPANTesters, CPANreviews. It seems to me that CPAN-related is a gap that could be filled by a section of this website. What do you think?

In reply to A CPAN related modules section by metaperl

Title:
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, details, 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, summary, 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.