Re: [w3c/editing] update charter (#215)

gked commented on this pull request.



> +
+- [Async Clipboard API](https://bugs.chromium.org/p/chromium/issues/detail?id=931839) 
+- [ContentEditableDisabled](http://w3c.github.io/editing/contentEditableDisabled.html) - ability to disable system UI 
+- [EditContext API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/EditContext/explainer.md) 
+- [Highlight API](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md) 
+- Native Selection and Caret behaviors 
+- [SpellChecker API](https://github.com/w3c/editing/issues/166) 
+- [SIP Policy](https://github.com/whatwg/html/issues/4876) 
+- [Input Events](https://www.w3.org/TR/input-events-1/) 
+- [ContentEditable](https://w3c.github.io/contentEditable/) 
+
+Deliverables are expected to eventually be shipped as standards recommendation by the Web Applications Working Group, CSS Working Group or any other group where a draft specification may fall into.
+
+### 3. Participation
+
+This task force is designed to make participation relatively easy for people not currently involved in the standards process (typically, developers of editing tool libraries) who may not be amenable to signing up to a large in scope discussions that can be found in, for instance, the main Web Applications Working Group.

@marcoscaceres we wanted to remove any barriers in people's participation. I agree that it is fair for people to become Invited Experts if they are ready to commit significant time and effort into editing discussions. (by the way, how do people become Invited Experts?). That said, do people need to go through the process if they just wanted to dial-in or leave comments/open issues in github?

-- 
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/pull/215#discussion_r342327849