Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

CPAN Ratings: the social failings of a useful system 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • how do we get people to direct comments (even if we knew where those should go) and bug reports to their respective, correct venues?

    How about some review guidelines just above the "Review" box? Such as:

    "Do not use this to report bugs, it is likely the author will never see it and it won't get fixed. Please report bugs via [link to the distribution's rt queue]."

    Ironically, use.perl is not the bug report forum for cpanratings. :) I'll mention this thread to Ask so he sees it.

    While I'm at it:

    "Think be

    • Hey, thanks for the comments. I am aware that this is not the bugreport forum for cpanratings :) (though I’m not sure what is), but I wasn’t reporting bugs so much as hoping to kick off a bit of discussion. (Maybe I should post to Perlmonks as well.)

      Some explanatory text would certainly help. It won’t suffice, I think, but it sure would be an improvement over the current situation. Having ratings mailed to authors is a good suggestion, but I’m not sure how it relates to my points;

      • I am aware that this is not the bugreport forum for cpanratings :) (though I’m not sure what is)

        About [perl.org] says to email ask@perl.org.

        (Maybe I should post to Perlmonks as well.)

        Speaking of places where bugs are reported which never get back to the author.

        Having ratings mailed to authors is a good suggestion, but I’m not sure how it relates to my points; was it supposed to, did I miss something?

        I was just sort of on a roll at that point. If nothing else it means the authors might actually r

        • Speaking of places where bugs are reported which never get back to the author.

          Uh, I did say that the intent was to get some discussion going to exchange ideas maybe, not to report a bug. The issues I brought up are no bugs; see also the title I chose.

          Just about every author has an user@cpan.org address. Its best way to guarantee the author, any author, will get your message.

          I agree, but that isn’t the direction I was talking about. I was wondering how the author (or someone else) could respond to a review(er), because that is what currently goes wrong in the system. The reviews seem to reach authors just fine in many cases: several authors have reacted to my reviews, one of them even had the sense to search long enough to find my email address. It won’t hurt to make this more convenient for authors too, of course, but that's not the pressing issue.

          As for bugs, yes, I had already mentioned that they shouldn’t be reported on cpanratings in the first place.

          •     Speaking of places where bugs are reported which never get back to the author.

            Uh, I did say that the intent was to get some discussion going to exchange ideas maybe, not to report a bug. The issues I brought up are no bugs; see also the title I chose.

            Just a general hate flung in the direction of Perlmonks. You just happened to be in the path.

            I agree, but that isn’t the direction I was talking about. I was wondering how the author (or someone else) could respond to a review(e

            • Ah! Of course. Noone but the author really needs to respond to a review. Good thinking. I’ll add one minor point: an author should not be able to post “self-reviews.”

              I think together with the stuff I wrote in reply to Ask that makes a cohesive set of proposed changes to mitigate the problems we currently see. I’ll summarize these in an email to him and see if I can lend a hand with the implementation.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.