BMO: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(164 intermediate revisions by 15 users not shown)
Line 1: Line 1:
= Bugzilla@Mozilla =
This is the main public page for all things related to https://bugzilla.mozilla.org, aka BMO, Mozilla's customized version of [http://www.bugzilla.org Bugzilla].


This is the main public page for all things related to https://bugzilla.mozilla.org (b.m.o). Here you can find information such as who is actively maintaining and contributing to b.m.o and what tasks are currently being worked on. Other information such as recent meeting minutes, and current release schedules can also be found here.
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.


== Contributors/Maintainers ==
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.


* dkl: Dave Lawrence (Engineer)
Updates are usually deployed on a weekly basis and are listed on the [[BMO/Recent_Changes|Recent Changes]] page.
* justdave: Dave Miller (Admin)
* gerv: Gervase Markham (Grease Gun)
* reed: Reed Loden (Engineer/Admin [Volunteer])


== Meeting Information ==
= B-Team =


Every Wednesday 11:00AM EST 1-650-215-1282 ext: 92, Conf# 473
The team that works on BMO is called the B-Team, because of past affiliation with the defunct Automation and Tools team (A-Team).


* [[BMO/Meetings/2011-01-05|Jan 05 2011]]
* dkl: Dave Lawrence (Owner/Engineer)
* [[BMO/Meetings/2010-12-22|Dec 22 2010]]
* glob (Manager)


== Current Projects ==
The Low-level, security, and quality tools team contributes tooling, and development:
* calixte: Calixte Denizet, (AutoNag)
* marco: Marco Castelluccio, (BugBug)


Here is a table of current projects being worked on for the near future. These are larger scale projects and not related to day to day bug fixing and features
We also also have some volunteers, that we consider to be part of the B-Team as well:
reported in individual bug reports. They will be prioritized and a schedule will be assigned based on current resources available. Click on the project description to get more detailed information.


<table style="width: 100%" class="fullwidth-table sortable" border="1">
* seban: Sebastin Santy (long-term volunteer, past GSoC student)
<tr>
* atoll: Richard Solderberg (Reviewer-at-Large, slightly borrowed from Mozilla IT)
  <th>Description</th>
* kohei: Kohei Yoshino, (UX Designer)
  <th>Goal</th>
* ''... and you can be one too!''
  <th>Priority</th>
  <th>ETA</th>
  <th>Status</th>
</tr>
<tr>
  <td>[[BMO/40Upgrade|4.0 Upgrade]]</td>
  <td>b.m.o is currently running Bugzilla version 3.6 and work is being done to upgrade to version 4.0 once the upstream community releases it. This keeps b.m.o updated with all of the recent bug fixes and well as new features available in 4.0. A schedule as well as current issues and remaining tasks will be available on the project home page.</td>
  <td>1</td>
  <td>After Firefox 4 ships</td>
  <td>IN PROGRESS</td>
</tr>
<tr>
  <td>[[BMO/REST|Native REST API]]</td>
  <td>Thanks to work done by Gervase, b.m.o has had a full featured REST API available to Bugzilla user's for some time now. Currently the REST API sits on a separate proxy between the client and the b.m.o server. Eventually we would like to see this become part of the core Bugzilla API.
  <td>4</td>
  <td>TBD</td>
  <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/CodeReview|Code Review Integration]]</td>
  <td>Developers would like to improve the current code review process by integrating either Review Board or Splinter with b.m.o so that code review can be done directly from the bug report instead of entering a separate tool.</td>
  <td>1</td>
  <td>Early Febuary</td>
  <td>IN PROGRESS</td>
</tr>
<tr>
  <td>[[BMO/Pulese|Pulse Integration]]</td>
  <td>This extension sends messages to a message broker via AMQP or STOMP
whenever an object (bug, keyword, component, etc) is created or modified.</td>
  <td>2</td>
  <td>TBD</td>
  <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/SecureBugMail|Secure BugMail]]</td>
  <td>Need a way to be able to interact with Bugzilla in a secure way so that changes made to bug reports or new bugs submitted can be guaranteed that they came from the proper person. Two possible solutions to this is the use of one time use tokens and/or GPG encryption.</td>
  <td>2</td>
  <td>Release with 4.0</td>
  <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/ComponentWatch|Component Watching]]</td>
  <td>Currently b.m.o only allows for watching for particular user accounts. Users of b.m.o would like to also be able to receive bug notifications on bugs assigned specific Bugzilla field values such as component, version, etc (https://bugzilla.mozilla.org/show_bug.cgi?id=76794).</td>
  <td>4</td>
  <td>TBD</td>
  <td>PENDING</td>
</tr>
<tr> 
  <td>[[BMO/BranchStatus|Branch Status Support]]</td>
  <td>b.m.o needs a better way to handle bug reports that are for specific branches of development and not necessarily specific release versions (https://bugzilla.mozilla.org/show_bug.cgi?id=55970).</td>
  <td>4</td>
  <td>TBD</td>
  <td>PENDING</td>
</tr>
<tr>
  <td>[[BMO/Sitemap|Sitemap Extension]]</td>
  <td>Allow various search engines to index bugs in b.m.o (https://bugzilla.mozilla.org/show_bug.cgi?id=223988)</td>
  <td>4</td>
  <td>Release post-4.0</td>
  <td>PENDING</td>
</tr>
</table>


== Other News ==
There are also some people that still have some involvement with BMO,
but their day-to-day attention is directed to other parts of Mozilla.


News related to b.m.o.
* zeid: Zeid Zabaneh (Engineer)
 
Past contributors include:
* mary: Mary Umoh (Intern, Summer 2017)
* gerv: Gervase Markham
* mcote: Mark C&ocirc;t&eacute;
* dylan: Dylan Hardison
* imadueme: Israel Madueme (Engineer)
* justdave: Dave Miller
* emceeaich: Emma Humphries, (Bugmaster)
* mhentges: Mitchell Hentges (Engineer)
 
= New Users =
 
Getting used to Bugzilla can be a bit daunting. We have a short [https://gerv.makes.org/popcorn/1bn6 introductory video] available that is as gentle as possible.  You may also be interested in the [[https://developer.mozilla.org/en-US/docs/Mozilla/Bugzilla MDN section about Bugzilla]], which contains information more suitable as an introduction to a general audience.  Of special interest is the MDN article, [https://developer.mozilla.org/en-US/docs/What_to_do_and_what_not_to_do_in_Bugzilla What to do and what not to do in Bugzilla], which contains instructions on getting elevated privileges.
 
= New Bots =
 
If you have a bot that uses BMO, be sure to add it to the [[BMO/Bot Registry]]
so we know who to contact about it!
 
= User Guide =
 
We're putting together a [[BMO/UserGuide|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!
 
= Road Map =
 
We keep a yearly [[BMO/Road Map|road map]] with our medium-term plans (1-2 years), at a high level.  Also see our [[BMO#Current_Projects|current projects]] for some of the big items we are working on in the current quarter.
 
= Browser Support For BMO =
 
Full Support includes: The current versions of Firefox, Chrome, Chromium, Safari, WebKit, and Edge; and the latest Firefox ESR.
 
Limited Support includes: The previous versions of Firefox, Chrome, Chromium, Safari, WebKit, Edge, and Firefox ESR; and Firefox Nightly.
 
Internet Explorer is no longer supported, though some features may still work with IE 11.
 
See {{bug|1359310}} and {{bug|1422435}}.
 
== JavaScript and Analytics ==
 
JavaScript is required to use bugzilla.mozilla.org.
 
The <code>Do Not Track</code> header sent by your browser is honored.
 
= Third-Party Applications =
 
Lots and lots of web apps and general tools have been written to interface with BMO.  We have started [[BMO/ThirdPartyApps|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: [https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html Phabricator], Mozilla's new and growing code-review tool.
 
= More Information about BMO =
 
Our discussion forum is mozilla.tools.bmo [[https://lists.mozilla.org/listinfo/tools-bmo mailing list]] [[https://groups.google.com/forum/#!forum/mozilla.tools.bmo Google Group]] [[news://news.mozilla.org:119/mozilla.tools.bmo USENET]].
 
We also have answers to [[BMO/FAQ|Frequently Asked Questions]] and a slightly-but-not-too-out-of-date [http://people.mozilla.org/~justdave/BugzillaPhysicalDiagram-rev110504.png hardware diagram].
 
If you're building an application or tool that interfaces with BMO, you may be interested in the following:
 
* [[BMO/Integration_Best_Practice|Best practices and etiquette]] for integrating external apps with BMO
* Info and plans on Bugzilla's [[Bugzilla:REST_API|REST API]], and the older, deprecated [[Bugzilla:BzAPI|BzAPI]].
 
Looking for another way to access Bugzilla's raw data?  Try the [[BMO/ElasticSearch|ElasticSearch cluster]].
 
= Contributing to BMO =
 
If you'd like to help out with BMO specifically (as opposed to the general upstream [[Bugzilla|Bugzilla project]]), you can find us in [irc://irc.mozilla.org/bmo #bmo] on irc.mozilla.org.  If you plan on contributing patches, see the documentation in the [https://github.com/mozilla-bteam/bmo/blob/master/README.rst README.rst].  You can file bugs under the [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org 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).
 
= Policies and Procedures =
 
 
== Code Updates ==
 
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.
 
Updates are usually deployed on a weekly basis and are listed on the [[BMO/Recent Changes]] page.
 
== Administrative Changes ==
 
If you need changes to BMO's configuration to support your team, project, etc., please consult this page before filing bugs:
 
* [[BMO/Requesting Changes|General information on requesting Changes to BMO]]
 
== BMO Administrative Processes ==
 
* [[BMO/new-product|Adding a new product]]
* [[BMO/new-version|Adding a new "rapid release" version]]
* [[BMO/new-security-group|Adding a new BMO security group]]
* [[BMO/RetiringComponents|Retiring Products and Components]]: moving things to the Graveyard classification.
* [[BMO/RestoringDisabledAccounts|Restoring Disabled Accounts]]
* [[BMO/MergingAccounts|Merging Accounts]]
* [[BMO/DisablingAccounts|Disabling Accounts]]
 
See also [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=45845955 BMO on Mana] (requires LDAP).
 
== BMO Development and Other Processes ==
 
* [[BMO/Development Processes|Overall Development Processes]]
 
* [[BMO/OutagePlanning|Planning a BMO outage]]
* [[BMO/ResetDevelopmentBranch|Reset the development branch to master]]
* [[BMO/Perl Dependencies|Maintaining Perl Dependencies for BMO]]
 
== Custom Bug Entry Forms ==
 
In the past, BMO developers supported writing custom bug entry forms specific for the needs of different projects and groups within Mozilla. In order to focus more on other important features, we will no longer be providing that support going forward. For more information on why this change was made, see [https://groups.google.com/forum/#!topic/mozilla.tools.bmo/tp4dSwUfKSA here].
 
There is a new [https://github.com/mozilla-bteam/custom-form-example custom form framework] being developed by an outside contributor named Sebastin Santy. It is still in the early stages but it eventually will be very useful for users who want to create a customized bug entry form that can be used to submit bugs to BMO.
 
[[Category:BMO]]

Latest revision as of 16:36, 30 October 2023

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.

B-Team

The team that works on BMO is called the B-Team, because of past affiliation with the defunct Automation and Tools team (A-Team).

  • dkl: Dave Lawrence (Owner/Engineer)
  • glob (Manager)

The Low-level, security, and quality tools team contributes tooling, and development:

  • calixte: Calixte Denizet, (AutoNag)
  • marco: Marco Castelluccio, (BugBug)

We also also have some volunteers, that we consider to be part of the B-Team as well:

  • seban: Sebastin Santy (long-term volunteer, past GSoC student)
  • atoll: Richard Solderberg (Reviewer-at-Large, slightly borrowed from Mozilla IT)
  • kohei: Kohei Yoshino, (UX Designer)
  • ... and you can be one too!

There are also some people that still have some involvement with BMO, but their day-to-day attention is directed to other parts of Mozilla.

  • zeid: Zeid Zabaneh (Engineer)

Past contributors include:

  • mary: Mary Umoh (Intern, Summer 2017)
  • gerv: Gervase Markham
  • mcote: Mark Côté
  • dylan: Dylan Hardison
  • imadueme: Israel Madueme (Engineer)
  • justdave: Dave Miller
  • emceeaich: Emma Humphries, (Bugmaster)
  • mhentges: Mitchell Hentges (Engineer)

New Users

Getting used to Bugzilla can be a bit daunting. We have a short introductory video available that is as gentle as possible. You may also be interested in the [MDN section about Bugzilla], which contains information more suitable as an introduction to a general audience. Of special interest is the MDN article, What to do and what not to do in Bugzilla, which contains instructions on getting elevated privileges.

New Bots

If you have a bot that uses BMO, be sure to add it to the BMO/Bot Registry so we know who to contact about it!

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!

Road Map

We keep a yearly road map with our medium-term plans (1-2 years), at a high level. Also see our current projects for some of the big items we are working on in the current quarter.

Browser Support For BMO

Full Support includes: The current versions of Firefox, Chrome, Chromium, Safari, WebKit, and Edge; and the latest Firefox ESR.

Limited Support includes: The previous versions of Firefox, Chrome, Chromium, Safari, WebKit, Edge, and Firefox ESR; and Firefox Nightly.

Internet Explorer is no longer supported, though some features may still work with IE 11.

See bug 1359310 and bug 1422435.

JavaScript and Analytics

JavaScript is required to use bugzilla.mozilla.org.

The Do Not Track header sent by your browser is honored.

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: Phabricator, 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 in the README.rst. 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).

Policies and Procedures

Code Updates

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.

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

Administrative Changes

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

BMO Administrative Processes

See also BMO on Mana (requires LDAP).

BMO Development and Other Processes

Custom Bug Entry Forms

In the past, BMO developers supported writing custom bug entry forms specific for the needs of different projects and groups within Mozilla. In order to focus more on other important features, we will no longer be providing that support going forward. For more information on why this change was made, see here.

There is a new custom form framework being developed by an outside contributor named Sebastin Santy. It is still in the early stages but it eventually will be very useful for users who want to create a customized bug entry form that can be used to submit bugs to BMO.

Retrieved from "https://wiki.allizom.org/index.php?title=BMO&oldid=1248774"