more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Regarding the other case ... if you can't be polite, don't be impolite. Just close the bug selecting "N/A" or similar reason. Great advice, but I think its missing the don't get mad message I've seen a few prolific authors who can't handle bug reports for things they've documented ... and the real problem isn't that they can't be polite , it is that they get mad -- once you're mad you're mad :) you don't gotta help , you don't have to be nice, but don't get mad , there is always going to be another one more anonymous somebody on the internet who won't read the docs... and they'll just keep coming, and coming, and posting OT question, and reporting bugs in other modules, and posting spam, and again, and again, and again ... and this can feel like harassment and offend the best of folks .... and when these "posters" receive not polite anger fueled responses -- it only results in angry impolite exchanges --- nobody profits When you're feeling angry and rantish, write it down and do not publish for a week, or a month, just ignore it Then come back to it a week or month later, and see how you feel about it From personal experience, I did that a dozen or so times (write the unkind words down), and it's been a long time since I felt the need I tried to search for this sort of ideas, and I found http://www.shlomifish.org/philosophy/psychology/hypomanias/dealing-with-hypomanias.xml, its not unlike dealing with trolls, don't let them get your goat :) just don't deal with them :) In reply to Re^4: Is bug report a contribution? (don't be mad at internets)
by Anonymous Monk
|
|