unclear wording in charter about proposals being (?) specifications

Open
#98 5 comments 0 reactions 1 assignee View on GitHub

@cwilso is already working on this.

Since Oct 5, 2022.

Assessment

This issue has not been assessed yet.

Description

Incubation Process

The WICG charter in the section on Community and Business Group Process and Patent Policy contains the text:

As with other Community Groups, W3C seeks organizational licensing commitments under the W3C Community Contributor License Agreement (CLA) (Proposals in this Community Group charter are applicable "Specification" in the CLA).

It's not particularly clear what this parenthetical means. What I hope it means is that any proposal (for example, an explainer) counts as a "Specification" in the terminology of the Community and Business Group Process, particularly where it says:

The label “Community Group Report” refers to any document produced by a Group. Some Community Group Reports are Specifications. The following rules apply to Specifications:

  • drafts are governed by Community Contributor License Agreement (CLA). W3C will provide a template for including copyright information.
  • they must include the name the group that published the deliverables and link to a public page about the group.
  • they must include a publication date.
  • the history of Contributions (as defined under the CLA) must be archived permanently on the W3C Web site.
  • They must include boilerplate language required by W3C (e.g., notice that Contributions are made under the CLA and that certain conditions apply).
  • When published on the W3C site, they must not violate the W3C Privacy Policy.
  • The content and style of the Specification must not cause confusion about its status, in particular with respect to W3C Technical Reports.

... and later:

Other types of deliverables must be publicly available and must be archived permanently.

It would be helpful if this sentence were clearer; it's not clear what "are applicable" means in this context.

Dominant language
HTML
Stars
60
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WICG/admin

All issues in WICG/admin

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.