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
WebPlat charter: Confirming consensus #152
Comments
We already post CFCs on Github, with a "Notice of CFC" email sent to the relevant email list. Recognising this practice in the charter seems like a good idea to me. |
We currently also allow decisions to be taken and advised through the minutes - should the text
be changed to state that "decisions" taken in synchronous meetings must be confirmed by a CfC? There is a tension with the "edit-first, seek forgiveness" work mode, and with the sense that people don't want to re-hash old discussions because someone didn't notice them at the time - but that poor decisions should of course be revisited. I suggest that any change we make clarify that by "decision" we mean "Working Group decision to resolve an issue", not just ordinary proposed changes to specs, which can be revisited. Suggested text or a PR would be helpful. |
I think the intention of this feedback is to prevent resolutions made at meetings going by unnoticed by the rest of the WG because they're buried somewhere inside (often lengthy) minutes. I don't get the impression the intention is to turn every editorial decision into a production. |
We could revise the work mode document to clarify this, but doing it in the charter seems like a worthwhile exercise. I propose we change this:
To:
|
Fix #152 Clarify process for decision resolution, add CTA WAVE as a liaison
Feedback from the AC review:
The charter states that consensus on decisions taken on calls or at meetings is provisional until confirmed online, when the decision is shared via the meeting minutes. This is insufficient because meeting minutes are easily missed. A clear message with an appropriate title ("CFC for XYZ" for example) should be required.
The text was updated successfully, but these errors were encountered: