- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Thu, 17 Feb 2022 17:01:48 +0000
- To: "public-webrtc@W3.org" <public-webrtc@w3.org>
- Message-ID: <DM6PR00MB07327B870386308F006F0020EC369@DM6PR00MB0732.namprd00.prod.outlook.com>
The Call for Adoption (CfA) of "Capture Handle - Bootstrapping Collaboration when Screensharing" concluded on February 14, 2022. The original announcement is here: https://lists.w3.org/Archives/Public/public-webrtc/2022Jan/0112.html 6 responses were received. 5 responses favored adoption: Tony Herre: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0000.html Elad Alon: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0003.html Arnaud Budkiewicz: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0017.html Bernard Aboba: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0013.html Harald Alvestrand: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0043.html There was 1 objection: Jan-Ivar Bruaroey: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0036.html Issues listed in the objection: Issue 3: Use case 1 is too broadly scoped by its headline https://github.com/WICG/capture-handle/issues/3 Issue 4: Use case 1 presumes tight integration https://github.com/WICG/capture-handle/issues/4 Issue 5: The API proposed is insufficient to solve use case 1 https://github.com/WICG/capture-handle/issues/5 Issue 6: Integrate the Actions compromise presented at January WebRTC interim https://github.com/WICG/capture-handle/issues/6 The Chairs will discuss next steps. Bernard For the Chairs
Received on Thursday, 17 February 2022 17:02:04 UTC