How do I know? I have these implementations here. Will I contribute them? Not to this CPAN.
How does refusing to contribute high-quality modules serve your stated goal of improving the quality of CPAN? Are you trying to punish CPAN or the Perl community by withholding your modules? What would happen if everybody followed your example?
The key point that you disagree on with me and at least some others in this thread is that "Unrestricted CPAN submission increases CPAN usefulness, Perl usefulness, and Perl popularity". As a CPAN user, I certainly appreciate being able to see everything that the contributors have to offer. If a module is crap or unmaintained, it's usually obvious pretty quickly. And even if it's not suitable for immediate use, I may be able to take some ideas or code from it, thereby making the job of re-implementing the module easier.
As a CPAN contributor (which I am not now but may be someday), I will appreciate being able to contribute my module, even if it is not 100% perfect and bug-free. That way I can get the most feedback on my code and contribute to others' use of Perl.
-
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.
|
