3,267
edits
Changes
Jump to navigation
Jump to search
Line 14:
Line 14: − + − + − + + + Line 28:
Line 30: + + +
BugSquad/Meetings/Minutes/2008-12-17 (view source)
Revision as of 15:21, 17 December 2008
, 15:21, 17 December 2008no edit summary
* Meetings: when/if
* Meetings: when/if
** triage meetings?
** 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
* Sprints: when/if
** maybe coordinated with downstream testing sprints?
** after releases
* Do we need a dedicated mailing list?
* Do we need a dedicated mailing list?
** what would be the emails that go to that 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
* Create a list of concrete tasks we expect the BugSquad to do regularly
** Who is responsible for setting priorities and milestones?
** Who is responsible for setting priorities and milestones?
** What needs to be happen to mark a ticket as fixed?
** What needs to be happen to mark a ticket as fixed?
* Action items:
** #ACTION: marcopg to look at the upstream/downstream interaction fedora+gnome