BugSquad/Meetings/Minutes/2008-12-17

• Agenda at http://sugarlabs.org/go/BugSquad/Meetings/Agendas/2008-12-17

• Logs: http://meeting.laptop.org/sugar-meeting.log.20081210_1206.html

• Do we agree on the mission?
  • http://sugarlabs.org/go/BugSquad/Mission (got accepted)

• What is needed in trac to start triaging?
  • add sucrose components
  • add milestones
  • base work flow on http://wiki.laptop.org/go/Trac_ticket_workflow
  • distribution field (where was the bug found)

• Meetings: when/if
  • schedule weekly triage meetings (especially to get people started, but things should be setup so that triaging happens async, because it needs to be a continuous)

• Sprints: when/if
  • after releases

• Do we need a dedicated mailing list?
  • No, we mostly have announcements and use tags if that is not the case, questions like (how do i triage bug #3)
  • sugar-devel - [bugsquad] and [bugsquad][announce]
  • "you can always triage at any time, and if you'd like to schedule your own sugar triage sprint, please do and announce it $here! if you're new and want help getting started but can't make a sprint, ask $here_2."

• Create a list of concrete tasks we expect the BugSquad to do regularly
  • solicit distributions for testing of new releases

• Triage Policy:
  • Who is responsible for setting priorities and milestones?
  • What needs to be happen to mark a ticket as fixed?

• Action items:
  • #ACTION: marcopg to look at the upstream/downstream interaction fedora+gnome