Changes

Line 32: Line 32:  
At this meeting we want to form the Sugarlabs Bugsquad, 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.
 
At this meeting we want to form the Sugarlabs Bugsquad, 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.
   −
The squad is modelled on the gnome bugsquad: http://developer.gnome.org/projects/bugsquad/
+
The squad is modelled on the gnome bugsquad: http://developer.gnome.org/projects/bugsquad/  
    +
More info about the sugar bugsquad can be found at [[BugSquad]]
 +
 +
===== Questions =====
 +
* do we need a special mailing list (bugsquad@sugarlabs.org)
 +
* do we need a special irc channel for the squad (#sugar-bugsquad)
 +
* do we want a tracker at sugarlabs.org to keep track of bugs in non-olpc distributions (debian, fedora ...)
    
===Thursday September 18 2008 - 14.00 (UTC) ===
 
===Thursday September 18 2008 - 14.00 (UTC) ===
3,267

edits