[documentreview] Wide review for registries?
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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