|Thanks to all who took part on 6th April. The date of the next BugDay will be decided soon.|
What is BugSquad?
The BugSquad keeps track of bugs in KDE software and makes sure that bugs are verified, and helps developers notice valid bugs.
You do not need any programming knowledge to be in the Bugsquad, and it is a great way to give practical support to the KDE community if you are just starting out (or are still relatively early) along the Programming Learning Curve (PLC).
The date for the next Bug Day has not yet been decided. However, if you want to start triaging bugs now, you can go to the bug-day page.
The results of all past bug days can be found here.
How to help
Read the guide and join us for one of our bug days. We meet on IRC in channel #kde-bugs on irc.freenode.org. You can easily get started by having your questions answered there. Someone in IRC will usually be able to help you. Although we do sleep sometimes!
A summary of the BugSquad guide is provided below to give you a quick idea of how you can help:
- Confirming bugs. Bugs with the UNCONFIRMED status should get the NEW status once someone else is able to reproduce the bug reliably.
- Finding bug duplicates. Many bugs entered into Bugzilla are duplicates of other bugs. Sometimes it's hard to recognize these as duplicates but multiple people checking can make the duplicates bubble to the top of the pile. The following remarks may help you identifying them:
- Using the Similar Bugs link to look if there are duplicates.
- In the case of crashes, use the link below the comment field to look for crash reports with the same backtrace. The backtrace must be in the body of the report in order to look for similar reports. This tool does not look in attachments with backtraces.
- Close bugs which have insufficient information and which have been open for a long time (e.g. reporter does not respond to a need-more-info request). Usually a timeout of one month or more is considered to be an "information timeout".
- Categorize bugs into the right components. Many bug reports can be further categorized into components. For example, Konqueror reports can be assigned to KHTML and kfm components.
- Labeling bugs which contain testcases as such in the title. Ideally, testcases contain the minimal amount of code (HTML, scripts, C++ etc.) necessary to reproduce a bug.
- Writing testcases. Very useful and saves developers' time.
The sheer number of open bugs can be overwhelming at the start. Here are some hints on getting started more smoothly:
- Look at a single product at a time. For large applications (like Konqueror), you may want to further limit your search to a particular component.
- Don't try to find duplicates early on. Finding duplicates is hard until you have become familiar with the bugs in a component. Start out with verifying UNCONFIRMED bugs as described above. That's valuable work, and a great way to familiarize yourself with the bug database.
- Avoid very old bugs with many comments, and also bugs with many votes. This may seem counter-intuitive, but in most cases these bugs are hard, have gotten a lot of attention, and are probably on a developer's TODO list already. If it is from an older version of KDE, and there are no recent comments, verify them, make a notation, and move on.
- Don't be afraid to ask the reporter for more info. It's something you can even do without Bugzilla permissions. And reporters will generally prefer being asked one question too many, instead of their report never being dealt with. Just remember to be polite. Ask yourself how you would feel if you got the message you are thinking about sending to a user.
- Look through the rest of our documentation for more information!
How to create useful crash reports - This article helps users to prepare their KDE packages such they can create detailed backtraces.