… do not forget to properly setup KAboutData !

DrKonqi, the KDE crash handler dialog and report assistant, is prepared to send crash reports to our bugtracker at bugs.kde.org.

However, there are KDE based applications that are not developed by the official KDE team or that use their own bugtracker. In those cases, you need to tell DrKonqi about this custom reporting address (which could be a site or a contact email). If you don’t do so, that kind of reports are going to end up being sent to bugs.kde.org and closed as DOWNSTREAM, usually causing more trouble for the reporting user (and increasing the work of the KDE bug triagers)

There are two ways to tell KAboutData (and therefore DrKonqi) about your custom tracker:

  • On the KAboutData constructor:
    The 10th argument of the KAboutData constructor allows the developer to set a custom bug reporting address entry (URL or email), in QByteArray format
  • Using the setBugAddress function:
    Once the KAboutData object is created, and before calling KCmdLineArgs::init() (and/or before creating the KApplication object), you can call aboutData.setBugAddress("URL");

You can always check the KAboutData API

Thanks!


Before proceeding: if you don’t know why I’m here you can read https://darioandreskde.wordpress.com/2009/12/06/hello-planetkde/

As the results of my work in the KDE bug tracker I wrote my own “ultimate” guide to Bug Triaging. This document describes the usual workflow in a bug tracker, and it includes tips to handle reports. Though it is a general guide, it focuses on the KDE BugZilla installation specifics.

Hopefully this guide will help new contributors to join the KDE bug triagers group and cleanup the database.

You can find the guide at http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging

Disclaimer: the document is not perfect yet and may have grammar/spelling errors. Contributions are corrections are welcome!.
Also, if you find technical words which should be described on the Glossary, or other random topics which should be explained on the FAQ, please notify me about them.


The first BugWeek session finished one week ago and I mostly finished processing its results. (What is a BugWeek?)

There were 12 participants registered (9 of them worked on the bug reports)

The overall results are:
141 bug reports checked (~14 of 20 batches)
42 bug reports which could be considered fixed/not-reproduceable (this is an estimation, some reports are not going to be closed)

Some statistics:
Statistics
(note that the results could change as it is somewhat difficult to “label” some bug reports’ status)

I think these are nice results considering the season (new year’s eve week), and that this was the first (and unpolished) experience. From my PoV, the whole experience was great: people was interested and willing to help us, and the BugSquad stuff was willing to help the participants too.

I would like to thank to all the participants: jtamate, Rémy Greinhofer, Ingo Malchow, tampakrap, Henry Rust, Ryan J Redding, talavis, Lasse Liehu, ComputerDruid, Kolia, meloon, jaafar; to the KDE Community Forums staff which helped me a lot organizing the session and preparing the forums subsection (specially to Ingo Malchow who encouraged me to work on this initiative); and to the BugSquad team which helped me processing the results.

You can read the whole summary topic here.
We also got nice feedback from the participants of the session in the feedback topic.
Also, if you are interested into the BugWeek session workflow, you can read the session’s main article.

See you the next time :)


Happy 2010 to everyone ;D

If you didn’t read about it (or you forgot it): we are currently running the first BugWeek session to triage and reduce the amount of Plasma Desktop bug reports.

Today is the last day to signup and read the guide to properly setup your environment and user accounts, or to ask for help.
Tomorrow we will start working on the reports.

Join us!, for a bug-free 2010 :)


The poll to choose the first BugWeek‘s target has finished. The results are:

  1. Plasma Desktop
  2. Kopete
  3. Dolphin
  4. Konqueror

I have decided to use these applications (the four of them) as the targets for the next BugWeek sessions. So there won’t be a new poll before the 4th session is completed.

The first session (“zero”) will start the next week, on December 28th.
You can already access the session’s main topic on the forums, and get your questions answered in this topic.

Join us!
Happy holidays :)


The next week we are going to start the first BugWeeks session (which is going to be the pilot experience).

The public poll to choose the target of the first BugWeek is now available at http://forum.kde.org/viewtopic.php?f=148&t=84633
I have added the KDE applications that have most bug reports in our database.

If you are interested in this initiative or if you are planning to participate in this session (or in the future ones), please vote on the poll ! ;) (Note that you have to sign-in with your KDE Community Forums account).

If you want to select another application not listed, just add a comment in the poll thread and we will evaluate adding it to the next session poll.


Both the KDE Community Forums and the BugSquad Team are proud to announce the new iniciative named “BugWeeks”: a different approach to bug triaging which was born as a complement of our current BugDays.

The main objective of this proposal is to provide a more user-friendly entrance point to the bugs-related work, with a continuous feedback between the mentors and the interested users, powered by the community forums.

We encourage you to give us feedback about the initiative proposal :)

Find more information about it at the official announcement.




Follow

Get every new post delivered to your Inbox.