Re: [w3c/editing] [charter] Define the Success Criteria (#281)

@BoCupp-Microsoft 
Yes, that is different from what is in the Web Apps Working Group that we are currently under, which specifies:

> Additionally, support from two or more web platform implementers is required before a substantive change can be made to a specification. This is enforced by a pull request template on GitHub, which Editors must fill out as a public record before a substantive contribution can be merged. [1]

That is the part that basically means we should not make any change to any draft without two implementers agreeing to implement it like that. So whenever you make any change to the EditContext spec, technically, you'd need promises from at least Firefox or Safari that they will implement it also in the new way.

I think the CSS WG works well for what it does. But it's currently different from this Editing Workgroup in that it is formed as a permanent working group that has no particular start or end.  It's possible that the Editing WG also will end up like that as we find more and more things of interest to standardize in this general area. But for now, at least for the duration of this charter, the goal is still to make it easier to create webbased richtext text editors, right? And so therefore the success criteria we set for ourselves should be whether we are able to deliver this feature to the web in some form or other or not. The period of "3 years" is picked rather arbitrary though.

That being said, I can see how "success criteria" can be understood in multiple ways, and so if it's more common to put some general text there that just kind of described what we are doing, then that is fine with me as well. 

[1] https://www.w3.org/2019/05/webapps-charter.html

-- 
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/281#issuecomment-808835689