Resolution of CfC on publishing an FPWD of "Region Capture"

Responses to the CfC on publishing an FPWD of "Region Capture" referred to unmerged PRs relating to several issues.

The PRs have now been merged, and the following issues are now resolved:
CropTarget should be made serializable · Issue #21 · w3c/mediacapture-region (github.com)<https://github.com/w3c/mediacapture-region/issues/21>
Remove language related to muting cropped tracks · Issue #22 · w3c/mediacapture-region (github.com)<https://github.com/w3c/mediacapture-region/issues/22>

Discussion continues on several API shape issues which need to be resolved promptly, but are not blocking publication of the FPWD:
Why expose produceCropTarget at MediaDevices level? · Issue #11 · w3c/mediacapture-region (github.com)<https://github.com/w3c/mediacapture-region/issues/11>
What makes CropTarget special to require an asynchronous creation? · Issue #17 · w3c/mediacapture-region (github.com)<https://github.com/w3c/mediacapture-region/issues/17>
Is CropTarget name too generic? · Issue #18 · w3c/mediacapture-region (github.com)<https://github.com/w3c/mediacapture-region/issues/18>

With the blocking comments resolved, we declare WG consensus to proceed with FPWD publication of "Region Capture".

Bernard

For the Chairs

-----------------------------------------------

The Call for Consensus (CfC) on publishing a FPWD of "Region Capture" completed on March 14, 2022.

The initial CfC announcement is here:
https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0063.html

5 WG participants responded to the CfC.

In support(3):
Elad Alon: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0064.html
Bernard Aboba: https://lists.w3.org/Archives/Public/public-webrtc/2022Feb/0065.html
Harald Alvestrand: https://lists.w3.org/Archives/Public/public-webrtc/2022Mar/0018.html

Objection (1):
Jan-Ivar Bruaroey: https://lists.w3.org/Archives/Public/public-webrtc/2022Mar/0031.html

No position taken, with comments (1):
Youenn Fablet: https://lists.w3.org/Archives/Public/public-webrtc/2022Mar/0011.html

Youenn's comment:

It seems desirable to improve the quality of the document a bit before making it a FPWD.

Several issues have been filed and seems to reach consensus (see issues labelled as Ready for PR).
I would tend to go over them and update the document accordingly before publishing it as FPWD (https://github.com/w3c/mediacapture-region/issues/22 <https://github.com/w3c/mediacapture-region/issues/22> and https://github.com/w3c/mediacapture-region/issues/21 <https://github.com/w3c/mediacapture-region/issues/21> in particular).

There are also a few API shape issues that it would be good to decide sooner rather than later, given Chrome is experimenting with this API.
I am thinking of:
- https://github.com/w3c/mediacapture-region/issues/11 <https://github.com/w3c/mediacapture-region/issues/11>
- https://github.com/w3c/mediacapture-region/issues/17 <https://github.com/w3c/mediacapture-region/issues/17>
- https://github.com/w3c/mediacapture-region/issues/18 <https://github.com/w3c/mediacapture-region/issues/18>

Elad's response:
https://lists.w3.org/Archives/Public/public-webrtc/2022Mar/0016.html

(Notes PRs for Issues 21 and 22, as well as ongoing discussion on issues 11, 17 and 18).

Jan-Ivar's objection:
I object to publishing a Region Capture FPWD in the present form, due to the same issues Youenn mentioned.

My objection is mild and could have been avoided by getting the document in shape ahead of CfC. The process [1] sates:

*"For all Working Drafts a Working Group:*

   - *should** document outstanding issues, and parts of the document on
   which the Working Group does not have consensus, and *
   - *may** request publication of a Working Draft even if its content is
   considered unstable and does not meet all Working Group requirements."*

Assuming there are no more objections, I propose we spend the time between
now and Thursday's editor's call to get *"ready for PR"* PRs merged,
document outstanding *"API shape issues"* disagreements as Notes in the
document, and then proceed with FPWD.

[1] https://www.w3.org/2020/Process-20200915/#maturity-levels

The Chairs will discuss next steps.

Bernard

For the Chairs