Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re^2: Is bug report a contribution?

by Tux (Monsignor)
on Oct 08, 2013 at 10:32 UTC ( #1057404=note: print w/ replies, xml ) Need Help??


in reply to Re: Is bug report a contribution?
in thread Is bug report a contribution?

Many bug reports/tickets are posted in the wrong queue, because people don't/can't/won't analyze the actual *cause* of the problem.

If module Foo::Bar is just a wrapper over Foo or a subclass of Foo, the problem might very well be hidden in Foo, way out of reach of the author to whose queue the bug was reported. Same for failures regarding system libraries malfunctioning (libxml2, libcrypto, ) or installed basic utilities with severe bugs (tar, cc, bash, ) for which the author of a module cannot be held responsible. IMHO a CPAN author may expect functional bash/cmd, tar, and cd.

Sometime it is hard to be polite to ticket posters telling your module sucks because it doesn't work on their system, even if Makefile.PL and README specifically state that their system or configuration is not supported because of a very good reason (e.g. DBD::Oracle will not install if there are no Oracle client libraries available: that id NOT the fault of the author/maintainer of DBD::Oracle and it is very well documented. I really understand how it pisses them of if people post tickets like that.


Enjoy, Have FUN! H.Merijn


Comment on Re^2: Is bug report a contribution?
Re^3: Is bug report a contribution?
by Jenda (Abbot) on Oct 08, 2013 at 11:01 UTC

    In case of the Foo::Bar subclassing/wrappig Foo, you as the author of Foo::Bar are in a much better position to forward the blame. You can't expect users of a "::Simple" wrapper to dissect the wrapper and guess all the preconditions and assertions you, the author of the "Foo::Simple", made about the "Foo" to find out whether there's something wrong with Foo or with the way you use it. And even if the problem is inside Foo, you usually do care. Even if the only thing you can do is to close it with "problem is in Foo, it was reported a year ago already".

    Regarding the other case ... if you can't be polite, don't be impolite. Just close the bug selecting "N/A" or similar reason.

    Jenda
    Enoch was right!
    Enjoy the last years of Rome.

      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 :)

        I concur. From personal experience, I've added the following line to my modules:

        The public support forum of this module is http://perlmonks.org/.

        This has relieved me from the burden of being the only knowledgeable person to answer questions, and also has relieved me of the burden of providing polite answers. If I'm not in the mood for a polite answer, maybe somebody else sees the question and can provide the answer from the FAQ or Troubleshooting, or find out that the question is not at all about a module by me.

        I also want to thank the people on this site for answering questions and generally keeping a civil tone.

Re^3: Is bug report a contribution?
by DrHyde (Prior) on Oct 09, 2013 at 10:42 UTC
    I do understand how annoying things like that are - I get them all the time from people who seem to think that they should report bugs in Some::Module to me because I list that module's pre-requisites on CPANdeps. Nevertheless, I try to be gentle. It doesn't cost me much to point them at the right RT or github tracker.

      Reading the replies, I get the impression that my statement was showing reasons to be impolite. I never meant that: I meant to say that I would understand authors to get upset, annoyed and impolite when that happens. As all of you say, we should still be correct and polite.

      Thanks for all additions. Even the regulars (on CPAN) can learn from this discussion.


      Enjoy, Have FUN! H.Merijn

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1057404]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (3)
As of 2014-07-26 10:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (175 votes), past polls