Bugmasters/Projects

Here are some ongoing Bugmaster projects to help manage Mozilla bugs. Each one will have bug days or events occasionally, to help its contributors communicate and work together. "Triaging" a bug can mean a lot of different things depending on context, but in general it means adding more information to a filed bug.

((Make separate pages for each project. Add a section for people to sign up on each team with a bugzilla name and link to Mozillians profile...)

Firefox UNCONFIRMED Team

Latest Untriaged Firefox bugs, UNCONFIRMED, from the last 60 days.

You may want to edit your search, limiting it to only the operating systems you can test.

• Understand the bug
  • Read the description and comments in the bug to understand the problem.
  • If you don't understand the bug
    • Comment, add need-info flag for reporter.
    • Ask for whatever additional details you need to understand.

• Check if it's a duplicate
  • Search on similar terms in Bugzilla to see if it is a duplicate of another bug.
  • (How to search)
  • (How to tell if it's a likely dup)
  • Tag it dupeme? if you're not sure, and move on.

• Check if it's a support question
  • If it's a support question (often malware, FF is slow reports)
  • Nicely let the reporter know where to look for the answer or for help.
  • Ask the reporter with a need-info flag to resolve the bug as invalid, or resolve it yourself.

• Test case, if needed
  • If this bug needs a test case and you don't have one:
  • Ask the reporter for one. That might mean simplest or reduced test case code, or a URL.
  • Or you could generate a test case and attach it.

• Replicate the bug
  • Can you replicate the bug? In the same OS?
  • If you can replicated it, and no one else has, leave a comment.
  • If you can't replicate it, and are in the same OS
  • Ask the reporter with need-info if they still see the issue
    • (Especially if it's an older bug and we're on a new version of FF now)
    • If they don't you can resolve it WORKSFORME or ask reporter to do so
    • If they still see the bug, tag it needs-replication
  • If you can't replicated it and are in a different OS
    • Comment
    • tag it needs-replication

• Safe mode, plugins off, New profile
  • In some cases (but not all) you may want to ask the bug reporter if they still see the bug in safe mode (with all plugins disabled) and with a new profile.
  • (((Explain when and when perhaps not to do this)))

• IF you can replicate the bug, and it's likely to be a Firefox bug (not a bug with a plugin, etc)
  • Comment that you replicated the bug
  • Mark it NEW
  • You can keep adding info to the bug if you think it will be useful.

Incoming Team

Bugs Filed Today. All bugs filed in the last 24 hours. Usually this is around 400 bugs, but the number fluctuates over the course of the day.

To work in this area, go through the bugs with status UNCONFIRMED.

• • Today's UNCO Bugs
  • If you can reproduce a bug, and are fairly sure it is a Mozilla bug, mark it NEW.
  • Assign the bug into a product and component, or tag it needs-component
  • Tag the bug with other triage tasks that may be needed.

Websites Team

This is for bugs that have been reported in Mozilla-run websites.

• Take a look at the Website UNCONFIRMED bugs.
• Sort on Status, ID, or another field.
• Check to see that the bug still exists.
  • If you can't reproduce it, ask the reporter, in a comment with a need-info flag, if they can reproduce it.
    • If they can't, or don't answer after a week or so, resolve the bug as WORKSFORME.
  • If you can reproduce it, mark it NEW and leave a comment to describe what you did. You may be able to find a person to cc on the bug if you look for who has resolved past, similar bugs.

• Websites bugs marked NEW can also use triaging! Here's a bugzilla query for Website NEW bugs reported within the last year.

Nightly build bug team

Hello! If you'd like to help out with bug management for Nightly builds, please email bugmaster@mozilla.com!

Every night the latest pre-release version of Firefox is made available. If you want to test against the cutting edge of Firefox, download the Nightly build and use it as your main browser. If you find any bugs, file them. (How to File a Bug).

You may also be interested in looking at the bugs others have filed, and see if you can replicate them or add any useful information. Triaging the Nightly bugs will help us catch important bugs as quickly as possible!

1. Download the Nightly build and run it.

2. Make a bugzilla account.

3. Skim over the current bugs against the Nightly release (currently, 23 build).

4. File bugs when you find them...

5. Triage through the list of Nightly bugs. So helpful!

--- replicate, comment, confirm

--- needinfo the bug reporter to get more details

--- regression testing

For example, the current released version of Firefox is 20.0. The Beta version is 21, and the Aurora version is 22. That means the Nightly build is 23. The bugs filed against that release are listed as being in the 23 branch of Firefox.

• To search later branches, go to the Advanced Search form in Bugzilla, select Firefox for the product, then under the Detailed Bug Information dropdown, scroll through the Versions listed and select the latest one. That search will bring up all bugs reported for the latest nightly build.

Mentored Bugs Team

Triage through the bugs that have "mentor=" as a whiteboard flag. Triage through bugs that have "good first bug" in the whiteboard flags.

• 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

TODO

• add queries and links to this section
• 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

This is for bug wranglers who would like to help accessibility developers and end users.

• Join #bugmasters and #accessibility

• Meta bug cleanup: this is a very easy task for beginners!
  • Look at accessibility meta bugs
  • Pick one, search for other bugs that are missing, and add them to the meta bug