Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

comment on

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

My question is entirely political in nature.

I recently posted a package to the CPAN, which was met with very harsh reviews due mainly to its use of source filters. Although I feel I've addressed the issues raised by reviewers, the negative feedback remains. If I were looking for something on CPAN, I'd probably skip over my own package because of its low rating. I'd give it at least a 3, but I'm clearly biased.

I'm wondering how others have dealt with similar situations? cpanratings allows you to post a comment as an author, and I did so, stating I had made several changes. One person was kind enough to retract their review, but I don't think the other person is going to do the same.

Should I try to publicize my project a bit and try to get more reviews? I don't think there will be many more reviews incoming, since people are probably passing over it now. I would contact the reviewer but I don't see that he's an author of any modules, and I don't know how to get a hold of him.

Not mentioning the project by name, but if you're interested, I'm posting this as my CPAN authors name-- look for the project with a 1-star rating. Always looking for feedback.


In reply to 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.