The KDE BugSquad keeps track of incoming bugs in KDE software, and goes through old bugs. We verify that a bug exists, and is reproducible, and that the reporter has given enough information. When applicable, we write testcases. Our end goal is to help developers notice valid bugs quicker, and to save their time.
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 to learn programming, it is a great way to gain familiarity with the components.
We have regular days where we pick a software package and look through all the old Bugzilla bugs to see if they are still valid. Sort of a Bugzilla cleaning day.
The next Bug Day will be 10th October 2010 and it will the first KWin Bug Day: http://techbase.kde.org/Contribute/Bugsquad/BugDays/KWinDay1
The results of all past bug days can be found here.
Our team has recently launched a new iniciative named "Bug Weeks", as an evolution of the traditional BugDays. All the workflow is based on the KDE Community Forums.
You can find more information about it at its official announcement
The first bugweek was about triaging Plasma Desktop bug reports. You can find more information in the BugWeek Session 0 article. (A summary article is yet to come)
We don't just do bugs on BugDays! Don't hesitate to join us at #kde-bugs on irc.freenode.net, we have plenty for you to do. ;) Check the topic to see what we are currently working on. And if you are new, please read the "how to triage bugs" page.
Read the guide and join us for one of our bug days. We meet on IRC in the #kde-bugs channel on irc.freenode.org. You can easily get started by having your questions answered there, and having someone guide you as to general bug triaging philosophy. 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:
The sheer number of open bugs can be overwhelming at the start. Here are some hints on getting started more smoothly:
How to create useful crash reports - This article helps users to prepare their KDE packages such they can create detailed backtraces.
Basic guide about crash reports - This article is a basic/simplified version of the previous one.
How to triage System Settings bugs - Explains how System Settings works from a bug squasher's perspective.
How to triage bugs - This article gives step-by-step what you do during a Bugday, or how to start triaging on your own in our "ongoing triage" (usually for old Konqueror bugs; see #kde-bugs for the current link).
Quick introduction to Bugzilla - This article explains the basics about the bugtracking software that KDE uses: "Bugzilla". It includes the description of a bug reports fields and the workflow of most common tasks like searching into the databse.
A Bug's Life Cycle - This article describes the possible status of a bug report and when each should be used.
Preparing a testing environment - This article from the BugWeeks initiative describes how to properly configure and setup a KDE SC environment in order to test the bugs.