Re: [w3c/editing] Move execCommand to WICG (#184)

> Point of clarification: there would not be a "newly created" anything. The repo merely just gets moved over to the WICG organization here on Github. 

Ok, so then it will be harder to find. Right now we are occupying github.com/w3c/editing for editing-related work and github/w3c/input-events for the one spec that is sufficiently developed to go through the W3C process. Instead of moving execCommand out of github.com/w3c/editing where it can easily be found, can we not just say that the editing folder is shared by the editing taskforce that is connected to the webapps group and the WICG? We could add some explanation on the frontpage of github.com/w3c/editing saying that only some of these are related to the webapps working group and the other ones we are working on outside of the webapps working group.

I understand that you may have some requirement about spec counts, etc. for the working group from somewhere up in the system. But it would be good if that could be handled in a way that affects the editing taskforce as little as possible. 

> I respectfully disagree with Chaals - which is why I'm rewriting the charter for the new Web Apps WG to be more focused on trying to get specifications to Rec.

Ok, so this is a change because you are changing the statutes to introduce this requirement? Or is there some other entity behind this requirement? If it's only you, I'd suggest you just drop the requirement as it doesn't fit with our reality. If some other entity is really behind this (finance department,. etc.) then I hope we can find a solution that is disrupting our work as little as possible.

-- 
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/184#issuecomment-437816401