Re: Call for Consensus (CfC): Publish webrtc-stats as updated Candidate Recommendation

I do too. But should the “CR blocker” labels be changed to “PR blocker”? The current label seems to serve no purpose if we spin a new CR without resolving the issues.

From: Henrik Boström <hbos@google.com>
Date: Monday, 15 July 2019 at 13:24
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: Call for Consensus (CfC): Publish webrtc-stats as updated Candidate Recommendation
Resent-From: "public-webrtc@w3.org" <public-webrtc@w3.org>
Resent-Date: Monday, 15 July 2019 at 13:23

I support publishing the current webrtc-stats as CR


On Fri, Jul 12, 2019 at 8:29 PM Bernard Aboba <Bernard.Aboba@microsoft.com<mailto:Bernard.Aboba@microsoft.com>> wrote:
The respec errors in Webrtc-Stats are now fixed:
https://w3c.github.io/webrtc-stats/

________________________________
From: Bernard Aboba <Bernard.Aboba@microsoft.com<mailto:Bernard.Aboba@microsoft.com>>
Sent: Thursday, July 11, 2019 8:09 AM
To: Harald Alvestrand <harald@alvestrand.no<mailto:harald@alvestrand.no>>; public-webrtc@w3.org<mailto:public-webrtc@w3.org> <public-webrtc@w3.org<mailto:public-webrtc@w3.org>>
Subject: Re: Call for Consensus (CfC): Publish webrtc-stats as updated Candidate Recommendation

The Editor's draft<https://w3c.github.io/webrtc-stats/> shows 11 respec errors, and the Issues list<https://github.com/w3c/webrtc-stats/issues> shows 8 unresolved Issues with the "CR blocker" label.

So perhaps a little more work is needed before a CR can be published.
________________________________
From: Harald Alvestrand <harald@alvestrand.no<mailto:harald@alvestrand.no>>
Sent: Wednesday, July 10, 2019 7:52 AM
To: public-webrtc@w3.org<mailto:public-webrtc@w3.org> <public-webrtc@w3.org<mailto:public-webrtc@w3.org>>
Subject: Call for Consensus (CfC): Publish webrtc-stats as updated Candidate Recommendation

Our present webrtc-stats, published as https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fwebrtc-stats%2F&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C0d5b18e330f34e01f29c08d705467791%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636983672521933649&amp;sdata=efffKD9Wp7Rd0D9Vyxvb5jAHeY0xiwBINk1xxdE6WQY%3D&amp;reserved=0, is almost exactly 1 year old.

The spec has evolved significantly over the course of a year; having this old version
around just confuses things.

The spec is still evolving, and needs some tidying, but the chairs feel that it is better to emit this one
as Candidate Recommendation now than to wait for stability to increase. Thus:

This is a Call for Consensus to push the editors' draft,
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-stats%2F&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C0d5b18e330f34e01f29c08d705467791%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636983672521933649&amp;sdata=fcxkyzDASKpqrkZMrozRSh8HxSLy34wVW8z3BSSO6xk%3D&amp;reserved=0, out as a new version of our
Candidate Recommendation.

The CfC will last for one week, and end on Wednesday, July 17, at 16:00 UTC

In response, please state one of the following:

- I support publishing the current webrtc-stats as CR

- I object to publishing the current webrtc-stats as CR, due to
issues filed in open bug <#number>.

Harald, for the chairs

--
Surveillance is pervasive. Go Dark.