There exist hundreds of ideas - some also crap but others perfect - how to improve quality of CPAN.
By submitting high quality modules, increasing the overall quality of CPAN.
I wouldn't object to the theory, that the Perl community *fears*, that a rigorous evaluation and control of the CPAN modules would bring the poor condition of the CPAN repository to light.
Have all the theories you want, but CPAN isn't "owned" by "the Perl community". CPAN is a project of a few (Jarkko, Andreas, Elaine, ...). Anyone is free to contribute. Anyone is free to not contribute. Anyone is free to start another project, with a different policy. But CPAN's policy has always been that anything is welcome, as long as it's freely distributable (and Perl related). And the CPAN people have stated in the past that this will be the policy for the foreseeable future. Any sort of "control" over modules on CPAN will make that CPAN no longer is CPAN. CPAN is a huge success, and in my opinion one of the major reasons, if not the most important reason of the success of Perl. Even if you could, would you be willing to risk that?
There exist hundreds of ideas - some also crap but others perfect - how to improve quality of CPAN. This is technical detail IMHO. What matters most, is to get the Perl community to accept such a project/shift. As for now, it seems like a holy cow where even providing download statistics or some kind of voting system is perceived as a hypothetic discrimination...
IMHO there is a golden way between the present laissez faire and "running the gauntlet" for module authors. My dream is, that we - the community - find and adopt it.
I really hate this kinds of posts. It's of the form " I don't like X. We should do something about it." But if offers zero suggestions of what should be done. And while it mentions "hundreds of ideas" from the past to change it, it discusses none. You probably rake in a fair amount of XP because of its emotional value, specially if some sucker frontpages it. You get a '--' from me though, because it's just whining, and calling others to solve your (perceived) problems.
Abigail
-
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.
|
