If you're really interested in contributing to the Perl community, there are plenty of ways to do it without actually crafting your own CPAN module. Unless you really have an innovative package that the world is clamoring for, what's the point? Instead, here are some ideas:
- Review others' work, submit patches for bugs/perldoc enhancements, etc.
- Tutor new monks in the art of proper namespace usage
- Understand the apocalypse
If you insist on making your mark in CPAN, focus on existing modules that might interest you. For example, I've always wanted to enhance some of the *::SSH::* modules out there. Granted, I've never had the time to start that project, but it would be a better use of my time and skills than trying to create a new module that nobody would really use.
-
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.
|