This page describes how to use GitHub labels, milestones, and projects in a uniform way across W3C specifications.
LabelsLabels describe the kind of issue or specific work that's needed to advance an issue.
Those labels are there to facilitate horizontal reviews.
- Affect the degree of resistance to, or protection from, harm of Web technologies.
- Affect the collection, processing and publication of personal data in Web technologies.
- Affect the design of Web technologies for people with disabilities.
- Affect the adaptation of Web technologies to different languages or regional differences.
- Affect the underlying principles that should be adhered to by all Web technologies.
- Affect the download and display speed of Web technologies.
- device independence
- Affect the ability of Web technologies to function on a wide variety of devices.
Testing and Implementations
Those labels are meant to track testing and implementation status.
- needs tests
- More tests will be needed in this area to exit the Candidate Recommendation state.
- needs implementation
- More implementation experience is needed in this area.
- More tests will be needed in this area.
- The reported issue can be addressed with an editorial change. This tag could be combined with others (except
- The reported issue will only be addressed with a substantive change. This tag could be combined with others (except
- The specification is broken or misleading and need to change.
- The specification works as-is but could be improved.
- help wanted
- The editor and/or Group need to resolve this issue.
- This issue or pull request was declared out of scope.
- This issue or pull request is a duplicate and will be closed if not already closed.
- This issue won't get addressed. Best is to combine this one with others, sich as
- This is used to track non-technical W3C Process related issues, such as transitions.
MilestonesMilestones describe the scheduling of bug fixes and changes. Often an issue is labeled with a particular milestone as a way to postpone work on it until after work needed for an earlier milestone.
- Resolve before experimenting with the new feature on general users.
- Resolve before migrating the spec from the WICG to a Working Group.
- Resolve before creating a First Public Working Draft.
- Resolve before advancing the spec to Candidate Recommendation.
- Resolve before advancing the spec to Proposed Recommendation.
- Resolve before advancing the spec to Recommendation.
- Work on these issues after the level-1 spec is complete.
- Work on these issues at an unspecified time in the future.
1-The WG processes the comment, and provides a resolution.
- Comment received, not yet processed by the WG
- Discussed but pending WG resolution
- WG resolution, (approved by WG)
- WG resolution and spec updated
- Partial WG resolution (partially approved by WG)
- Partial WG resolution and spec updated
- Comment Rejected by WG
For each comment, please fill a "type" with above labels
2-Once the WG has processed all comments, the next steps are to get approval from the commenter
For more information please refer to the TTWG wiki Wide Review page.
Note that groups may work on a level-2 spec concurrently with pushing the level-1 spec through the Recommendation process, so repositories may need milestones like "level-2-CR".