AboutWelcome to Free Software Daily (FSD). FSD is a hub for news and articles by and for the free and open source community. FSD is a community driven site where members of the community submit and vote for the stories that they think are important and interesting to them. Click the "About" link to read more...
* 658 New bugs need a hug
* 131 Confirmed bugs just need a review
Nothing needs to be said about how important Firefox is, it just needs to work. With over 1300 bugs currently open, we can use a lot of help getting the information needed to shake out the bugs.
More bugs, and bug reports, are good. No really, at least that's what Karl Fogel says in trying to squash the idea that bugs are "technical debt that developers must repay. Fogel, who works for Canonical on the Launchpad platform, says that it's a fallacy that growths in bug reports is bad. On the contrary, more bug reports mean good news because it means more users are using the project.
Six-monthly releases have become something of a talking point in free and open source software circles after the problems Ubuntu has faced with users unhappy over major bugs. The OpenBSD project has been doing six-monthly releases for the last 12 years - with no major bugs.
The object of this post is to make you think about ways we could improve each one. I’ll try to link to bugs where there are bugs, but a lot of these are quite new design decisions only present in 10.04 and hence don’t have bugs filed.
The openSUSE Project recently announced the availability of openSUSE 11.1 Beta 1 for wide scale testing and bug squashing. This development release is available in x86, x86-64 and PPC architectures as a DVD disk image (liveCDs are not available for the current beta).
Finding bugs in your code can be quite nasty—especially if you don’t know where to look. However, finding bugs automatically does not require astronaut training. I think it’s time to leave that “pleasure” to free (as in freedom) automatic static code review tools like the ones reviewed in this series of articles.
I read glyphobet's blog, itemizing frustrations he's had reporting bugs to Ubuntu. While I've not had frustrating experiences reporting bugs to Ubuntu, I've reported bugs to a lot of different open source projects, and had more than a few closed in a way I wasn't happy with, so I can definitely sympathize. I hope in Ubuntu these sorts of experiences are the exception, but certainly there's always room to improve.
In my own experience at having bugs closed in ways I thought were inappropriate or incorrect, while I was initially angry about it, after reflecting I realized in each case it was really a consequence that I didn't understand that particular project's bug philosophy and had filed the bug in a way that didn't adhere to their guidelines.
One of the things I’ve always liked about using Linux is the feeling that my input is actually important. Either by way of giving input to the developers directly or (more importantly) reporting bugs that inevitably appear on a system. It’s the latter of the two that help Linux. But to the new user, these bugs are nothing more than a nuisance, getting in the way of things “just working”.
