clarify understanding of all WCCG adjacent repos and orgs

[thescientist13]

Overview

Coming out of one our recent meetings and touched upon as part of our ongoing process ideation thread, the question arose of what all the WCCG related / adjacent repos and orgs are for and how they are involved in our activities as the WCCG.

Here are the related repos, with my best guess where possible.

Repo / Org	Description	Organization	My Notes
w3c/webcomponents-cg (the one we're in right now!)	Web Components community group	W3C	Used for our related W3C activities, like TPAC prep
WICG/webcomponents	Web Components specifications	WICG	Proposals for the web platform ( ❓ )
https://github.com/webcomponents/ (org)		WebComponents	Hosts sites and projects like webcomponents.org, custom-elements-everywhere.com, and custom elements manifest
https://github.com/webcomponents-cg (org)		WebComponents-CG	Hosts projects / initiatives like Community Protocols and docs / guides

Thoughts / Observations

1. Seems like one quick win is to at least get descriptions into the WebComponents and WebComponents-CG organizations, just to at least clarify their motivations as of today, regardless if anything comes out of this particular audit
2. What's the difference the WICG repo and going directly to a standards org like the W3C repo? Is it analogous to our community protocols repo, but for more viable things that could potentially become web standards? And so... 👇
3. Is the goal with WICG proposals that they eventually land in a WHATWG repo, for example?
4. Who owns the WebComponents org? Is it Google?
5. Was WebComponents-CG org created to be a community companion to the WebComponents org, perhaps? Seems like these two have the most overlap and org ownership aside, could be consolidated?

---

Please feel free to answer / comment / correct down below and I will live update this issue as we go. ✍️

[michaelwarren1106]

my first question is more about the web component cg org. i figure that we at least need a repo for tracking and discussing things. do we the wccg also need an org as a home to put more things?

[Westbrook]

WCCG repo: a home for centralizing the community needs and wants around API and features to present them to implementors with a unified voice.

WCCG org: where things that likely won't make it into standards live.

WC repo in WICG: where community interest and needs meet implementor understanding of their respective browsers and grows into actual proposals/spec for promoting to CSS, HTML or DOM.

WC org: originally a Google project, still one, where documentation and polyfills for various things live but with vague amounts of access for non-Google community members.

[michaelwarren1106]

so it seems like the low hanging fruit might be to start distancing from the WC org since it’s google owned, and the community has increasingly less googler members.

that seems like an me easy way to slim things down by moving/copying whatever we need from the WC org to elsewhere? maybe the wccg repo?

[Westbrook]

In and out seem to have similar ownership issues in the WC org but that’s an interesting solution.

[JRJurman]

It would be valuable in the table above to list what permissions we / others have, since that feels like an important thing to capture, especially if those permissions would limit our ability to do things in those spaces.

Additionally, I stumbled on this recently, might be a good reference point for previous conversations about some of the repos and attempts to close / move them (7 years old at this point) - WICG/webcomponents#652

[thescientist13]

Good call @JRJurman . From my naive insight, I think that it's just the webcomponent-cg organization we "own"?