About Me

Wednesday, November 10, 2010

Help Improve Ubuntu on 'Bug Day'

By helping to triage reported bugs, even nontechnical users can participate in making the open source Linux software better. 

One of the great strengths of open source software is that it is continuously being scrutinized and improved by users and developers around the world.

Ubuntu, for example, has a global community of participants who are constantly working to make the Linux distribution better by contributing to the development, design, debugging, documentation, support and other aspects of work on the free and open source operating system.

Today, there's a global online event planned in which anyone can donate a little bit of their time to improving Ubuntu. It's called Ubuntu Bug Day, and it's a great opportunity for users and fans to get involved and contribute to the operating system--no training or experience required.

Bug Triage
Ubuntu Bug Days are actually regular events in the Ubuntu world, and they typically take place on a dedicated Internet Relay Chat (IRC) channel called #ubuntu-bugs.
To join a Bug Day, you'll need client software designed for IRC; many options for various operating systems are available for free download. The IRC section of Ubuntu's online documentation lists several possibilities, but if you use a recent version of Ubuntu, Empathy is the default.
On average, more than 1,800 Ubuntu bugs get reported every week, and the primary task on Ubuntu Bug Days is to "triage"--or classify--those reports so that they can be addressed as quickly as possible. Much the way emergency-room patients get triaged the minute they walk in the door so that they'll get what they need as soon as possible, so bug reports are subjected to a similar categorization process.
Individual Bug Days typically focus on triaging a specific category of bug reports, and today it's bugs for which no associated package was listed in the original report. So, those participating in today's Bug Day will be going through bug reports that don't list which software package is affected, and then adding that information. Once that's done, the bug reports can be forwarded on to the appropriate place for fixing.
Open Source's 'Killer App'

No comments: