Confirmed users
746
edits
Firefox Core Engineering: Difference between revisions
in progress
(in progress) |
(in progress) |
||
| Line 1: | Line 1: | ||
=Purpose= | == Purpose == | ||
Quoting the [[Platform/UI Team]]: "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 | Quoting the [[Platform/UI Team]]: "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. | 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 | 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= | == Personnel == | ||
* Neil Deakin (:enn) | * Neil Deakin (:enn) | ||
* Felipe Gomes (:felipe) | * Felipe Gomes (:felipe) | ||
| Line 13: | Line 13: | ||
* Gabriele Svelto (:gsvelto) | * Gabriele Svelto (:gsvelto) | ||
* David Durst (:ddurst) | * David Durst (:ddurst) | ||
== 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). | |||
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 | |||
* Add-on shutdown correlation | |||
* Main Thread I/O | |||
* Population Distribution | |||
* Power Dashboard | |||
* SlowSQL | |||
* ChromeHangs | |||
=== symbolapi.mozilla.org === | |||
This is the [[Snappy_Symbolication_Server|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 == | |||