Auto-tools/Projects/Bugmaster 2013Q3: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
Line 4: Line 4:
Create a contribution pipeline for 30 incoming bugmasters and track them through each stage of involvement in order to get 1 to the state where they regularly do triage.
Create a contribution pipeline for 30 incoming bugmasters and track them through each stage of involvement in order to get 1 to the state where they regularly do triage.


* {OK|Code and Release an addon for triage} to give out task list and track participation
* {{ok|Code and Release an addon for triage}} to give out task list and track participation
* integrate with the SUMO folks and help them progress along the spectrum of involvement
* integrate with the SUMO folks and help them progress along the spectrum of involvement
* give out untriaged bug list in each response to inquiry emails and ask for comments on the bugs.  
* give out untriaged bug list in each response to inquiry emails and ask for comments on the bugs.  
* {{OK|Wire in specific 5 different bugzilla actions}} to the training missions on openhatch  (am using trainingmontage instead)
* {{ok|Wire in specific 5 different bugzilla actions}} to the training missions on openhatch  (am using trainingmontage instead)
* {{OK|improve user profiles}} in BMO  (About to launch on Saturday 8/24)
* {{ok|improve user profiles}} in BMO  (About to launch on Saturday 8/24)
* draw/outline and update a new contributor roadmap (with mhoye)  
* draw/outline and update a new contributor roadmap (with mhoye)  
* help the teams working on tools with identifying the use cases and problems we most need to solve (duplicate detection, etc) (Met with Bram)
* help the teams working on tools with identifying the use cases and problems we most need to solve (duplicate detection, etc) (Met with Bram)

Latest revision as of 18:43, 22 August 2013

Q3 goals:


Create a contribution pipeline for 30 incoming bugmasters and track them through each stage of involvement in order to get 1 to the state where they regularly do triage.

  • [ON TRACK] Code and Release an addon for triage to give out task list and track participation
  • integrate with the SUMO folks and help them progress along the spectrum of involvement
  • give out untriaged bug list in each response to inquiry emails and ask for comments on the bugs.
  • [ON TRACK] Wire in specific 5 different bugzilla actions to the training missions on openhatch (am using trainingmontage instead)
  • [ON TRACK] improve user profiles in BMO (About to launch on Saturday 8/24)
  • draw/outline and update a new contributor roadmap (with mhoye)
  • help the teams working on tools with identifying the use cases and problems we most need to solve (duplicate detection, etc) (Met with Bram)
  • host more bug days and report on outcome. Planned: SUMO, Good First Bug
  • host more workshops on bugzilla and triage.
  • make bugmaster/bugzilla swag to give out at events and send to new contributors.


Improve Bugzilla Help pages.