Difference between revisions of "BugSquad"

Latest revision as of 16: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}}
+[[Category:BugSquad]]
+[[Category:Team]]
+</noinclude>
+== 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]].
-{{TeamHeader|TestingTeam}}
+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.
-=Testing Team=
+The squad is modeled on the GNOME BugSquad: https://webstats.gnome.org/Bugsquad/
-We are about to start a project to actively recruit volunteer testers for Sugar and Sugar Activities.  The vision is to have thousands of volunteers, world-wide, working in different languages and on different hardware platforms to "crowd-source" testing.
+== How bugs are tracked ==
-Our first step will be to recruit high school teachers to engage students interested in community service and technology.
+* 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.
-==Who is Working on this project?==
+== Upstream bugs ==
-* Caroline Meeks - Solution Grove volunteer
-* Mel Chua - OLPC QA
-* Olin College Curriculum Team - Sandra Lam
-==What is our plan?==
+When you find a bug in a package we do not directly maintain, please report it [[BugSquad/Upstreaming_bugs|upstream]]
-# Recruit high school teachers with interested students
+== How to join the squad ==
-# Create a system for them to test and record bugs
+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.
-# Create curriculum to help teachers get them started and that align with curriculum standards
-==Secondary Goals==
+== Subpages ==
-# Help publicity for G1G1
+{{Special:PrefixIndex/BugSquad/}}
-# Get experience creating and sharing standards based curriculum
+{{Special:PrefixIndex/Testing}}
-#* Potentially work with Curriki to distribute the curriculum
-= About =
-The Testing team is the Quality Assurance (QA) team for Sugar. The team keeps track of current bugs in the sugar software and try to make sure that bugs are triaged correctly. Furthermore the squad does coordinate the testing efforts. 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 =
-We use [http://trac.edgewall.org/ trac] to keep track of bugs in the Sugar software. Sugar is a component of the trac instance installed at [http://dev.laptop.org dev.laptop.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.
-[[Category:TestingTeam]]