|
|
| Line 1: |
Line 1: |
| Here are some ongoing Bugmaster projects to help manage Mozilla bugs. Each one will have bug days or events, to help its contributors work together. "Triaging" a bug can mean a lot of different things depending on context. In general, it means adding more information to a filed bug. | | Here are some ongoing Bugmaster projects to help manage Mozilla bugs. Each one will have bug days or events, to help its contributors work together. "Triaging" a bug can mean a lot of different things depending on context. In general, it means adding more information to a filed bug. |
|
| |
|
|
| |
| ==Mentored Bugs Team==
| |
|
| |
| Many developers tag bugs as good first bugs, or as mentored bugs. Some are tagged with both.
| |
|
| |
| '''We are having a triage day in May 2013 to rummage through the mentored bugs!'''
| |
| * Sign up here: https://etherpad.mozilla.org/triage-mentored-bugs<br>
| |
|
| |
|
| |
| Currently, mentored bugs feed the [http://www.joshmatthews.net/bugsahoy/ Bugs Ahoy] site.
| |
| Good first bugs feed into [https://openhatch.org/search/?q=Mozilla openhatch.org]. (Out of date. Wrote to Asheesh, who is looking into it.)
| |
|
| |
| Help maintain this list for contributors who are new to Mozilla development!
| |
|
| |
| * Is the bug old and stale?
| |
| ** Should it be closed?
| |
| ** needinfo on the reporter, or mentor, or assignee?
| |
| * Is the bug current, and assigned, but the assignee hasn't touched it for a couple of weeks?
| |
| ** needinfo the assignee to ask nicely if they're still working on it or intending to
| |
| ** If the reporter hasn't touched the bug in a month, unassign it
| |
|
| |
| * Triage through bugs that have the whiteboard flag [good first bug] but NOT the mentor= flag.
| |
| ** [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=6500843&o1=casesubstring&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=good%20first%20bug&v1=mentor good first bugs query] (no mentor)
| |
|
| |
| * Triaging strategies:
| |
| ** Sort the list by component.
| |
| *** Pick a particular product and component. Talk with the bugzilla owner of that component or the module owner.
| |
| ** Sort the list by ID. It's good to check up on very old bugs with a low ID number.
| |
| ** Sort the list by last changed. For bugs that haven't been touched in weeks or months, look if they're assigned and ask the assignee, by commenting with the needinfo flag, if they're still working on it.
| |
|
| |
|
| |
| * Triage through the bugs that have "mentor=" as a whiteboard flag.
| |
|
| |
| * Triage through bugs that have "good first bug" AND "mentor" in the whiteboard flags.
| |
| ** should they have both?
| |
|
| |
| TODO:
| |
| * write up how to check on good first bugs
| |
| * write up how to choose and tag good first bugs/mentored bugs, and link
| |
|
| |
|
| ==Accessibility Triage Team== | | ==Accessibility Triage Team== |