Firefox Core Engineering

Purpose

"The Platform teams and Firefox teams are co-dependent, but oftentimes priorities between the two groups do not line up perfectly. If Platform has a goal to ship some new feature that requires UI, and the Firefox team has no cycles to help develop the UX or UI, then it that feature will often languish."

This can happen in the opposite direction too, with Firefox needing support for a feature that doesn't line up with current Platform priorities.

The purpose of this team is to address needs that fall between Firefox and Platform, with an emphasis (currently) on improving stability, quality, and performance – supported by data. As such, we overlap a bit with everyone from Platform through Firefox, Data, and more.

This team grew out of, in part, the Performance Engineering team, and owns that team's previous infrastructure – performance-related dashboards on telemetry.mozilla.org, the symbolication server, and more.

Personnel

Neil Deakin (:enn)
Felipe Gomes (:felipe)
Chris HC (:chutten)
Kirk Steuber (:bytesized)
Gabriele Svelto (:gsvelto)
Jimmy Wang (:jimicy)
David Durst (:ddurst)

Communication

Currently, we do not reside in just one IRC channel or mailing list. You can typically find us in:

IRC

#developers
#e10s
#fx-team
#perf
#telemetry
#uptime

Mailing lists

bsmedberg-team
dev-platform
fhr-dev

Process and Queuing

There is currently no regimented process for regular triage of candidate work. Needs usually filter down through Benjamin Smedberg's team or tangentially related to e10s performance analysis and experimentation.

All actively tracked work is marked with the whiteboard "[fce-active]" (for now). Or look at the #Active Bug List on this page.

Major initiatives are listed here.

Owned Infrastructure

telemetry.mozilla.org Dashboards

All of these dashboards are in the process of transferring ownership. Please contact ddurst if you need data that is currently not functional.

Add-on startup correlation: via iacomus; broken on 403 for S3 bucket
Add-on shutdown correlation: via iacomus; broken on 403 for S3 bucket
Main Thread I/O: data exists? status code 200 but no data
Population Distribution: functional
Power Dashboard: functional
SlowSQL: functional
ChromeHangs: jquery csv issue resolved, currently backfilling data from 3/07 to 6/05

symbolapi.mozilla.org

This is the symbolication server (aka "Snappy Symbolication Server") used by platform developers and performance dashboards. It is not used for the analogous process on socorro.

Historical knowledge areas

e10s system add-on (felipe)
e10s data analysis (chutten)
telemetry (histograms and pings) and data reporting (chutten)
stack walking (gsvelto)
back-end of the user interface (enn)

Pipeline

2016 Q3

Client-side stackwalking in Nightly/Aurora (read the planning doc, or view on bugzilla)
ChromeHangs, SlowSQL, and Main Thread I/O dashboard rebuild
Assisting with add-ons e10s experimentation
Content process data aggregation, collection, and crash handling (view on bugzilla)
Preparing for Plugin blocking & UI: definition, experimentation with Test Pilot (read the planning doc, or view on bugzilla)

Potential future projects

This list should be considered a work in progress. Decisions will be reflected for a particular quarter.

Profiling WebExtensions (via dev tools)
Assisting with measuring (and addressing) jank and hang

Active Bug List

No results.

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