Difference between revisions of "Contribute/Bugsquad"

Jump to: navigation, search
Line 3: Line 3:
  
 
==How to help==
 
==How to help==
Read the [[Bugsquad/Triage guide|triage guide]] and join us for one of our [[Bugsquad/Bug weekends|bug weekends]]. We meet in IRC in channel #kde-bugs on irc.freenode.org. You can get started have your questions answered there. Even outside of weekends someone in IRC will usually be able to help you.
+
Read the [[/Triage guide|triage guide]] and join us for one of our [[/Bug weekends|bug weekends]]. We meet in IRC in channel #kde-bugs on irc.freenode.org. You can get started have your questions answered there. Even outside of weekends someone in IRC will usually be able to help you.
  
 
==Bugs to be done==
 
==Bugs to be done==
A temporary place we will use for bugs that need additional attention is the [[Bugsquad/Bugs to be done|Bugs to be done]] page.
+
A temporary place we will use for bugs that need additional attention is the [[/Bugs to be done|Bugs to be done]] page.
  
 
==External links==
 
==External links==
 
*[http://bugs.kde.org/ The KDE Bugzilla installation]
 
*[http://bugs.kde.org/ The KDE Bugzilla installation]

Revision as of 20:01, 13 September 2006

The Bugsquad tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.

How to help

Read the triage guide and join us for one of our bug weekends. We meet in IRC in channel #kde-bugs on irc.freenode.org. You can get started have your questions answered there. Even outside of weekends someone in IRC will usually be able to help you.

Bugs to be done

A temporary place we will use for bugs that need additional attention is the Bugs to be done page.

External links


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal