Category Archives: Common

Bug Triaging Guest Blog: The wandering bug triager was here

I was contacted by Buovjaga from the LibreOffice QA team to spread the word about the current bug triaging efforts going on.

Therefore now a short guest block about that ;=)

Thanks to Buovjaga for trying to get some public interest in this important aspect of open source work: handling our flood of bugs!


Free software needs more contributors from the non-coding user community. The problem is that there is no scientifically proven method for attracting them.

After dealing with thousands of LibreOffice bug reports and simultaneously trying to recruit more testers through various cunning plans, I realized the topic of free software quality assurance needs to become more prominent. I came up with the idea for a publicity stunt where I camp out at different bug trackers while telling the world about it. I chose KDE and Kate for my first month of triaging.

Bug triagers act as guardians of the bug tracker and save the developers from a lot of wasted time. If the number of unconfirmed reports in a project is not close to zero, it needs more triagers.

There were about 120 reports I deemed suitable for testing. I skipped crash debugging, testing of advanced features and only focused on the basic stuff. My take on the stats is that there is currently no one doing this sort of thing regularly for Kate.

To get started in triaging KDE bugs, you

– start testing unconfirmed reports and ancient confirmed ones while keeping the Bug triage guide at hand

– join #kde-bugs IRC channel after having commented on a bunch of reports and request rights to edit report details

– join the IRC channels of the products you are helping and coordinate testing with others

I believe a goal should be set for recruiting one person to deal with triaging per every actively-developed KDE product. After achieving this goal, it will quickly become apparent to each product team just how many triagers are needed in order for the work to be sustainable. However, the teams should not remain in isolation. The whole of KDE needs to become transparent. An “Everything about KDE” web dashboard would enable contributors to quickly see, which teams are in need of assistance. Tools for this are available in the Grimoire Lab suite KDE sysadmin team does not have the resources to set them up, so if you have the necessary skills and want to make this happen, please contact them on the #kde-sysadmin IRC channel.

If you want to contact me, you can find me on the #libreoffice-qa channel @ Freenode network, nickname: buovjaga.


What happened to Kate in Randa?

This years topic for the Randa meeting, was multi-platform end-user application development. That was a golden opportunity to work on the Windows and Mac versions.

One thing that happened was that the icon.rcc file generation is moved to the breeze-icons repository in stead of doing it separately for every application. The icon.rcc file loading was moved to KIconThemes so that all applications linking to it don’t have to invent the wheel again. This would not have been so easy if we hadn’t been at the same place discussing things face to face.

A more noticeable thing is that Kate now does not need a DBus server on Windows and Apple any more. Both Kate and KDevelop now use QtSingleApplication to open all documents in one window.

The search plugin also got a face-lift. Hopefully the new layout will be a bit more useful than the previous 🙂

A Randa development release of Kate on Windows was also done. Download the installer from here.

To be able to continue with similar activities we need your help.