17 May 2007 cinamod   » (Master)

I know that I and my projects haven't been the most responsive when addressing bugs. And for that I must apologize. Truth be told, there are always a lot more reporters than there are developer hours.

As a free software user, I understand closing a bug due to lack of feedback or insufficient information. As a free software user, I understand closing a bug because it can't be reproduced by the development team. As a free software user, I understand closing a bug because it's been filed against the wrong project and there's no good way to migrate the bug between the two projects. I may sound a little like JWZ here, but I don't understand a project closing all of its bugs because it changed its name and moved its bug tracker to another server.

I got this gem in my inbox yesterday from Gaim's SourceForge.net bug tracker:

As we have now renamed the project, and are migrating to developer.pidgin.im, I am closing this ticket. Please create a new ticket at http://developer.pidgin.im if this issue persists with 2.0.0

At least in JWZ's "Cascade of Attention-Deficit Teenagers" post, all of GNOME and its supporting libraries were basically rewritten from scratch when the bugs got closed. It's like saying "we changed and accomplished so much that we're hopeful that these bugs are gone. Please try again, because there's some non-zero chance that your bug got fixed."

Here, the project in question ran `sed 's/gaim/pidgin/g'`, moved their bugzilla to another machine and thought that those actions justified closing all the bugs rather than migrating them. This is hardly a spongeworthy accomplishment.

I really do appreciate all the hard work that the Gaim/Pidgin crew has done. I use it daily, largely without issue. I advocate it to my friends and co-workers. It's a good piece of software. Unfortunately, I haven't personally helped them out in any way beyond filing a few bugs. And I understand that migrating bugs from SF.net's tracker to your own might not be the world's easiest task. But those bugs are nonetheless a contribution to the project, and I'd like to think that those contributions wouldn't be thrown away with such reckless abandon.

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!