Difference between revisions of "BugSquad"

From Sugar Labs
Jump to: navigation, search
(How bugs are tracked: Other distros)
(How bugs are tracked: upstream)
Line 14: Line 14:
 
* 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].
 
* 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.
 
* See [[BugSquad/Bug Report]] for an introduction to bug reporting.
* Other Linux distributions where Sugar runs have their own bug tracking systems.
+
* Other Linux distributions where Sugar runs have their own [[BugSquad/Upstreaming_bugs|upstream]] bug tracking systems.
  
 
== Upstream bugs ==
 
== Upstream bugs ==

Revision as of 10:29, 26 May 2011

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

BugSquad/Bug ReportBugSquad/Bug TriageBugSquad/Contacts
BugSquad/CoordinatorBugSquad/DownStreamBugSquad/Email Bug Report
BugSquad/FAQBugSquad/Get Logs
BugSquad/Getting InvolvedBugSquad/MeetingsBugSquad/Meetings/Agendas
BugSquad/Meetings/Agendas/2008-12-10BugSquad/Meetings/Agendas/2008-12-17BugSquad/Meetings/Minutes
BugSquad/Meetings/Minutes/2008-12-10BugSquad/Meetings/Minutes/2008-12-17BugSquad/Meetings/Minutes/2009-02-12
BugSquad/MissionBugSquad/ResourcesBugSquad/Roadmap
BugSquad/Status FieldsBugSquad/SugarBotBugSquad/TODO
BugSquad/Telepathy DebuggingBugSquad/Test CasesBugSquad/Testing
BugSquad/TriageBugSquad/Triage GuideBugSquad/Triage Guide/Stock Responses
BugSquad/Triage TeamBugSquad/Upstreaming bugs
TestingTesting/BrowseTesting/Reports
Testing/Reports/ARM RPiTesting/Reports/ARM RPi/Duplicating a RPi SD CardTesting/Reports/ARM TrimSlice
Testing/Reports/Activity Matrix (A to I)Testing/Reports/Activity Matrix (J to Z)Testing/Reports/Liveusb-creator
Testing/Reports/SoaS installation variationsTesting/Reports/SoaS v10 ActivitiesTesting/Reports/Sugar-runner in Fedora 21
Testing/Reports/Sugar on a StickTesting/Reports/Sugar on a Stick PersistenceTesting/Reports/Sweets on Debian Wheezy
Testing/Reports/Sweets on GNOME Debian WheezyTesting/Reports/Sweets on Raspberry pi armhf raspbianTesting/Reports/dd installs
Testing/Reports/livecd-iso-to-disk