W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [webrtc-pc] Move features at risk to an extension spec (#2323)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 10 Oct 2019 09:16:42 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-540478996-1570699001-sysbot+gh@w3.org>
I think what @aboba said is important; there may be a distinction between more mature features that have not been implemented but have consensus, and less mature features that there is interest from at least one implementer to do, but commitment and priority is unclear from other implementers.

On the latter with my Chrome hat on, I want to unblock our engineers from shipping features that is of immediate interest to Chrome, but I do not want this to happen wild west style - we need a place of discussion and attempt at standardizing features that are still on their way to maturing, and minimize divergence and interop risks on our path to get there.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2323#issuecomment-540478996 using your GitHub account
Received on Thursday, 10 October 2019 09:16:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC