I personally think that a free-for-all PerlMonksesque threaded discussion would be of less use in this context. I do like the idea of having a node devoted to a specific CPAN module, but that's not the same thing as an editor doing the research to present a focused presentation of what's available out there.
Right now I use the XBEL Bookmark Exchange Language to store this kind of information. There are a couple of things that I would like to see added to the specification (multiple URLs for a "link" to support google cached docs for one), but it's perfect for storing most of what such a site would need. There's even a CPAN module to display it.
What I would do would be to designate editors for specific areas (Crypt, HTML, etc) and have them organize resources around their areas in an XBEL XML doc. Than the editors can fold their additions into the master documents displayed on the site. I would start with registered modules and then work down to stable ones from there.
Here's a proposed XBEL folder structure for a specific modules:
NameCPAN Module Link
CPAN Author(s) Link
Home page for the module
Description, including platforms supported
It would be no big woop to set up a display site on one's Perlmonk server account (one of the reason's I asked for one, actually). Hell's bells, I may just start doing this today. Let me know what you think.
- Usenet (Probably goggle as a simple start)
(I've already written a column on that, etc...)
- Useful modules that use it.
(This way one can point to specific code samples from the CPAN.)
- Alternatives with pros and cons to them.
- Dependencies (not just modules, but libraries and applications such
as Apache/mod_perl or GD)