Re: [webrtc-stats] Write a "how to add more stats" guideline document

This document will be targeted towards developers and aims to:
- Give developers an idea how standardization works and guide them through it.
- Put ownership of the entire process of adding the stats (spec issue, spec PR, implementation) on the developer proposing the stats. Allowing resources and expertise to be used appropriately.
- Decrease the perceived and actual delay time of standardization efforts. Spec should not be a blocker unless we really should not add the stats.

No more "I filed an issue and nothing happened so I added a goog-stat".

This will allow us to:
- BAN adding more goog-stats, which will...
- Incentivize more development efforts to be put into spec-compliance, and
- Encourage switching to the spec-compliant API.
- And eventually deprecate legacy getStats().

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/345#issuecomment-378652375 using your GitHub account

Received on Wednesday, 4 April 2018 15:57:50 UTC