Bugmasters/Meetings/2013/Feb7

Bugmasters meeting

Thursday, February 7, 2013 9:30am PST

Attendees: lizzard, glob, ctalbert, bsmedberg, tyler downer, mhoye, ioana, kyle,

Agenda

Bugmaster Status report!

• Moving towards a plan for a bugmaster community. Dev, QA, Support, Advocacy, bug reporters, tool builders
• Bugmaster landing page https://wiki.mozilla.org/Bugmasters
• Bugmastering guidelines page https://wiki.mozilla.org/Bugmasters/Guide
• Focus for now: bring people in to triage early in bug life cycle.

- idea: Make first-time bugzilla users triage their own bugs. - as in, if it's a duplicate, the new user triages that as such, not a dev. - Verify that users can mark their own bugs, and comment on bugs without reopening them. (verified, bug reporters are able to edit all fields, including marking a bug as a duplicate. comments won't reopen a bug) the only restriction is new users can't mark a bug as FIXED (Killer, thanks! - mhoye)

• Gave a talk at She's Geeky unconference, 10 attendees, 4 or so tried triaging, 1 is submitting a patch. Got good feedback for future "come be a bugmaster" talks.

Coming soon!

• Adding context dependent links into bugzilla.mozilla.org (lead to wiki for triage, build questions)
  • (info) links by product and component in a hidden div, pulls text from show_components.cgi, Liz will add links to MDN or WMO for each component
  • screenshot: http://www.flickr.com/photos/lizhenry/8451504743
• The awesomely great bugzilla dashboard. Try it!
  • https://bugzilla-dev.allizom.org
    • ping glob or dkl for an account (email is disabled)
  • screenshots: http://www.flickr.com/photos/lizhenry/sets/72157632708019232/show/
  • Dashboard by user
  • Product dashboard
  • report bugs in it under bugzilla.mozilla.org::User Interface
    • these reports will be live when bmo is upgraded to 4.2 (eta, end of month)
• Status of the READY status. Ready or not? (glob: not; it's a "breaking" change, maybe worth discussing alternatives)

Stuff that needs doing

• Develop triage guidelines for specific actions and modules.
• Describe various common bugmastering tasks, with good examples.
• Tell more stories about triaging particular bugs.
  • A story: http://bookmaniac.org/walking-through-early-bug-triage/
• Conversion points chart - refine it. https://wiki.mozilla.org/Contribute/Conversion_points#Other_project_areas
• Figure out and mark bugs for bugmastering to feed into Bugs Ahoy. (maybe)
• Identify bugs likely to be easier to triage. Websites. Also closeme, dupeme, easytriage tags
• What else would you add to this?

Discussion

Write more thoughts and questions here as you think of them!

• bsmedberg's bug-triage app: http://benjamin.smedbergs.us/bugbudgeter/
• https://bugzilla.mozilla.org/page.cgi?id=triage_reports.html is a thing too, and i can extend this if required (to cover things which aren't possible with bugzilla's search)
• What would be involved in getting an updated snapshot of Bugzilla data? (Jetpack team has changed our system of triaging things since mid-2012, so the dashboards aren't helpful at the moment) (glob: i can provide sanitised snapshots on request, and there's plans to automate this, --> mhoye)
• whiteboard is "tag space" and it's searchable but not the most efficient.... can you edit it without editbugs? Should we add a new tag field that you don't need editbugs to add stuff to? expanding the existing keyword field to allow arbitrary keywords would probably be a better route... not sure adding more fields to bugzilla is a net win :)
• https://globau.wordpress.com/2012/10/16/coming-attraction-comment-tagging/