Re: [webrtc-stats] Assorted comments on `RTCAudioPlayoutStats` (#742)

> This was not presented to the WG, it was presented on the bi-weekly stats meeting.

Those meetings aren't open to members, and therefore do not represent the view of the WG. My understanding of the role of editors includes discretion to craft and merge editorial PRs, maybe PRs for normative bug fixes where WG opinion can be inferred from earlier discussion, and PRs for issues that have been discussed in the WG that the WG agrees to proceed with.

It's been best practice for a while in most specs this WG owns to present new features and even substantive normative fixes to the WG in its monthly online interim meeting to ensure that proper WG discussion has happened.

> We've had bi-weekly stats editors meetings for years (since the inception of the getStats API), but as of recently there have been a couple of questions around WG involvement.

This document, now governed by the [2 November 2021 W3C Process Document](https://www.w3.org/2021/Process-20211102/), is [auto-published](https://www.w3.org/standards/history/webrtc-stats) by the chairs to [TR](https://www.w3.org/TR/webrtc-stats/#dom-rtcstatstype-media-playout), which is the canonical version the public is pointed to, in spite of its disclaimer:
- _"Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Draft integrates changes from the previous Candidate Recommendation that the **Working Group intends to include** in a subsequent Candidate Recommendation Snapshot."_

I've emphasized _"Working Group intends to include"_ to highlight that this document purports to represent the current will of the WG, not its editors.

> In your opinion ...Should WG presentation be required any time we add a new stats type?

Yes. Other WGs that have a more live document model usually pay the cost of a more rigorous PR process.

> Any time we make "larger" additions?

If they're normative, yes. This [has been happening](https://docs.google.com/presentation/d/1HUx-gh2RlNMCjHNbTjQYvrPcLmov8Sq8MAC7sNxXbB8/edit#slide=id.g152223e7293_31_17) AFAIK.

> Or do you want to get involved in the bi-weeklies as well / individual metrics?

Adding one more person to those meetings won't solve things. For disclosure, I was unaware of this recurring meeting until last year, and I haven't been at them. All other WebRTC specs are covered by our weekly WebRTC editors' meeting, which I attend regularly.



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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 8 March 2023 15:50:49 UTC