New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write a "how to add more stats" guideline document #345
Comments
This document will be targeted towards developers and aims to:
No more "I filed an issue and nothing happened so I added a goog-stat". This will allow us to:
|
The document should also cover experimental stats, both the kind we aim to standardize but need to test the metric before we know it's a good one and the kind that is only useful for Chromium debugging and evaluating the result of feature experiments. |
Experimental stats will have limited exposure, e.g. not exposed to the web platform by default (hidden behind Origin Trials experiment, etc.). |
Here's the doc I intend to share, please comment. |
Sent to mailing list, no comments. Guess it's perfect. |
It makes sense to either link to it or copy it into the webrtc-stats repo - not as a spec, but as "helpful material". |
I'll create a PR to link to it from our README.md. |
We're so closed to PR we probably don't need this anymore |
Go to provisional stats to give input |
This has been on the plan for a while, but it's nice to have a bug on it.
The text was updated successfully, but these errors were encountered: