[w3c/editing] CFC: Move ExecCommand to WICG (#185)

This is a Call For Consensus (CFC) for the proposal to move the [ExecCommand](http://w3c.github.io/editing/execCommand) specification to the Web Platform Incubator Community Group (WICG).

This proposal has been discussed in the [Editing Task Force (TF)](https://github.com/w3c/editing/issues/184
).

There are reasons for moving ExecCommand to WICG, and reasons to keep it in the WebApps WG (which is expected to partly replace the WebPlat WG).

Reasons for moving ExecCommand to WICG:
* It will enable more input from the developer community
* The specification has implementations, but not interoperability
* There is no commitment from implementors to resolve the interoperability
* ExecCommand will ultimately be replaced by [contentEditable](http://w3c.github.io/editing/contentEditable) and [Input Events](https://rawgit.com/w3c/input-events/v1/)

Reasons for keeping ExecCommand in WebApps:
* It will keep all the Editing Task Force (TF) specifications in one place
* The Editor prefers that it remain in the WG
* ExecCommand will ultimately be replaced by contentEditable and Input Events

If you think that ExecCommand should move to WICG, please respond to this issue with a "thumbs up".

If you think that ExecCommand should remain in the WG, please respond to this issue with a "thumbs down".

If you do not feel strongly, or do not want to participate in this CFC, please put a "0" or "abstain" in a comment on this issue.

You do not need to respond at all, but it really helps if you do. If you would like to respond privately, you can send your response to team-webplatform@w3.org instead.

Please respond to this CFC no later than the end of your day on Tuesday 20th November 2018.

@marcoscaceres @chaals 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/185