AdoptionTeam

Differences between revisions 1 and 2
Revision 1 as of 2010-01-06 21:11:51
Size: 325
Editor: ck752853-a
Comment:
Revision 2 as of 2010-01-11 16:08:27
Size: 1511
Editor: ck752853-a
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
TBD, see [[BugSquad/AdoptPackage/Nautilus]] for an example. ||<<TableOfContents>>||

== Team structure ==
The team as a whole is responsible for managing the bugs of the chosen package. Within the team the roles are divided in several tasks.

=== Subtasks ===
 * '''New bugs''': Triage new bugs, with the exception of forwarding upstream
 * '''Confirmed bugs''': Get bugs marked as 'Confirmed' to the 'Triaged' status
 * '''Forwarding upstream''': Report or link sufficiently triaged bugs upstream, and cooperate
 * '''Old bugs''': Go through old bug reports and verify them

Everyone whose task is not 'Forwarding upstream' can open an empty upstream task for the bug, and should when they deem it ready for it. That would allow other members to search for bugs ready for forwarding upstream.

This division is not mandatory. Everyone, team members and non-team members alike, can still help with any stage of the triaging process if they wish. Its goal is to make people work faster and more efficiently because they don't have to regularly switch to environment.

=== Accountability ===
Once every month(??) the team adds an status overview to the wiki with a graph showing the number of bugs in each stage. The progress of any goals is documented here as well.
----
CategoryBugSquad

An AdoptionTeam is a group of people who committed themselves to triaging the bugs of one (large) source package. This page defines the default structure of such a group. Please keep in mind that this was designed with medium size source packages in mind.

== Team structure == The team as a whole is responsible for managing the bugs of the chosen package. Within the team the roles are divided in several tasks.

Subtasks

  • New bugs: Triage new bugs, with the exception of forwarding upstream

  • Confirmed bugs: Get bugs marked as 'Confirmed' to the 'Triaged' status

  • Forwarding upstream: Report or link sufficiently triaged bugs upstream, and cooperate

  • Old bugs: Go through old bug reports and verify them

Everyone whose task is not 'Forwarding upstream' can open an empty upstream task for the bug, and should when they deem it ready for it. That would allow other members to search for bugs ready for forwarding upstream.

This division is not mandatory. Everyone, team members and non-team members alike, can still help with any stage of the triaging process if they wish. Its goal is to make people work faster and more efficiently because they don't have to regularly switch to environment.

Accountability

Once every month(??) the team adds an status overview to the wiki with a graph showing the number of bugs in each stage. The progress of any goals is documented here as well.


CategoryBugSquad

BugSquad/AdoptionTeam (last edited 2010-02-05 21:14:41 by ck752853-a)