Difference between revisions of "BugSquad"

Revision as of 10:20, 1 April 2010

Team Home · Join · Contacts · Resources · FAQ · Roadmap · To Do · Meetings

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 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.

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 bugs.sugarlabs.org.
See BugSquad/Bug Report for an introduction to bug reporting.

Upstream bugs

When you find a bug in a package we do not directly maintain, please report it upstream

How to join the squad

As mentioned above, virtually anyone can be helpful. Best way to get started is by reading the BugSquad/Triage Guide and to join us at #sugar on irc.freenode.net.

Subpages

@@ Line 1: / Line 1: @@
-<noinclude>{{GoogleTrans-en}}{{TeamHeader|BugSquad}}
+<noinclude>{{TeamHeader|BugSquad}}{{TOCright}}
+[[Category:BugSquad]]
+[[Category:Team]]
 </noinclude>
-{{TOCright}}
 == 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.
+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]].
-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.  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 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.
 The squad is modeled on the gnome BugSquad: http://developer.gnome.org/projects/bugsquad/
@@ Line 11: / Line 12: @@
 == How bugs are tracked ==
-* We use [http://trac.edgewall.org/ trac] to keep track of bugs in the Sugar software. The Sugar Labs trac instance can be found at [http://trac.sugarlabs.org trac.sugarlabs.org].
+* We use [http://trac.edgewall.org/ trac] to keep track of bugs in the Sugar software. The Sugar Labs trac instance can be found at [http://bugs.sugarlabs.org bugs.sugarlabs.org].
+* See [[BugSquad/Bug Report]] for an introduction to bug reporting.
 == Upstream bugs ==
@@ Line 24: / Line 26: @@
 {{Special:PrefixIndex/BugSquad/}}
 {{Special:PrefixIndex/Testing}}
-[[Category:BugSquad]]
-[[Category:Team]]