[documentreview] Title is about Wide Review, contents are about Horizontal Review
@swickr is already working on this.
Since Jun 8, 2021.
- Dominant language
- HTML
- Stars
- 84
- Forks
- 69
- Avg merge
- 14h 52m
- Merged PRs (30d)
- 2
Description
I'd like to see more clarity about the requirements for Wide Review here: the title is about wide review but almost all the content is only about the subset of Wide Review that is Horizontal Review.
As a general point, as per w3c/w3process#130 it would be good to document the process for handling review comments, and what kinds of responses are likely to result in a transition request being declined.
For example, if a responder says "I don't like the colour of the text in this document" and the WG ignores the comment, not even sending a response, is that okay? Or at the other end of the scale, if a commenter raises a detailed technical point, the WG considers and responds, and then the commenter remains unhappy with that response, is that okay?
What level of tracking of responses is required and what is merely good practice?
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.
Assessment
This issue has not been assessed yet.