Revision as of 15:07, 9 March 2016 by Ochurlaud (talk | contribs) (Created page with "File:Bugweeks_ladybug.png ==What is BugSquad?== The '''KDE BugSquad''' keeps track of incoming bugs in KDE software, and goes through old bugs. We verify that a bug exis...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Bugweeks ladybug.png

What is BugSquad?

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.

Bug Meetings

We celebrate bug meetings 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 meeting.

Note-box-icon.png
Note
Meetings are nice, but don't hesitate to join us at #kde-bugs on irc.freenode.net at any time. 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 some of the articles below to get on your feet.


Bug Days

When these meetings are 24-hours long, we call them Bug Days. They are usually organized live through IRC — #kde-bugs on irc.freenode.net.

Note-box-icon.png
Note
There is currently no Bug Day scheduled. Why don’t you organize one yourself?


Bug Weeks

As an alternative to Bug Days, there are also meetings that take one week. The workflow is based on the KDE Community Forums. More information →


Content is available under Creative Commons License SA 4.0 unless otherwise noted.