I don't think a CPAN2 is a good idea. It would be easier to make the current CPAN a better place. And thats quite easy by just writing another Gate to CPAN. So in your case, you could write a kind of search cpan e.g. for linguists which just returns trusted modules who passed your reviews. Thats all needed for a better CPAN, including only the part of CPAN you or your contributers are able to judge. Gateways for specialists like Linguists, Biologists or whatever seem to be a good way, to make CPAN a better place. That probably will not change the attitude of some writers, who advanced to lesson 2 of there beginners textbook of some foreign language, to immediately write crap modules, but at least we could find out, which modules we can trust or not.

If you want to start such a project, I may volunteer to participate, if it does not become an aggressive page. This means, fair reviews even if this means "crap module" are fine to me, after the author had a change to correct his mistakes. Writing "crap module" without contacting the author in advance, is not the kind of style I could cope with.

In reply to Re: Re: Re: The quantity vs. quality lesson by Hanamaki
in thread The quantity vs. quality lesson by PetaMem

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.