1,157
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + Line 8:
Line 8: − + + + + − * Meetings: when/if+ − o triage meetings? + + − * Sprints: when/if+ − o maybe coordinated with downstream testing sprints? + + − * Do we need a dedicated mailing list?+ − o what would be the emails that go to that list? + + + + − * Create a list of concrete tasks we expect the BugSquad to do regularly+ − o How can we best help the poor developers? + + + + + + + + + + + + + + − * Triage Policy:+ − o Who is responsible for setting priorities and milestones?+ − o What needs to be happen to mark a ticket as fixed?+ + +
BugSquad/Meetings/Minutes/2008-12-17 (view source)
Revision as of 20:16, 24 February 2010
, 20:16, 24 February 2010moved Walter is a wanker 7/Meetings/Minutes/2008-12-17 to BugSquad/Meetings/Minutes/2008-12-17 over redirect: revert
* Agenda at http://sugarlabs.org/go/BugSquad/Meetings/Agendas/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
* Logs: http://shell.sugarlabs.org/~erikos/bugsquad_17_12_2008.log
* What is needed in trac to start triaging?
* What is needed in trac to start triaging?
** sucrose components, milestones, action needed field?
** 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)
** at #sugar-meeting
* Sprints: when/if
** after releases
** at #sugar-meeting
* Do we need a dedicated mailing list?
** No, we mostly have announcements and use tags for cases like: "I was triaging bug #567 but didn't know what to do?"
** sugar-devel - [bugsquad] and [bugsquad][announce]
** wiki note: "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."
** irc questions at #sugar
* Create a list of concrete tasks we expect the BugSquad to do regularly
** solicit distributions for testing of new releases
** maintain the BugSquad wiki pages (especially with policies like "we use #sugar for discussion, tag your sugar-devel posts this way")
** add components, tags, milestones
** triage tickets
** provide feedback on how to improve bug advocacy on a ticket, when requested. ("How could I have written this bug report better / which developers should I ping on it"?)
* Triage Policy:
** Who is responsible for setting priorities and milestones?
*** the bug gets in
*** bug squad make the bug nice (a well-written bug report, a suggestion on the next step to push it to developers for fixing - who to talk to, etc.), assign to maintainer
*** maintainer assign a milestone
*** the dev does fix it
** What needs to be happen to mark a ticket as fixed?
*** not fully discussed the policy
* Action items:
** #ACTION: marcopg to look at the upstream/downstream interaction fedora+GNOME
** #ACTION: mungwell to look at the upstream/downstream interaction ubuntu+GNOME (launchpad)
** #ACTION: erikos clean up wiki with today's info
** #ACTION: erikos work on trac with marcopg