-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we graduate this? #102
Comments
Is this just for moving this repo from WICG to CSSWG, or does this include merging the specs too? For the latter there's w3c/csswg-drafts#3433 too |
@rakina, I'm not sure to be honest. Whatever works best: moving the whole repo, or just taking "the best bits" and copy pasting them into an existing document, works. |
@rakina, thanks also for pointing me to the discussion - that's great to see happening! It's exactly the discussion I was hoping to happen here. When CSS is ready to take it, we can decide what to do with this repo. I'll subscribe to the other thread so I can follow along. |
Friendly ping! Any progress on moving this to CSSWG? |
We're very supportive of moving this to CSSWG, but candidly I'm really hoping @emilio is up for doing the work? |
It seems that both Google and Mozilla are behind this, so should we move this to the CSS WG?
cc @WICG/chairs
The text was updated successfully, but these errors were encountered: