[w3c/webcomponents] Close this repository in the future (#652)

Given that the actual spec update has been happening recently in [WHATWG DOM Standard repository](https://github.com/whatwg/dom)  and [WHATWG HTML Standard repository](https://github.com/whatwg/html) , I am feeling that there is a kind of duplication (or redundancy) if we continue to keep this w3c/webcomponents repository's all functionalities. This repository has acted its role, but we might re-consider this repository's role now.

Regarding spec discussion:
- Shadow DOM: Use [DOM Standard repository's issues](https://github.com/whatwg/dom/issues), basically
- Custom Elements: Use [HTML Standard repository's issues](https://github.com/whatwg/dom/issues), basically
- HTML Imports: This is *Chrome-specific* feature. It might be better to [file a bug for Blink](http://crbug.com).
- HTML Modules: It might be okay to use this repository, but that doesn't have to be here, I think.

I don't have any concrete idea how to migrate issues to WHATWG Standard repository, but I don't think we have a lot of of important files bugs which need to be migrated.

Regarding W3C version specs:
- Until the situation becomes clear (and/or all things are upstream-ed), we should keep and maintain them somehow. [Shadow DOM](https://w3c.github.io/webcomponents/spec/shadow/), [Custom Elements](https://w3c.github.io/webcomponents/spec/custom/)


-- 
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/webcomponents/issues/652

Received on Tuesday, 25 July 2017 05:37:40 UTC