Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

To be honest, I wouldn't worry about it that much.

I for one never even see CPAN ratings. My interaction with CPAN is all done on the command line.

If you want people like me to consider your module, the things you should be worrying about are, most important first:

  1. The name. If I can't guess what your module does from its name, I probably won't even glance at it. (Cute names like "Moose" can work, but only if you put the effort into publicity.)
  2. The README. This is the first thing I look at once I've found a promising name. It must contain a clear statement of what the module has to offer. If it doesn't catch my interest, I move on.
  3. The license. There are some nasty surprises on CPAN -- complete modules that can only be used for non-profit purposes, for example. I need to be able to find the license quickly, and it needs to be a standard one -- preferably "same terms as Perl itself".
  4. The POD. If the README looks promising, I read the module's documentation. I'm looking particularly for clear usage examples.
  5. If the documentation doesn't quite convince me that I've found a quality module, but it looks like it might do what I need, I look at the code itself to see whether it looks well written.

Arbitrary scores from random reviewers don't even figure. I probably don't know those people, and I have no way of judging whether they're qualified to review your code. Why would I care whether they gave it one star or five? Forget Web 2.0-y fluff; it's the meat of the module that matters.

In reply to Re: Dealing with CPAN reviews by Porculus
in thread Dealing with CPAN reviews by aayars

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.