Posts Tagged ‘QA’

UDS Days 2-5

June 10, 2009

I never got around to more blogging during UDS, but here’s a summary of the rest.

We had a discussion with Canonical’s Rick Spencer about the role Canonical’s desktop team is or should be playing in Kubuntu and how to avoid problems we’ve had in the past.  Conclusion: communication communication communication.

Then there was a session on Wine integration and what to do when a user clicks on a windows program.  Will need to keep up for Kubuntu.

We had a session on QA in Kubuntu.  We discussed how to avoid major problems we’ve had in the last couple of cycles and how to improve our QA process in general.  There was also a separate session about l10n problems.  The interesting thing that came out of this is a plan to have a feedback plasmoid on the desktop during the development cycle so we can pick up on problems quickly.  We also decided to expand the use of the Apport bug reporting tool and crash handler in Kubuntu.  The QA team has some neat plans for this tool, some of which are already being implemented, so hopefully the overall quality of bug reports will keep improving.

We had some discussions about the default IRC client and web browser for Karmic and came up with features we’d like to see in our options.

Several of the KDE guys and I sat in on a session about the messaging applet.  It really helped us understand what the Ayatana team is going for.  Sebas then showed off lion mail, which is similar in some ways, and several productive sessions kicked off regarding how to create a messaging indicator for KDE that both follows the DX team’s vision and the KDE way of doing things.

Riddell showed off some of the social web plasma applets available and we decided to include one or two by default in Kubuntu Social from the Start.

There was a session about what we need for KDE integration from Ubuntu One.

We had a session discussing the Kubuntu web site where we mostly talked about how much we like the Xubuntu website.  We came up with some things we can improve on the site, but most importantly, DESIGNERS WANTED!

There was a session discussing creating a way to create a bootable USB stick in KDE, and work is underway.

The last session I went to was on Canonical desktop and usability team’s “Death by a Hundred Paper Cuts” project.  The project will find and try to fix a hundred seemingly trivial usability bugs each cycle.  Neat!  We won’t get the benefit of the professional user testing on the KDE side of things, at least not during the current experimental stages of the project, but maybe we can start a similar initiative?

On the social side, we went out to a bar to watch the European soccer championship game, Barcelona vs. Manchester.  Quite a time and place to be in Barcelona.  Friday night was of course karaoke — barbie girl and bohemian rhapsody KDE style, and some other umm.. good shows.

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.