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

> The point is that it provides more ability for a wider audience to participate in the process - it's why the W3C community created the WICG in the first place: to remove the need for "invited experts" and lower the barrier or entry for folks that want to participate in the standards process.

This probably applies to some working groups, but in this editing taskforce, I doubt that you could build much more of a community than what we have done already. The number of JS editing projects out there is limited. And we have been writing to every single text editing project out there to ask their opinions about various things - and inviting them to participate more directly in some form. There are several that have been participating in physical meetings as well and of course on the mailing list. The reason several of them prefer to wait for me to email them with questions every now and then rather than write on the email list themselves is that likely that they have a business to run and a software to maintain and therefore only participate if they see things moving in the wrong direction. I doubt adding a WICG community page will change any of it. Also the number of text editors out there is somewhat naturally limited by the amount of effort it takes to program one (several years) and the relatively slim profit margins in the sector.

When it comes to developers working on editing code in browsers - we have participation in some form or another of those developers from at least Firefox, Chrome and Safari, and we have representatives from all four browsers participating in the taskforce at all levels.

I don't know who is in charge of the email list and if there should be some kind of strict check for IE in there, but reality is that there is not, nor is there on filing github issues. My own participation started, if I recall correctly, in that I started posting things on the email list and eventually someone from the W3C asked me to please click through something to accept status as an Invited Expert. I don't really see how it could have made sense for me to start changing files on github before talking to anyone on the mailing list.

So far this sounds to me like a solution in search for a problem. I see no benefit to us. But maybe there is some benefit for the working group that statistics look better if some specs are not there? In that case I can understand why it makes sense to do some bureaucratic shuffling around of documents, and in that case I just think it's important that we are not affected by it in any substantial way.

-- 
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#issuecomment-438547410