w3c / w3c/guide

[documentreview] Wide review for registries?

Open
#271 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
84
Forks
69
Avg merge
14h 52m
Merged PRs (30d)
2

Description

https://w3c.github.io/documentreview/#when_should_review_be_requested

When should review be requested?

  • For most documents, after a First Public Working Draft is published
  • Process-2019 requires wide review before a document is published at CR (Candidate Recommendation)
  • When a document is both reasonably stable and still flexible enough to allow changes where issues are identified
  • When new features are added after a document has already gotten wide review (perhaps requesting a review limited to the new features)

The Process Document says "Rules for publication and advancement on the Registry Track are identical to that of the Recommendation Track with the following exceptions".

I haven't seen any exceptions related to wide review, so I assume registries also need to be reviewed. If this is the case, can we also mention it in this document?

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.

Research direction

Start with the linked “When should review be requested?” section in the documentreview guide, then compare it with the Registry Track rules in the linked Process-20211102 document. Confirm whether wide review applies to registries and identify the appropriate wording or section to update. Done means the guide accurately explains the review expectation for registries.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.