Re: Unread bug reports ?
On Sat, 25 Jun 2011 20:39:44 +1000, Scott Ferguson wrote:
> On 25/06/11 19:43, Camaleón wrote:
>> I can feel his pain :-(
>
> Which does nothing to negate the problem caused when this list is
> broadcast on side band where swearing is illegal, or when it offends
> thin-skinned people.
When you are frustrated, it's normal to use such terms. Nothing illegal
per se, at least not in my country. I've read worst things in another
mailing lists...
Yo can change that "bull****" with "crap" if you find it's a more
"politically correct" term for your soft mind >:-)
> I can validate his anguish also. I also know several developers who,
> wrongly, have acted like sulky children when people demand things from
> them.
> And like watching someone shoving at the outward-opening door at the
> Institute for the Intellectually Gifted I feel compelled to offer them a
> more productive approach to the problem...
Sure, bad reactions can go from both parts (reporter <-> developer).
Humans can always have a bad day.
>> You open a bug report willing to help and you get no reply... that's
>> very discouraging for the reporter. And I am not talking here about to
>> get the bug solved *now* but just a single reply that makes you think,
>> "hey, at least someone cares about it and it's being debugged".
>
> Here - have a hug. Feel better? ;-p
Nice try, but nope.
Should I wanted a hug I would have go to meetic not bugzilla ;-)
>> But no reply is the "common" way for every bug tracking system I've
>> used: most of the time the bug is solved because is so old that the
>> application is no longer maintained >:-)
>>
> I could have looked in the wrong places - but it didn't appear the
> maintainer of the package in first quoted bug-report has been active
> since January. But then I spent all of 2 minutes looking.
Which is fine... but in such cases there should be the figure of an
ombudsman, the "glue" that acts when no one is in charge of a package- or
that seems to be missing- that at least lets you know what is happening
and what's the bug status. With accurate information, you can quietly
wait or go upstream with the bug. You have more choices.
Not news is not good news is this case.
> NOTE: the swearing, followed by the "it never worked" (if it never
> worked, then it's not broken now!) was promptly answered by the
> maintainer. Do you think the maintainer will be so quick to respond next
> time?
(...)
I'm not judging the words expressed at the bugs reports but a situation
every bug reporter knows very well: when no one asks you for more
information on the problem and the bug falls into the Helm's deep in
forgotten realms. Then the last chance is "airing" the bug in mailing
lists and pray for someone reacts.
Greetings,
--
Camaleón
Reply to: