-
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
Closing wg #212
Closing wg #212
Conversation
It's not part of this PR but, imho, we should move the Team internal doc on closing wg under process/tilt/ since Group closure request should get reviewed there. |
Co-authored-by: ianbjacobs <ij@w3.org>
Co-authored-by: ianbjacobs <ij@w3.org>
We could, yes. |
Co-authored-by: ianbjacobs <ij@w3.org>
Co-authored-by: ianbjacobs <ij@w3.org>
Co-authored-by: Philippe Le Hegaret <plh@w3.org>
Co-authored-by: Philippe Le Hegaret <plh@w3.org>
Co-authored-by: ianbjacobs <ij@w3.org>
I just raised an issue against the Process Document, asking that Closing a group require a Team Decision (which can be appealed by the AC) rather than a W3C Decision. |
|
||
<h2 id="early">Early closure</h2> | ||
|
||
<p>Exceptionally, a group may be closed before it has completed its work:</p> |
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.
This seems to be at odds with the W3C Process: the W3C Process identifies causes to clause a group before the end of its chartered duration, which is often orthogonal with having completed its work.
The documentation on closing a WG was Team-only, there was nothing Public.
Process 2023 adds requirements (AC review, W3C Decision) for early closure.
The Team-only page remains, it has a different audience and is more about implementing group closure than deciding to close.