-
Notifications
You must be signed in to change notification settings - Fork 30
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
Initial stab at living CR/REC #151
base: main
Are you sure you want to change the base?
Conversation
Note this related thread re charter language: w3c/charter-drafts#275 |
@plehegar meta-remark: under the 'Reviewers' section (at the top of the left pane), you have a link to "Convert to draft" this PR. It will be explicitly marked as a draft, and I guess that the merge button will not be available. |
Co-authored-by: Nigel Megitt <[email protected]>
I think I addressed the initial feedback (thank you @nigelmegitt ). I feel more comfortable asking for feedback from a wider audience now (team and process CG, then Chairs) |
Co-authored-by: Wendy Seltzer <[email protected]>
Co-authored-by: chaals <[email protected]>
Co-authored-by: chaals <[email protected]>
Co-authored-by: chaals <[email protected]>
Co-authored-by: chaals <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional improvements
Co-authored-by: chaals <[email protected]>
Co-authored-by: chaals <[email protected]>
It would be useful to characterize when one "uses" living CR and when one uses REC. For example, if a spec is destined to be used by a regulatory body, or used by vendors to pour silicon to put it into a chip - you really need a REC. If you are working on spec-text that rapidly evolves on an annual basis, it may be preferable to use living CR. |
(this is work in progress)