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

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

No, because then they still sit in the w3c organization - and we only really want working group specs in the W3C org. Plus we keep the WICG ones in one place, and eventually pass them back to the W3C if they are going to be on the Rec track. 

I understand your position, but let's be pragmatic here... the editing specs are not a rapidly evolving set of specifications. execCommand hasn't been updated in a year, according to the below. The other specs range between 2-3 years since they've been touched, so it's not like it's disturbing some rapid moving task force (or am I looking at the wrong thing here?):

![screenshot 2018-11-12 21 04 33](https://user-images.githubusercontent.com/870154/48340395-a323b080-e6be-11e8-94c9-4a791ef9e174.png)

Additionally, GitHub also provides us with the ability to move issues, so even for those it won't cause much (if any) disturbance.  
 
> 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? 

You could say it's me and the W3C, in as far as I've been tasked to chair the group and make it more successful (we have a clearly defined success criteria: get specs to Rec). Part of that is evaluating the viability of various specs in becoming a web standard. As stated by the execCommand document itself, this has zero chance right now of becoming a W3C standard. When that changes, then it would be appropriate to have it be part of the working group.    

> If it's only you, I'd suggest you just drop the requirement as it doesn't fit with our reality. 

We are doing a reality check on all specs - might require some reality adjustments :) But that's what I'm here for, to help you through that.    

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

As, I said, I'm happy to help move things to make things as painless 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-437830250