Posts Tagged ‘hug day’

Kubuntu Bug Day on Tuesday!

July 14, 2008

This Tuesday we will be continuing last week’s work of transitioning KDE3 bug reports to KDE4. The Hug Day will be held all day Tuesday, July 15th 2008 in #ubuntu-bugs please join and help!

Last week we were able to close and otherwise triage dozens of bug reports, thanks to the work of JontheEchidna, txwikinger, apachelogger, and others. Here’s the progress in open bug reports in kdebase over the last week:

Open bugs in kdebase for the past week

Open bugs in kdebase for the past week

About a quarter of the remaining bugs are already triaged and/or reported upstream, or waiting on information from the reporter. It’ll be very important to get a good chunk of the remaining 300 reported upstream to

My 5 today: #243602 (kdebase-workspace),#243419 (kdebase-workspace), #243616 (meta-kde), #243416 (kdebase-workspace), #243421 (kdebase-workspace)
Do 5 a day – every day!


Kubuntu Bug Day Tomorrow!

July 7, 2008

Kubuntu Hug Days are back! Tomorrow, Tuesday, July 8th, 2008 we will be holding a Hug for a Bug Day to work on transitioning old KDE3 bug reports to KDE4.

Kubuntu Intrepid will bring major changes with KDE 4.1, fixing a lot of bugs or making them irrelevant. We need help sorting out which bugs can now be closed, which still need to be fixed in Intrepid, and which bugs are really important and need to be fixed in Hardy/KDE3. Join us in #ubuntu-bugs to help out and ask questions!

Amarok Hug Day is done

March 13, 2008

…and not because the day is over, but because it’s all green!
“New” bugs in Amarok:
amarok hugday new bugs
This is what a little teamwork and a couple dedicated people can do!

13:53 < Nightrose> yuriy: ;-) - skype session ftw
13:54 < Nightrose> and teamwork ftw

Just so the statistics don’t lie too much (we didn’t actually fix all those bugs) here is the graph for bugs in incomplete status:
amarok hugday incomplete bugs
Thanks to Parthan, santiago-ve, jjesse, and especially to apachelogger and Nightrose for participating. Hope to see some more new faces || screennames next week.

5-a-Day and Hug Days

February 21, 2008

5-a-Day and Hug Days*

Some updates to my previous post. Pedro tells me there are two Hug for a Bug days a week now:

  • Tuesdays for some category that applies to all of Ubuntu, such as this Tuesday’s day for printing bugs.
  • Thursdays for desktop bugs. This will now include a separate page for KDE bugs. So Kubuntu users: every Thursday come to #ubuntu-bugs to collaborate on improving bug reports for a Kubuntu Desktop package. It’s not too late to join in today to work on powermanager bugs!

So what’s this Hug Day thing I’m rambling on about anyway?
There are thousands of bug (problem) reports filed for (K)ubuntu in Launchpad. Far too many for the small group of developers to handle. People are needed to look through them, make sure everyone reporting a problem gets a response and make sure the reports are useful for developers. You don’t need to be a developer to participate!
This task can be much more efficient if done in an organized manner. That is what the BugSquad is for. Hug for a Bug days are a chance for you and the bug squad to work together, on one day, concentrating on one component, so you can collaborate and ask questions, and at the end of the day have a noticeable contribution to the quality of the set of bug reports, and thus to the quality of Kubuntu. For example, today the bug squad managed to get the 200 or so untouched Gnome Power Manager reports down to less than 30! Oh and, of course, if you work on a bug, you get a [virtual] hug! (This idea can be improved upon by getting a partner to work with you next to you)
Hugs to the bug squad for the great work today!

Of course, Tuesdays and Thursdays aren’t the only time to work on bugs. That’s what the new 5-a-Day initiative is all about. Just like an apple a day will do for you, helping with 5 bugs a day will keep Kubuntu healthy. And you can show off a nice little signature with your contributions, like so:

My 5 today: #177504 (kde-guidance), #96290 (kde-guidance), #174574 (kde-guidance), #79225 (kde-guidance)
Do 5 a day – every day!

(OK, for those counting, I need to do a little more work today.)

In other news, the Massachusetts LoCo Team will be hosting an InstallFest this Saturday at MIT and I will be showing off KDE 4.0.

*Planet seems to be hungry for wordpress blog titles, so for now I’m going to add the titles to the top of the posts.

Getting Kubuntu and other derivatives in on the QA initiatives

February 20, 2008

Hug Days have been frequent lately (8 already this year!). However, instead of the previous general Hug Days, these usually come with a specialty. Some particular package or area is picked to be looked at for the day. This is a great idea and I think it should be much more effective than attacking bugs at random. However, often the category ends up being Gnome specific (5 of the aforementioned 8 have been). No problem with that, but derivatives should participate in these types of events as well. I’ve gotten the impression that while there are people doing hard QA work on their own, or when someone asks to test something, these organized events are often ignored by Kubuntu people (please correct me if you’ve been participating!) (how about Xubuntu and others?) If the gnome testers are spending a day looking through desktop bugs, then KDE/xfce/etc users/testers can spend their day looking at packages related to their respective desktop.

What’s missing are the resources that the bug squad guys and other teams have set up and set up for each hug day to help manage and improve the bug reports. Namely:

  • A list of bugs to be worked on for the Hug Day. Here’s the one for Gnome Power Manager for Hug Day on Feb. 21 (that’s today in some time zones!). Here’s an analogous page for KDE Guidance Power Manager so this time Kubuntu folks can participate. I don’t know if other derivatives use a different power applet, but if so, then it would be appropriate to make a similar page for it for this Hug Day. And so on for future bug hunting events.
  • Debugging procedures. There are pages there for many parts of GNOME on how to improve bug reports and none for KDE or other desktops (if you know of some pages and they just aren’t linked there (or anywhere) please add them!). This certainly needs some work to make bug management effective. To start building up the resources, maybe next time you work on a bug, add a wiki page for that component to tell others what sort of information was required. Combined with 5-a-Day, that should get some decent resources up pretty fast to make the process more efficient in the future.

That’s just a start to some more organized QA for Kubuntu, which I think would help a lot in getting it as polished as Ubuntu is.