Difference between revisions of "BugSquad"
Jump to navigation
Jump to search
(→About) |
(→About) |
||
| Line 4: | Line 4: | ||
= About = | = About = | ||
| − | The Sugar Labs BugSquad | + | The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and try to make sure that bugs are triaged and handled correctly. The team does not do testing itself. This is done by the downstream projects shipping Sugar. |
You do not need any programming knowledge to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program. | You do not need any programming knowledge to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program. | ||
Revision as of 12:12, 16 December 2008
About
The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and try to make sure that bugs are triaged and handled correctly. The team does not do testing itself. This is done by the downstream projects shipping Sugar.
You do not need any programming knowledge to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program.
The squad is modeled on the gnome BugSquad: http://developer.gnome.org/projects/bugsquad/
How bugs are tracked
- We use trac to keep track of bugs in the Sugar software. The Sugar Labs trac instance can be found at dev.sugarlabs.org.
How to join the squad
As mentioned above, virtually anyone can be helpful. Best way to get started is by reading the TestingTeam/TriageGuide and to join us at #sugar on irc.freenode.net.