-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seek horizontal reviews on the spec #284
Comments
Thanks for opening this tracking issue. You're of course welcome to take the first stab at any of these questionnaires and checklists and request the group to review. (This reminds me, this list should actually be turned into an issue template. I've assembled a similar list manually for so many specs.) |
tidoust
added a commit
to w3c/documentreview
that referenced
this issue
Jun 7, 2021
This adds a button to the "How to get horizontal review" section to generate a meta-issue to track horizontal review steps in a GitHub repository, following a suggestion made by @anssiko in: w3c/openscreenprotocol#284 (comment) Some notes: - Taking that approach instead of creating an issue template, as I believe that the issue template would be seen whenever someone tries to create a new issue and the horizontal reviews issue will only be useful once or twice per specification. - Sub-details sections are not included because they would grow the length of the body beyond what can be passed to GitHub in a query string - To keep script simple, actual steps need to be made explicit by enclosing the prose for each step into a `<span class="step">` construct.
deniak
pushed a commit
to deniak/Guide
that referenced
this issue
Nov 7, 2024
This adds a button to the "How to get horizontal review" section to generate a meta-issue to track horizontal review steps in a GitHub repository, following a suggestion made by @anssiko in: w3c/openscreenprotocol#284 (comment) Some notes: - Taking that approach instead of creating an issue template, as I believe that the issue template would be seen whenever someone tries to create a new issue and the horizontal reviews issue will only be useful once or twice per specification. - Sub-details sections are not included because they would grow the length of the body beyond what can be passed to GitHub in a query string - To keep script simple, actual steps need to be made explicit by enclosing the prose for each step into a `<span class="step">` construct.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per charter, invitation for review of the spec must be issued after publication as First Public Working Draft. The How to do wide review document details practical actions that need to be taken. I'm creating this issue to track them:
The text was updated successfully, but these errors were encountered: