I took my own advice at submit-cpan-ratings - upload ratings to CPAN for stuff you've used.

This ought to be a script: run it against a source tree and it'll find the modules you used, ask you if you have an opinion on it, solicit some text and prompt for a number of stars.

C:\Documents and Settings\diotalevi\My Documents> submit-cpan-ratings 
+Devel-Foobar\

Modules used:
   DBI-1.21
   POE-0.21
*  WWW::Mechanize-0.12 (already rated)

Comment on DBI-1.21 (enter two blank lines to finish your comment):


Comment on POE-0.21 (enter two blank lines to finish your comment):
I love it. I get the benefits of IPC and/or threads all without having
+ to use threads or forking!


Use this comment? (Y/n):

Rate POE-0.21
  Documentation (0 - 5)? 4
  Interface (0 - 5)? 3
  Ease Of Use (0 - 5)? 4
  Overall (0 - 5)? 5

Thank you! Now uploading your ratings to http://ratings.cpan.org.

[download]

Added: The easy bits are: ExtUtils::MakeMaker does something File::Find-like to fine .pm files, do some basic source regexing to find a list of packages, then just load them and say things like $version = POE->VERSION and DBI->VERSION to get the proper version. From there on out, cpan-upload is an example of storing your cpan credentials locally (and of uploading a script to cpan), use WWW::Mechanize (or something lesser) to submit the results, make a note locally on which module versions have been rated.

In reply to Re: CPAN ratings without reviews harmful or not? by diotalevi
in thread CPAN ratings without reviews harmful or not? by Solo

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.