You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Substantial portions of the proposed charter read like those of a CG, rather than those of a WG, and even refer to the group itself as a CG. Sections 7 to 10 of the charter should probably be rewritten, possibly starting from the charter template.
For example:
Specifications created in the Community Group must use the W3C Software and Document License. All other documents produced by the group should use that License where possible.
All GitHub repositories attached to the Community Group must contain a copy of the CONTRIBUTING and LICENSE files.
Meetings may be restricted to Community Group participants
In particular, sections 8, 9, and 10 are not appropriate for a WG:
encouraging forking in case of disagreement is typical for a CG, but WGs have different mechanisms to resolve and escalate disagreements.
The choice of chairs being at the discretion of the Group is typical for CGs, but unusual for WGs, where the Process expects that the appointment is made by the Team.
Allowing the WG itself to amend its charter goes against the Process, which empowers the AC through an AC Review to do that.
The text was updated successfully, but these errors were encountered:
Substantial portions of the proposed charter read like those of a CG, rather than those of a WG, and even refer to the group itself as a CG. Sections 7 to 10 of the charter should probably be rewritten, possibly starting from the charter template.
For example:
In particular, sections 8, 9, and 10 are not appropriate for a WG:
The text was updated successfully, but these errors were encountered: