Firefox/Search

From MozillaWiki
Jump to: navigation, search

Firefox Desktop Search and Navigation Team

The purpose of this team is to maintain, improve and innovate on the functions of the Firefox frontend around search and navigation. Firefox surface areas that the team often works with are the location bar, the search bar, the library and related preference panes.

Members

  • Mark Banner (Standard8)
  • Michael de Boer (:mikedeboer)
  • Marco Bonardo (:mak)
  • Bridget Kaluzny
  • Javaun Moradi (:javaun)
  • Drew Wilcoxon (:adw)
  • Mike Connor (:mconnor)
  • Dão Gottwald (:dao)
  • Dale Harvey (:Dale)

Contact

Team Meeting

Day of week Pacific Time Eastern Time UTC Central European Time
Mondays 10:00AM - 10:30AM 1:00PM - 1:30PM 6:00PM - 6:30PM 7:00PM - 7:30PM
  • Frequency: One meeting per week on Monday.
  • Duration: 30 min
  • Vidyo Room: searchmeeting
  • IRC: #fx-search, #fx-team
  • Mailing list: fx-search, firefox-dev

Bugzilla

Bugzilla components don't tend to align properly with project boundaries, so this team is monitoring bugs across a number of components that contain the whiteboard tag [fxsearch]. Common components of interest are Firefox:Location bar, Firefox:Search, Toolkit:Places and more.

Selecting a New Bug for the Current Release

  1. Select any 'P1' bug which is currently unassigned and not blocked on a dependency. If no 'P1' bugs are available then select from the available 'P2' bugs, and so on.
  2. Add the following if not already present:
  • [fxsearch] whiteboard tag.
  • QE verification flag.

Adding a New Bug to the Backlog

  1. Add the [fxsearch] whiteboard tag.
  2. Set the bug as a dependency of a user story bug or a meta bug if applicable.
  3. The bug priority will be set during the Weekly Meeting:
  • 'P1': Must Have - development occurring in the current release.
  • 'P2': Should Have - targeted for next release.
  • 'P3': Could Have - planned for development in an upcoming release.
  • 'P5': Will Have - not scheduled for any particular release, patches accepted.

Submitting a Bug for Triage

  1. Add the [fxsearch] whiteboard tag.
  2. Leave the priority field empty (--).

Triage

Collection of work waiting for the team to review and determine if it should be included in the Product Backlog

No results.

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

Releases

Current Release

P1: Must Have - development occurring in the current release

Next merge: Mar 18 (soft-freeze is one week earlier)

No results.

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

Current Release: Completed

No results.

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

Next Release

P2: Should Have - targeted for the current release if production capacity exists

No results.

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

Backlog

P3: Could Have - planned for development in an upcoming release

No results.

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

Patches Accepted

P5: Will Have - not scheduled for any particular release, patches accepted

No results.

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

¯\_(ツ)_/¯

P4: (should be reprioritized to P3 or P5)

No results.

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

Completed Releases

View Performance Archive