BMO

From MozillaWiki
Jump to: navigation, search

This is the main public page for all things related to https://bugzilla.mozilla.org, aka BMO, Mozilla's customized version of Bugzilla.

BMO is a core piece of infrastructure at Mozilla. It is used to track not only bugs and feature requests but also many other tasks across various teams.

The BMO source is a slightly modified fork of Bugzilla with many custom extensions. It is currently based on Bugzilla 4.2 but with many features backported from 4.4 and master. All the BMO devs are also involved in the Bugzilla project, and we contribute features and fixes upstream where they are generally applicable, that is, not too specific to Mozilla's particular needs.

Updates are usually deployed on a weekly basis and are listed on the Recent Changes page.

Contributors/Maintainers

  • dkl: Dave Lawrence (Owner/Engineer)
  • glob: Byron Jones (Owner/Engineer)
  • dylan: Dylan Hardison (Engineer)
  • mcote: Mark Côté (Manager)
  • justdave: Dave Miller (Admin)
  • gerv: Gervase Markham (Governator)
  • lizzard: Liz Henry (Bugmaster)

New Users

Getting used to Bugzilla can be a bit daunting. We have a short introductory video available that is as gentle as possible. Also see the MDN article, What to do and what not to do in Bugzilla, which also contains instructions on getting elevated privileges.

User Guide

We're putting together a user guide with helpful information on various aspects of Bugzilla. New and experienced users alike should benefit from it. There's a lot to go through, so please feel free to contribute!

Third-Party Applications

Lots and lots of web apps and general tools have been written to interface with BMO. We have started cataloguing them. If you're looking for different ways to interface with BMO, check it out; similarly, if you are thinking about writing an app, check the catalogue to see if something similar exists that you could use, contribute to, or fork before setting out on your own.

There's one in particular that is particularly important: MozReview, Mozilla's new and growing code-review tool.

More Information about BMO

Our discussion forum is mozilla.tools.bmo [mailing list] [Google Group] [USENET].

We also have answers to Frequently Asked Questions and a slightly-but-not-too-out-of-date hardware diagram.

If you're building an application or tool that interfaces with BMO, you may be interested in the following:

Looking for another way to access Bugzilla's raw data? Try the ElasticSearch cluster.

Contributing to BMO

If you'd like to help out with BMO specifically (as opposed to the general upstream Bugzilla project), you can find us in #bmo on irc.mozilla.org. If you plan on contributing patches, see the documentation on hacking BMO. You can file bugs under the bugzilla.mozilla.org product. Don't file them under the Bugzilla product unless you are sure it's a bug in the general Bugzilla product. In particular, all administrative changes should be filed under bugzilla.mozilla.org (see below for more).

The BMO team meets every Tuesday at 11:30 PM EST/EDT in the A-Team Vidyo Room (8416), dial-in extension 98416. We're open to all! You can also see (generally, quite brief) minutes of past meetings.

Policies and Procedures

Code updates are normally deployed to bugzilla.mozilla.org late Monday/early Tuesday, US/Pacific time, at no specific time, if changes need to be pushed out. Security fixes or other fatal type errors will always go out as soon as possible.

Administrative Procedures

If you need changes to BMO's configuration to support your team, project, etc., please consult these pages before filing bugs.

Other processes for BMO developers and admins:

Current Projects

This table lists the bugs representing the current quarterly goals (and, near the end of the quarter, sometimes next quarter's goals). Those that were set at the beginning of the quarter are tagged with the keyword "bmo-goal". The BMO team also regularly gets requests for high-priority work items throughout the quarter; those that will take more than a day or two in total, thus potentially jeopardizing other goals, are included below, tagged with "bmo-big". The daily smaller tasks are also generally tracked in Bugzilla but not represented in the table below.

P1 indicates a critical project. P2 indicates an important but deferrable item. P3 is as P2 but more deferrable. Note that all items are important, and it is presumed that lower-priority items will increase in priority over time as high-priority tasks are completed, i.e., we don't plan to defer any of these tasks indefinitely.

Goals

ID Priority Summary Status Resolution Assigned to
1051056 -- The REST API needs to be versioned so that new changes can be made that do not break compatibility RESOLVED FIXED David Lawrence [:dkl] (dkl)
1118365 P1 Write extension to use GitHub for Authentication RESOLVED FIXED Dylan William Hardison [:dylan] (dylan)
1144468 P1 Bugzilla Auth Delegation via API Keys RESOLVED FIXED Dylan William Hardison [:dylan] (dylan)
1144482 -- Migrate CI testing from Travis CI to Taskcluster NEW David Lawrence [:dkl] (dkl)
1144485 P1 Adapt upstream Selenium test suite to BMO NEW David Lawrence [:dkl] (dkl)
1150541 -- [tracking] feature parity between classic show-bug and the bug-modal view NEW Byron Jones ‹:glob› (glob)
1163761 P1 Allow MozReview to skip user consent screen for Authentication Delegation NEW Dylan William Hardison [:dylan] (dylan)

7 Total; 4 Open (57.14%); 3 Resolved (42.86%); 0 Verified (0%);

High-Priority

ID Priority Summary Status Resolution Assigned to
44393 P2 develop an extension that provides comment-only inbound email support ASSIGNED Byron Jones ‹:glob› (glob)
956390 P3 Add suggested reviewers capability to the ui review flag ASSIGNED David Lawrence [:dkl] (dkl)

2 Total; 2 Open (100%); 0 Resolved (0%); 0 Verified (0%);

Further documentation about goals above and other projects follows:

  • User Roles
    • Generate different user roles based on what tasks a user is trying to complete when using the BMO system.

Past Projects

Some of these will have on-going maintenance and improvements, but the initial deployment has been accomplished. Others have been abandoned or rejected due to various factors, noted below.