A database where the community can do the categorisation?

I'm for this option, preferably wiki-ish to lower the barriers for contribution and change.

I've thought about this before and I think trying to get to tasks rather than categories -- or hierarchies of tasks -- might be the way to go.

A good model might be something along the lines of the Perl Cookbook or Advanced Perl Programming (2ed).

E.g.:

Q: How do I find all the module dependencies of another module or prog
+ram?

A1 -- if you are willing to execute the module or program:

# discussion of those modules

A2 -- if you don't want to execute the module or program:

# discussion of those modules

[download]

I think this would allow for a fuller community discussion of leading candidates and pros/cons of different modules. Part of the problem with search is the sheer number of options for some common tasks and the lack of context for what works well, what other people find useful, what is well-maintained, etc.

cpanratings, CPANTS, annocpan and bugcounts on RT help somewhat, but those still have to be navigated module-by-module to get any detail. (Thankfully, search.cpan.org does provide some summary of information of those.)

I've seen some attempts at this scattered around the web. Some examples include:

It would be nice to see one centralized, sanctioned place to collect these kinds of comparisons.

So how about it? Anyone else for cookbook.cpan.org?

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Module categorization by xdg
in thread Module categorization by szabgab

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.