The other part of that is to be a tester for the CPAN.
Check out http://testers.cpan.org and sign up to be a CPAN
tester. You'll get an email each time a module is uploaded
to the CPAN. Try to install a module, and send the results
to the CPAN with a handy-dandy little script. It adds a
few seconds after each time you install a module, and it
helps the authors know what works and doesn't.
I've been doing it for about a year now. It's certainly
not as useful as Chromatic going and writing up bunches of
tests for key modules, but then again, if people don't run
those tests, what good are they?
xoxo,
Andy
--
<megaphone>
Throw down the gun and tiara and come out of the float!
</megaphone>
-
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.
|
