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

@johanneswilm, I agree, it is not about the specs per se but rather about whether they solve developer problem. 
As W3C working group we should agree on the successful flow which I think, we are all aligned on:

1. Developer presents a problem.
2. Someone (can be invited experts or browsers themselves) propose solution that solves the problem via an explainer
3. People discuss high level solutions via the explainer. 
4. Once there is a general agreement on the shape of an API, spec editor is determined and the spec is drafted.
5. Spec editors get a commitment from at least two implementers.
6. Spec draft is moved into a official recommendation draft.

I think what we are talking about here is the commitment on delivery of steps 5 - 6. Steps 5 and 6 are naturally out of control for WG. If chairs also happen to be spec editors then 6 can be mitigated.
And I think the wording below matches the flow I outlined with minor corrections:

> How about --
> In order to advance to [Proposed Recommendation](https://www.w3.org/Consortium/Process/#RecsPR), each specification is expected to have [at least two independent implementations](https://www.w3.org/Consortium/Process/#implementation-experience) of each feature defined in the specification, which may include in a basic JS text editor that works across writing system, based on tests. The Working Group is therefore expected to proactively work on writing, reviewing, and maintaining tests.


In order to advance to [Proposed Recommendation](https://www.w3.org/Consortium/Process/#RecsPR), each specification is expected to have [at least two independent implementations](https://www.w3.org/Consortium/Process/#implementation-experience) of each feature defined in the specification, which may include in a basic JS text editor that works across writing systems and with a sufficient number of tests. The Working Group is therefore expected to proactively work on writing specifications, reviewing issues, and maintaining tests.


-- 
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-816045652