Thanks for contributing to CPAN, and for asking this question on PerlMonks. I've learned about a few resources from the other responses.

Here are some factors I consider when looking at CPAN.

I look at reviews before choosing a module, and appreciate intelligent comments and responses that help me to choose among several different modules. As stated elsewhere, the review section is often empty.

Your CPAN module includes a significant amount of code and documentation - docs are a plus.

You have been updating it recently, several times in the last few weeks - recent activity is a plus.

You responded to the negative review with a specific comment to one criticism. However, you did not address the second criticism (many dependencies). Your INSTALL note mentions the fact that there are many dependencies. Perhaps you should also mention it in your review comment, so anyone reading the reviews will see the issues raised and your responses.

Another idea is to provide a link from your review comment to the section in your documentation that describes your use of other modules and why you did that (rather than writing a long and detailed review comment that merely repeats data listed elsewhere in the package documentation).

In reply to Re: Dealing with CPAN reviews by clp
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":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.