-
Notifications
You must be signed in to change notification settings - Fork 18
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
Identifying CG or IG topic areas #330
Comments
The scope of the IG charter also states "Reach out and collaborate with interested organizations, industry specific and infrastructure vendors, and communities in support of the Interest Group's mission". From my understanding the W3C CG will eventually not run under the new created non-profit. Once the non-profit is formed. The W3C can't provide the resources in order to maintain a chat system etc. That's why we should run these parts under the CG. While the CG has "reaches out and supports the development of a community not represented by the W3C WoT WG." Something along that line. What do you think @egekorkan @relu91 ? |
I think I agree but I am not sure understand every point properly. It would be difficult that a CG represents a WG given the political problems that it might cause. |
I think this conflict with the IG that you pointed out also in the marketing call, might confuse people and we should somehow sort it out.
What he is saying is that the IG should represent the WG while the CG will be a separate entity. I am ok with this differentiation as long as "the product" brand (i.e., Web of Things standards) will be consistent among the different groups. |
Exactly. I agree with the part that it makes sense to be more involved in communities. And potentially having a matrix server etc.
Good point. If we provide services etc. it has to be clear it's compatible with the WoT standards, but not a service by the W3C. |
With the new WoT CG charter, we should discuss what topic areas should be moved to CG:
Opinions of people so far:
The text was updated successfully, but these errors were encountered: