Monday, November 26, 2007

Oh forget it.

I have a pet peeve with a great deal of the OSS developers out there. Now, this doesn't include all of them -- some of them behave considerably better than others -- but I have had the misfortune to stumble upon far too many that anger me to the point of not wanting anything to do with Open Source projects that it isn't funny any more.

My pet peeve is with bug reporting. Most OSS projects have a bug tracker and in theory they encourage users to post bugs so that they can be tracked down and fixed. IN THEORY.

The problem is, in an absurd amount of projects, if you actually take the time to write a bug report that isn't a duplicate, and describe the problem as best as you can, some developer will come along and dismiss you as an effing moron.

Let's say that I notice that the latest version of one of my favourite applications has this slight bug where when I do one thing, like maximise the window, my cpu usage will skyrocket. Now, this doesn't happen when the application is minimised, and it didn't happen with the previous version, and it also doesn't happen with some different window configurations.

Now, being a responsible OSS application user, I will report this odd behaviour to the application's bug report, thinking, oh, this must be a new bug in the application I'm using, because it doesn't happen with any other application, any other VERSION of this one application, or with some other configurations of my system. Since this behaviour is NEW, and the only thing I have changed is my APPLICATION, it MUST be the application's fault -- goes the logic.

With the bug reported, all should be well right? The developer should look at my bug and ask me questions or try to duplicate it or other things, right?! NO! What do I get?! I get the developer telling me that it's NOT the application's fault, it must be my window configuration. That's right, even though if the developer had actually READ my bug report, they would know that THIS BUG DIDN'T HAPPEN UNTIL THE NEW RELEASE WITH THE SAME CONFIGURATION. BUT DO THEY READ THAT PART?! NO! THEY TELL ME THE BUG IS INVALID AND CLOSE IT, REFUSING TO HEAR THAT THEY MAY BE CAUSING USERS OF THEIR APPLICATION ISSUES!

WTF.

Why the hell do they even have a bug tracker then? Why not just say to all their users, "everything is someone else's fault, not this application, so go complain to them."

Look, if you don't want users filing bug reports, DON'T ASK THEM TO. If you don't want to hear a goddamned word that someone may be trying to tell you about your new code base, DON'T ASK FOR IT.

I am absolutely sick of this mentality.

Want to know why people don't bother posting effing bug reports? That's pretty simple: YOU DON'T LISTEN TO A DAMN WORD THEY SAY!

Honestly, I'd rather spend my time finding an alternate application than post bug reports any more, it's just not worth my time to be told that kind of garbage*.

(*see rant on gaim/pidgin for yet ANOTHER example of bug reporting / developer idiocy.)

2 comments:

eliott said...

Yes. Some projects don't recieve bugs well. Some projects have shitty developers.

I have been on the other side though, having to deal with mountains of horribly documented bugs that are problems with configurations and environments. Clearly not the problem of the software app itself. It can be burdensome to filter through the mountain of crap to find good bug reports.

*However*. Some projects are amazingly great. Some bug reports are awesome and useful.

At the end of the day, I am just glad I am not submitting a bug report on some closed source software that I *know* will never be fixed in my lifetime...

;)

Cerise said...

I've been on the other side too -- and getting a bug with, "It don't work. Dunno." can drive any sane person to postal-level insanity (and that's assuming that developers are sane to begin with...questionable.)

I just don't want to be tricked into thinking that the developers actually give a rat's if they don't. I'd rather know ahead of time that it will never be fixed because they can't be $#@%'ed than to be encouraged to spend time and post bugs when they won't listen to a single word.

Tell me upfront that you don't want any reports of problems and I'm cool. But if you tell me that you do want bug reports and then reply without even reading the bug report -- that's when I have a problem.

Just do what you say you're going to do and all is well.

;)