Add some speed documentation:

docs/speed/README.md

+# Chrome Speed
+
+## Contact information
+
+  * **Contact**: chrome-speed@google.com

[benhenry, 2017/06/16 18:01:28]

Can we make this TBD for now?

[sullivan, 2017/06/16 18:53:54]

Yep! Do you think it's reasonable to have something figured out by Thursday
though?

+  * **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.
+    * General discussion: chrome-speed-operations@google.com

[benhenry, 2017/06/16 18:01:28]

Are you ok taking out things with @google email right now? Also, since this is
in the open source, maybe we should think about which of these are necessary for
all people vs. googlers.

[sullivan, 2017/06/16 18:53:54]

I took these out for now. FWIW I really like the memory documentation's use of
chromium vs google mails:
https://chromium.googlesource.com/chromium/src/+/master/docs/memory

It links google.com mailing lists but it has a clear rationale of why each list
exists and when to use them. I think it's fine for us to put google.com lists
back in the documentation when our mailing list story is that crisp. Do you
agree?

+    * Tracking releases and regressions: chrome-speed-releasing@google.com
+    * Benchmark-specific discussion: benchmarking-dev@chromium.org
+    * Requests for new benchmarks: chrome-benchmarking-request@google.com
+    * 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)