Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

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

If you (not OP - you!) care about this issue the best thing you can do *right now* is go review at least 5 modules you use regularly or are of particular importance to one of your projects. At least give a rating and a paragraph explaining it, it doesn't have to be extremely detailed.

The fact is ratings are displayed prominently on search.cpan regardless of how many have rated, or how sensible or old it is. There's also no system in place to weight ratings based on the % of people who find it useful. The best thing to do is up the review counts and drown out the "noise" of non-sensible/old reviews.


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