Want to help improve KDE? But you can't write code? Join the KDE Bugsquad!

Last weekend I took part in the "Konqueror Bugsquad Days". We had a few handful of KDE contributors taking part, AFAIK all of them non-C++/Qt coders. Knowing nearly nothing about HTML rendering, or JavaScript and what-not, I picked to sift through all bug reports that contained the string "print".

Why do we do it at all? We want to cleanse the bug data base.

Why do we want to cleanse it? To get rid of duplicate + invalid + solved + un-verifi-able entries. To verify and improve bug descriptions if the original reporter didn't supply enough details.

Why is that nice? Because then the real developers of the respective application (here: Konqueror/KHTML) can better concentrate on *fixing* bugs. And because this is a job that can easily be done to a large part by non-coders.

If you want get in touch, join the #kde-bugs channel on Freenode. You'll find people hanging out there most of the time.

Will you take part in the next round of KDE Bugsquad attacks?