Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I can think of a couple ways to counteract the negative review. Firstly, create a list of your module's strengths. Since you only first released it a few months ago (according to the "Changes" file), you must have done some research which led you to believe there are some advantages over other similar modules, such as:
  • Unique methods/functions
  • Convenient methods/functions
  • Optimized for speed/memory/whatever
  • Portable across unix/windoze

You should mention some of these advantages in the module's POD, instead of down-playing it, as you are currently doing.

Secondly, consider promoting your code by participating more in on-line forums, such as PerlMonks, if you are not already doing so. For example, answer questions posed by Seekers of Perl Wisdom, and offer your code as a potential solution, where applicable. Demonstrate to the public that your code is indeed valuable by providing concrete examples to solve a problem. I learned about many of the CPAN modules I use today because I saw others posting code here at the Monastery, not by reading a CPAN review.

By the way, I have seen other authors post reviews of their own modules when they release new versions. It is a good approach.


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

Title:
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.