Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

comment on

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

This is one feature that I wished that they removed from CPAN. Reviews don't generate enough traffic to be meaningful and when problems with a module are fixed or addressed ratings are not changed to reflect this.

A good example is Module::Build, it has a rating of 3. It is currently on revision 0.34 and got reviews as early as revision 0.19( which was in 2003). A person complained about the lack of PREFIX support and gave it a 1 star in 2005! I am sure over the course of 4 years that issue has been addressed but that rating is never going to change.

Ratings for CPAN modules are more like credit scores but they don't go away after 7 years. They just have no relation to reality, so don't worry about.

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