- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2023 23:51:27 +0000
- To: public-webrtc-logs@w3.org
> - The API does not have consensus in the WG @alvestrand could you be more specific about which parts of the API lack consensus? Looking at the history, RTCRtpScriptTransform appears to have consensus from our September 2. 2021 [successful CfC](https://lists.w3.org/Archives/Public/public-webrtc/2021Sep/0000.html) on our [FPWD](https://www.w3.org/TR/2021/WD-webrtc-encoded-transform-20210921/#rtcrtpscripttransform) (1 objection was over SFrameTransform). From your [response](https://lists.w3.org/Archives/Public/public-webrtc/2021Aug/0041.html): > I support promoting this document to WG draft. > > Note that I still think the document is a better document if #111 is merged (I don't think we did a good job of checking consensus on #64), and I think we should resolve #89 according to my suggestions there, but I think we can continue that discussion post FPWD. You expressed concern that we didn't do a good job checking consensus on #64 which you merged four months prior to CfC following agreement at the [April meeting](https://lists.w3.org/Archives/Public/public-webrtc/2021Apr/0049.html). But isn't the CfC a catch-all for this? No other responses mentioned it. No concerns seemed raised against the RTCRtpScriptTransform API shape itself, modulo a constructor argument. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/216#issuecomment-1865287174 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 December 2023 23:51:30 UTC