| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 1 | # Chrome Speed |
| 2 | |
| 3 | ## Contact information |
| 4 | |
| sullivan | ef27621 | 2017-06-16 20:00:04 | [diff] [blame] | 5 | * **Contact**: **speed@chromium.org** |
| sullivan | ebf00905 | 2017-06-17 01:51:08 | [diff] [blame] | 6 | * **Escalation**: |
| 7 | * benhenry@chromium.org (TPM) |
| sullivan | ebf00905 | 2017-06-17 01:51:08 | [diff] [blame] | 8 | * **File a bug**: [template](https://bugs.chromium.org/p/chromium/issues/entry?template=Speed%20Bug) |
| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 9 | * **Regression postmortem**: [template](https://docs.google.com/document/d/1fvfhFNOoUL9rB0XAEe1MYefyM_9yriR1IPjdxdm7PaQ/edit?disco=AAAABKdHwCg) |
| 10 | |
| 11 | ## User Docs |
| 12 | |
| 13 | * [How does Chrome measure performance?](how_does_chrome_measure_performance.md) |
| 14 | * [My CL caused a performance regression! What do I do?](addressing_performance_regressions.md) |
| 15 | * [I want Chrome to have better performance](help_improve_performance.md) |
| 16 | * [Perf sheriffing documentation](perf_regression_sheriffing.md) |
| 17 | * [I want to add tests or platforms to the perf waterfall](adding_tests_bots.md) |
| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 18 | |
| 19 | ## Core Teams and Work |
| 20 | |
| Tim Dresser | 676006fd | 2018-03-28 16:44:21 | [diff] [blame^] | 21 | * **[Speed tracks](speed_tracks.md)**: Most of the speed |
| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 22 | work on Chrome is organized into these tracks. |
| sullivan | 6562f627 | 2017-06-16 21:33:32 | [diff] [blame] | 23 | * **[Chrome Speed Operations](chrome_speed_operations.md)**: provides the |
| 24 | benchmarks, infrastructure, and releasing oversight to track regressions. |
| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 25 | <!--- TODO: General discussion: chrome-speed-operations mailing list link --> |
| 26 | <!--- TODO: Tracking releases and regressions: chrome-speed-releasing mailing list link --> |
| 27 | * Benchmark-specific discussion: benchmarking-dev@chromium.org |
| 28 | <!--- TODO: Requests for new benchmarks: chrome-benchmarking-request mailing list link --> |
| 29 | * Performance dashboard, bisect, try jobs: speed-services-dev@chromium.org |
| Tim Dresser | 676006fd | 2018-03-28 16:44:21 | [diff] [blame^] | 30 | * **Chrome Speed Metrics**: provides a set of high-quality metrics that represent real-world user experience, and exposes these metrics to both Chrome and Web Developers. |
| sullivan | c3535a7d | 2017-06-16 19:12:51 | [diff] [blame] | 31 | * General discussion: progressive-web-metrics@chromium.org |
| Tim Dresser | 676006fd | 2018-03-28 16:44:21 | [diff] [blame^] | 32 | * The actual metrics: [speed launch metrics survey.](https://docs.google.com/document/d/1Ww487ZskJ-xBmJGwPO-XPz_QcJvw-kSNffm0nPhVpj8/edit#heading=h.2uunmi119swk) |
| Ben Henry | 9f703ad | 2018-01-08 21:32:32 | [diff] [blame] | 33 | |
| 34 | ## For Googlers |
| 35 | |
| 36 | * We have a bi-weekly meeting to keep everyone in sync. Join chrome-speed@ or |
| 37 | contact benhenry@chromium.org for more information. |
| 38 | * Have something to include in our Milestone-based Speed report to the Chrome |
| 39 | team? Please keep track of it [here](https://goto.google.com/speed-improvement). |
