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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|