BugSquad: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude> | <noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude> | ||
{{TeamHeader|BugSquad}} | |||
= About = | |||
The Sugarlabs Bugsquad is the Quality Assurance (QA) team for Sugar. The squad keeps track of current bugs in the sugar software and try to make sure that major bugs do not go unnoticed 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 Sugar community if you cannot program. | |||
= | The squad is modelled on the gnome bugsquad: http://developer.gnome.org/projects/bugsquad/ | ||
= How bugs are tracked = | |||
= How to join the squad = | |||
== Testing Sugar == | == Testing Sugar == | ||
see [[BugSquad/Testing]] | see [[BugSquad/Testing]] | ||
== Working with Distributions == | == Working with Distributions == | ||
| Line 28: | Line 30: | ||
We need help keeping our bug-tracking system organized; please help us by setting the right priorities, assigning to the appropriate milestones, finding duplicates, or verifying bugs. | We need help keeping our bug-tracking system organized; please help us by setting the right priorities, assigning to the appropriate milestones, finding duplicates, or verifying bugs. | ||
= | = Useful Resources = | ||
== Open Tickets == | == Open Tickets == | ||