- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Oct 2019 23:29:35 +0000
- To: public-webrtc-logs@w3.org
@henbos My suggestion would be to create a "landing pad" extension document so that "features at risk" removed from WebRTC-PC can have some place to reside. This extension document could live in the WebRTC-PC repo which will make it easier to review removal PRs for features such as oauth and `ptime` that are already in the WebRTC-PC spec, but haven't been implemented. Since the "features at risk" already have WG consensus, they don't need to be go back to the WICG. I would suggest a separate document for features that aren't currently in WebRTC-PC, so that we aren't mixing features at different levels of maturity within the same document. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2323#issuecomment-539247668 using your GitHub account
Received on Monday, 7 October 2019 23:29:36 UTC