UbuntuBugDay
Announcing the Hug Day (or Bug Day?)
With Feature Freeze past us, we finally can focus on getting bugs fixed and get all the bits and pieces together. The best thing for us to do at the moment is getting an overview over our bugs. We'll have a Hug Day to to help our Bug Team to get up to scratch and everything sorted.
Despite of [http://www.osnews.com/permalink.php?comment_id=104201 ignorant opinions] on our concept, we know where our success comes from. That's why we're going to stick to our special Bug Day. We're going to have lists of things to do of different Ubuntu teams, so we can better track the impact we had. Planning is one thing, but we'll surely stick to our concept of success: the Hug Day. This is a very special Bug Day: on Hug Day, when someone closes a bug, then someone else should hug him/her. Why? This is a very special way for us to tell everyone that we love contributions! And triaging bugs is a really big contribution.
In addition to that we added ["UbuntuBugDay/BugsForExtraPoints"] - a page where you can list your most annoying bugs. Fixing these bugs will give extra points and extra hugs of course.
Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain you everything.
Where to join the Hug Day? #ubuntu-bugs on freenode IRC. And you can go there every other day too!
When to join the Hug Day? Next hug day is on March 17th, 2006 In all timezones. But again, you can go there every day and help with triaging the bug tracking systems.
We can't stress it enough: everyone can help. So join us for the Hug Day!
Tasks
Stuff to sink our teeth in.
- (Gnome) Desktop Team:
- MOTU Science Team:
http://tiber.tauware.de/~laserjock/bug_list.html - list of source packages in the math, science, and tex sections with bugs.
- The MOTU Science team (["MOTU/Teams/Science"]) will hopefully get all the science related bugs triaged and at least a few Hugs earned.
- KDE Team:
- Poke Riddell for help
- Firefox:
There are many [https://launchpad.net/distros/ubuntu/+source/firefox/+bugs?field.searchtext=&orderby=-priority%2C-severity&advanced=1&field.assignee=&field.unassigned.used=&field.include_dupes.used=&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status-empty-marker=1&field.severity-empty-marker=1&field.attachmenttype-empty-marker=1&search=Search Unconfirmed firefox bugs] and any help triaging them would be greatly appreciated.
See DebuggingFirefox for some hints and tips.
- ["XSwat"]
[https://launchpad.net/people/ubuntu-x-swat/+packagebugs package overview]
[http://tinyurl.com/9gs46 Unconfirmed Bugs]
[http://tinyurl.com/9zma4 Confirmed Bugs]
- talk to fabbione and infinity
Everything related to hotplugging ([https://launchpad.net/distros/ubuntu/+source/hal/+bugs hal] and [https://launchpad.net/distros/ubuntu/+source/gnome-volume-manager/+bugs gnome-volume-manager] bugs)
- This needs many testing especially on current Dapper. Many open bugs are probably fixed in current Dapper, and didn't see an updated test from the original reporter. Also, many are just not easy to reproduce.
- Talk to pitti on IRC.
- Security bugs
Vulnerabilities which already have a CVE number assigned are automatically tracked on [http://people.ubuntu.com/~pitti/ubuntu-cve ubuntu-cve].
If you find an unassigned vulnerability which affects a package in main, assign it to martin.pitt@ubuntu.com.
- If you find a vulnerability without a CVE number, ask pitti about finding one, as these numbers are very important for efficient tracking.
Resources
["UbuntuBugDay/Draft"] (Draft of the announcement mail)
["UbuntuBugDay/Attending"] (People from the Distro team attending)