* dkl: Dave Lawrence (Owner/Engineer)
* emceeaich: Emma Humphries, (Bugmaster)
* glob (Manager)
* zeid: Zeid Zabaneh (Engineer)
* mhentges: Mitchell Hentges (Engineer)
Past contributors include:
* imadueme: Israel Madueme (Engineer)
* justdave: Dave Miller
* emceeaich: Emma Humphries, (Bugmaster)
* mhentges: Mitchell Hentges (Engineer)
= New Users =
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.
= 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; some of which will take more than a day or two in total, thus potentially jeopardizing other goals. The other daily 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 ==
<div>
<bugzilla>
{
"keywords": "bmo-goal",
"keywords_type": "anywords",
"include_fields": "id, priority, summary, status, resolution, assigned_to",
"field0-0-0": "status",
"type0-0-0": "equals",
"value0-0-0": "NEW",
"field0-0-1": "status",
"type0-0-1": "equals",
"value0-0-1": "ASSIGNED",
"field0-0-2": "status",
"type0-0-2": "changed_after",
"value0-0-2": "2018-01-01"
}
</bugzilla>
</div>
== High-Priority ==
<div>
<bugzilla>
{
"product": "bugzilla.mozilla.org",
"keywords": "bmo-on-deck, bmo-goal",
"keywords_type": "nowords",
"priority": ["P1"],
"include_fields": "id, priority, summary, status, resolution, assigned_to",
"status": ["ASSIGNED"],
"field0-0-2": "status",
"type0-0-2": "changed_after",
"value0-0-2": "2017-01-01"
}
</bugzilla>
</div>
== Upcoming ==
<div>
<bugzilla>
{
"keywords": "bmo-on-deck",
"keywords_type": "anywords",
"priority": ["--","P1","P2","P3","P4","P5"],
"include_fields": "id, priority, summary, status, resolution, assigned_to",
"field0-0-0": "status",
"type0-0-0": "equals",
"value0-0-0": "NEW",
"field0-0-1": "status",
"type0-0-1": "equals",
"value0-0-1": "ASSIGNED",
"field0-0-2": "status",
"type0-0-2": "changed_after",
"value0-0-2": "2017-01-01"
}
</bugzilla>
</div>
Further documentation about goals above and other projects follows:
* [[BMO/UserRoles|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.
* [[BMO/ChangeNotificationSystem|Change Notification System]]
* [[BMO/40Upgrade|4.0 Upgrade]]
* [[BMO/42Upgrade|4.2 Upgrade]] (Completed March 5th, 2013)
* [[BMO/UserProfiles|User Profiles]]
* [[BMO/TrackingFlags|Tracking Flags]]
* [[Bugzilla:REST_API|Native REST API]]
* [[BMO/Pulse|Pulse Integration]]
** This was completed and deployed, but it generated a lot of traffic and is of questionable utility since it must access Bugzilla as an anonymous user. A simpler, more general system is the [[BMO/ChangeNotificationSystem|Change Notification System]].
* [[Bugzilla:Migrating_to_git|Migrating Bugzilla and BMO code from bzr to git]]
** Completed 2014/03/11.
[[Category:BMO]]
