Add some speed documentation:
* README.md, which is intended to be the main landing site for
go/chrome-speed
* how_does_chrome_measure_performance.md, which matches our original
outline pretty closely.
* addressing_performance_regressions.md, which had a few differences
from our original outline:
- I felt it was better to put eveything in one doc, since I do stuff
like refer to the bisect bot output in multiple sections.
- I added a LOT more detail than I think we originally had slated.
- I added a "it's not my cl!" section.
There's still a long way to go, but I think this is a good base.
[email protected],[email protected]
Review-Url: https://codereview.chromium.org/2943013003
Cr-Commit-Position: refs/heads/master@{#480118}
diff --git a/docs/speed/README.md b/docs/speed/README.md
new file mode 100644
index 0000000..2aaa2c9
--- /dev/null
+++ b/docs/speed/README.md
@@ -0,0 +1,33 @@
+# Chrome Speed
+
+## Contact information
+
+ * **Contact**: TBD
+ * **Escalation**: [email protected] (PM), [email protected] (TPM),
+ [email protected] (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: [email protected]
+ <!--- TODO: Requests for new benchmarks: chrome-benchmarking-request mailing list link -->
+ * Performance dashboard, bisect, try jobs: [email protected]
+ * **[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: [email protected]
+ * The actual metrics: [tracking](https://docs.google.com/spreadsheets/d/1gY5hkKPp8RNVqmOw1d-bo-f9EXLqtq4wa3Z7Q8Ek9Tk/edit#gid=0)
\ No newline at end of file
