Proposal for WoT WG and IG liaison

[egekorkan]

• This PR will be reviewed by WoT CG, IG, and WG before being merged.
• We should look into how other groups how they handle the relationship.

[relu91]

We should look into how other groups how they handle the relationship.

I briefly investigated how the Webassembly working group is working together with their corresponding CG. I reviewed:

• WG charter
• CG charter
• Github repositories: Webassembly design Webassembly spec.

Key takeaways:

1. The working group charter lists the CG as the place where to coordinate seed specification to begin the standards process.
2. The community group charter is very clear on how to contribute and their implications (See section Contribution mechanics. In particular, any substantial changes are bound to W3C COMMUNITY CONTRIBUTOR LICENSE AGREEMENT (CLA)
3. Both repositories refer to joining the CG as a required action before contributing. The Webassembly contributing md file even explicitly says: "Please join the W3C Community Group before sending pull requests: it provides the legal framework that protects the work in this repository"
4. After quickly reviewing CLA, I saw that section 9 regulates what happens when contributions from CG members are moved to REC documents, citing sections of the W3C Patent Policy. Section 3 regulates generic contributions in terms of Patents.

All and all it seems promising at least from my POV.

@mmccool @sebastiankb @ashimura

[egekorkan]

The reports that the CG can produce are documented at https://www.w3.org/community/reports/

[egekorkan]

Call of 07.11:

• We should mention that CG is a lower barrier of entry so that is a collaboration in a way. -> Change to charter to mention the role of CG
• For creating a use case, requirement, or binding, we can allow CG members to write it in md format in the beginning.
• Use Cases and Requirements will be CG Reports. Feature Request (as discussed in the TPAC) is out of scope since that requires a work item in the WG to exist. -> Change to charter
• Bindings can be DRAFT specifications (see WebAssembly CG Charter here) -> Change to charter
• Contribution to Test Cases: TDs, TMs can be submitted as test inputs for WG deliverables. We need to specify the level of quality we expect. This can be a new section under Test Suites and Other Software of the charter. -> Change to charter
• Feedback on Draft Specifications: Can be done any way desired such as GitHub issues, emails, chat.
• Outreach of WG Activities: Meetups and Events, Tutorials, and more.
• Joint Activities such as Plugfests: This has to be a joint activity where participants of all groups are welcomed. -> Change to charter

[egekorkan]

We have finalized it for review in the CG Internal Meeting of December 4th. An email will be sent to WoT CG and WoT IG/WG for feedback and resolution.

[lu-zero]

It seems good, maybe Low Entry can be changed to "Low barrier to access"