g0n wrote:

One advantage of cpanforums does strike me though: a year or so ago, I was having trouble getting a module to work at all, and wanted to contact the author. I tried half a dozen different addresses that the author had listed at one time or another, and all bounced. If a module has been abandoned, at least Cpanforums gives the community the opportunity to advertise and/or discuss the fact in an obvious and well advertised location, with direct links to the module page on CPAN.

And that's why I'm posting this here: this is the meta-PerlMonks discussion section, and the place to suggest software, policy, and behaviour enhancements.

What I think about CPANForums is that this is Yet Another Place to Post Module discussion (not support, nor bugs! -- threre are specific, well-advertised places for them).

To make mine your example, if an author abandon a module, there should be a place at PerlMonks where the community could discuss about this and volunteers could offer your free time to take care of a module. Also, this place could offer RSS feeds for module authors about his/her modules, so they don't need to look for posts at PerlMonks.

What I'm effectivelly suggesting is that PerlMonks offer kind of a Module Forum, where architectural issues and orphanage/adoption of modules could take place, without interfering with the http://rt.cpan.org (for bugs) and the author's emails and discussion list (for support).

This way, the community could concentrate its activities arround a single place, easying maintainer's life and making simpler and fair the adoption of orphaned modules.

But this, of course, is just my humble opinion about what I've read about this issue.

-- monsieur_champs

In reply to Re^2: A room for CPAN Modules discussion? by monsieur_champs
in thread A room for CPAN Modules discussion? by monsieur_champs

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.