- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2023 02:46:33 +0000
- To: public-webrtc-logs@w3.org
The reason for the lightweight process was that, historically, the metrics were well defined and if there was a good standards reference, it was quicker to include it into the spec, as webrtc observability was in its infancy and we needed a corpus of well defined metrics, for browsers to implement. However, with the emergence of the experimental spec, the bar for the main webrtc-stats spec was raised from well defined metric to at least one implementation of the metric (the implicit assumption that it was well defined and/or was shown to be useful in an origin trial or similar). All metrics that do not meet the bar are moved to the experimental spec. So perhaps a moment in time to re-think the above process. I would rather move towards a more rigorous PR process than have a combined editor's meeting (which would still not be an open meeting). -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/746#issuecomment-1469223530 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 March 2023 02:46:35 UTC