Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(2371)

Unified Diff: docs/speed/README.md

Issue 2943013003: Add some speed documentation: (Closed)
Patch Set: Removed references to google.com mailing lists. Created 3 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | docs/speed/addressing_performance_regressions.md » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/speed/README.md
diff --git a/docs/speed/README.md b/docs/speed/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..2aaa2c9e1faaf67902d1ce6cd0be4f3fca26bf73
--- /dev/null
+++ b/docs/speed/README.md
@@ -0,0 +1,33 @@
+# Chrome Speed
+
+## Contact information
+
+ * **Contact**: TBD
+ * **Escalation**: rschoen@chromium.org (PM), benhenry@chromium.org (TPM),
+ parisa@chromium.org (eng director)
+ * **[File a bug](https://bugs.chromium.org/p/chromium/issues/entry?template=Speed%20Bug)**
+ * **Regression postmortem**: [template](https://docs.google.com/document/d/1fvfhFNOoUL9rB0XAEe1MYefyM_9yriR1IPjdxdm7PaQ/edit?disco=AAAABKdHwCg)
+
+## User Docs
+
+ * [How does Chrome measure performance?](how_does_chrome_measure_performance.md)
+ * [My CL caused a performance regression! What do I do?](addressing_performance_regressions.md)
+ * [I want Chrome to have better performance](help_improve_performance.md)
+ * [Perf sheriffing documentation](perf_regression_sheriffing.md)
+ * [I want to add tests or platforms to the perf waterfall](adding_tests_bots.md)
+ * [I'm looking for more information on the Speed Progam](speed_program.md)
+
+## Core Teams and Work
+
+ * **[Performance tracks](performance_tracks.md)**: Most of the performance
+ work on Chrome is organized into these tracks.
+ * **[Chrome Speed Operations](https://docs.google.com/document/d/1_qx6TV_N20V3bF3TQW74_9kluIJXAwkB8Lj2dLBRsRc/edit)**: provides the benchmarks, infrastructure, and
+ releasing oversight to track regressions.
+ <!--- TODO: General discussion: chrome-speed-operations mailing list link -->
+ <!--- TODO: Tracking releases and regressions: chrome-speed-releasing mailing list link -->
+ * Benchmark-specific discussion: benchmarking-dev@chromium.org
+ <!--- TODO: Requests for new benchmarks: chrome-benchmarking-request mailing list link -->
+ * Performance dashboard, bisect, try jobs: speed-services-dev@chromium.org
+ * **[Chrome Speed Metrics](https://docs.google.com/document/d/1wBT5fauGf8bqW2Wcg2A5Z-3_ZvgPhE8fbp1Xe6xfGRs/edit#heading=h.8ieoiiwdknwt)**: provides a set of high-quality metrics that represent real-world user experience, and exposes these metrics to both Chrome and Web Developers.
+ * General discussion: progressive-web-metrics@chromium.org
+ * The actual metrics: [tracking](https://docs.google.com/spreadsheets/d/1gY5hkKPp8RNVqmOw1d-bo-f9EXLqtq4wa3Z7Q8Ek9Tk/edit#gid=0)
« no previous file with comments | « no previous file | docs/speed/addressing_performance_regressions.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698