Difference between revisions of "BugSquad"

Latest revision as of 15:21, 14 May 2016

NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

No longer needed, just use Github issue tracker and let the repo Watchers handle things

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 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 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 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: https://webstats.gnome.org/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.
Other Linux distributions where Sugar runs have their own upstream bug tracking systems.

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 | 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>
+{{Obsolete|No longer needed, just use Github issue tracker and let the repo Watchers handle things}}
+<noinclude>{{TeamHeader|BugSquad}}
-{{TeamHeader|BugSquad}}
+[[Category:BugSquad]]
+[[Category:Team]]
-= About =
+</noinclude>
-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.
+== About ==
+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]].
-The squad is modelled on the gnome bugsquad: http://developer.gnome.org/projects/bugsquad/
-= How bugs are tracked =
-We use [http://trac.edgewall.org/ trac] to keep track of bugs in the Sugar software. Sugar is an component of the trac instance installed at [http://dev.laptop.org laptop.org]. To see the open tickets for Sugar you can use a query similar to that [http://dev.laptop.org/query?status=assigned&status=new&status=reopened&group=component&component=sugar&order=priority one].
-== Add a new ticket ==
-Here is a link to the page for opening a [http://dev.laptop.org/newticket new ticket]. (Note: you need to be logged in to the Trac system to post a ticket).
-= How to join the squad =
-As mentioned above virtually anyone can be helpful. Best is to start reading the [TriageGuide]
-== Testing Sugar ==
-see [[BugSquad/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 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.
-== Working with Distributions ==
+The squad is modeled on the GNOME BugSquad: https://webstats.gnome.org/Bugsquad/
-Good Communication with downstream distributions is essential for receiving bug reports and patches from outside developers.
-see [[BugSquad/DownStream]]
+== How bugs are tracked ==
-== Working with Application Developers ==
+* 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.
+* Other Linux distributions where Sugar runs have their own [[BugSquad/Upstreaming_bugs|upstream]] bug tracking systems.
-== Triaging Bug Reports ==
+== Upstream bugs ==
-see [[BugSquad/Triage]]
-== Managing the Bug Database ==
+When you find a bug in a package we do not directly maintain, please report it [[BugSquad/Upstreaming_bugs|upstream]]
-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.
+== 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 ==
+{{Special:PrefixIndex/BugSquad/}}
-[[Category:BugSquad]]
+{{Special:PrefixIndex/Testing}}