-
Notifications
You must be signed in to change notification settings - Fork 130
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
Visibility of FO handling #870
Comments
Basically, I'm flexible on how we get there, but I support the principle that no FO should be followed by silence. Doesn't matter if it's overruled or sustained, doesn't matter if it's short circuit or delegation or whatever, if there is an FO, we must let people know how it was disposed. Some of this may already exist through various existing Process rules, but we may have holes to plug or other improvements to make. Let's look into it and fix whatever is missing. |
It's not clear to me that UPHELD is the correct state to record in the situation @tantek describes. The FO has been made moot, as the decision that was objected to has been un-made. It would be clearest to record that the FO was made moot. |
I the “[…] and the Team withdraws the charter” scenario, I agree that's not FOs being upheld, but being rendered moot. The broader point which I believe is right is that once an FO has been made, interested parties need to be able to figure out what has happened to it. That might take different paths depending on what has happened to it, but that should be discoverable, without excessively complicated research. |
Partly related to w3c/strategy#475 |
Forking a new issue from a comment by @tantek in #852 (comment):
The text was updated successfully, but these errors were encountered: