I agree with you on the need to calm down. But I also agree with schwern's point about rt.cpan and dedicated mailing lists - those and private mail are the only places you can really count on an author seeing the input. I think the way you ( Tanktalus) approached it in the node you cited was the best way to do it - you said (paraphrasing) "I've found a problem but I'm not sure which module it applies to, does any monk have some wisdom? If not I'll send a bug report to the author." You were using PerlMonks to its full advantage, gathering the collective wisdom, but you also realized that if you couldn't find an answer here, the right thing to do (for yourself and for me, as the module author) was to contact the module author.
I was going to stay out of this particular thread, but since I'm here anyway, just let me say to schwern: a) thanks for all of the fantastic work you've done and the many contributions you've made to the Perl community and b) chill out dude, no use getting *your* blood pressure up just because some people like to whinge. (also, it's harder to see the difference between a whinge and valid feedback when your blood pressure is up.)
-
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.
|