You are able to give back to CPAN, maybe not perl code but that's not all there is.
For example, what if you find a bug in a module? Or something you believe is a bug? You can always mail the module maintainer and inform him about it. After which he can look at it and fix the bug.
You could also try to create a little test-case/script and send it along with your bug report so that the maintainer can easily check if the bug is fixed and perhaps include the test in the distribution. (To make sure the bug is fixed once and for all.)
Another thing you might be able to do is mail the module maintainer about a unclear statement that is too unclear in the docs. You said it yourself, you are not a programmer, perhaps the programmer who wrote it considers it to be too obvious to add a bigger explanation?. Perhaps you don't understand all the constructs used in the module's documentation, perhaps the examples need to be easier, ...
If you do that then you are indeed not contributing code or modules to CPAN but you certainly are contributing to CPAN (IMHO).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||