Mm, not an aspect I'd considered, I must admit.

However, I'm not sure I agree that bad feedback is much worse than no feedback. A trollish or daft feedback mail can just be binned. How much notice to take of feedback is a judgement call on the part of the author. If you are getting helpful feedback from a range of regular users, then a POD skim is not likely to be helpful.

On the other hand, for those of us (raises a timid hand) maintaining 'niche' or new modules, which don't have a significant user base, feedback saying 'xyz is not really clear/your constructor syntax is difficult to follow' etc might be of help.

I come back to the comment earlier in the thread - I'm not suggesting that we replace the process of CPAN testing, but widen the range of QA by looking at the POD of distributions that otherwise might not go through any other public testing.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.