Changes

</noinclude>

</noinclude>

== About ==

== About ==

The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and trys 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. See [[BugSquad/Testing|testing]].

The Sugar Labs BugSquad keeps track of current bugs in the Sugar software and tries 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. See [[BugSquad/Testing|testing]].

You need only be interested in the programming process to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program.  If you have an interest in the programming and development process, you can learn a great deal from the communications of the those involved.  However, see this thread for what can happen if insufficient respect and deference is applied: http://www.mail-archive.com/devel@lists.laptop.org/msg18897.html.

You need only be interested in the programming process to be in the BugSquad; in fact it is a great way to return something to the Sugar community if you cannot program.  If you have an interest in the programming and development process, you can learn a great deal from the communications of those involved.  However, see this thread for what can happen if insufficient respect and deference is applied: http://www.mail-archive.com/devel@lists.laptop.org/msg18897.html.

The squad is modeled on the gnome BugSquad: http://developer.gnome.org/projects/bugsquad/

The squad is modeled on the gnome BugSquad: https://webstats.gnome.org/Bugsquad/

== How bugs are tracked ==

== How bugs are tracked ==