Software bugs

Callum McKenzie notes that bug opening rates rates equal bug fixing rates in gnome-games, but Luis Villa’s experience is that that’s how bug statistics work in Free Software.

Popularity: 45% [?]

The Debian QA team hunt down and fix bugs in Debian packages, among other things. Most activity seems to be coordinated via their mailing list.

Popularity: 53% [?]

The KDE Community Wiki site has a guide to getting involved by helping out with bug triaging. It also contains more useful tips regarding making a good bug report.

Popularity: 63% [?]

Telsa sent a link to her Making the right sort of difference: bugs and what to do with them summary from her talk at linux.conf.au 2003.

She writes that she has recently had an opportunity to confirm that bug numbers are increased by an approaching deadline…

It covered a lot of material: finding bugs, reporting bugs and getting people to fix bugs for you.

You can also find an Ogg Speex audio recording of the talk at planetmirror (Australia only) or on the LCA 2003 ISO image distributed by various mirrors (see the linux.conf.au 2003 site).

Popularity: 58% [?]

… or why your browser bug didn’t get fixed.

Via Malcolm again, Dave Hyatt describes ways not to get your bugs fixed and the sheer number of potential browser bugs.

Popularity: 51% [?]

Via Malcolm’s diary, Joe Bork, a Microsoft software tester, writes about known bugs that go unfixed and the cost of fixing a bug (salary costs, regression testing, testing the fix and so on).

Popularity: 48% [?]

The Mozilla QA team finds, researches and reports bugs in the Mozilla projects.

Popularity: 45% [?]

The GNOME Bugsquad are the team who track current GNOME bugs.

They also have several resources for bug hunters including their own Bugzilla guide and a guide to triaging bugs.

Popularity: 60% [?]