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
Refactor Group/Chair Decision Appeal and Formal Objection sections #643
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frivoal
added
Agenda+
Marks issues that are ready for discussion on the call
Director-free: FO/Council
Issues realted to the W3C Council and Formal Objection Handling
Director-free (all)
All issues & pull request related to director-free. See also the topic-branch
labels
Sep 23, 2022
Based on the changes introduced by the director free project and introduction of the Council, these are no longer meaningfully different. Merging them makes the Process shorter, easier to understand, and reduces the amount of specialized terminology we need to introduce.
frivoal
force-pushed
the
merge-fo-and-decision-appeals
branch
from
September 30, 2022 09:29
cded6da
to
c3f8cf9
Compare
in the past, the Director was allowed to be delayed the processing of formal objections until a transition. this change puts a clock rather than a transition. |
The Revising W3C Process CG just discussed The full IRC log of that discussion<fantasai> Subtopic: Refactor Group/Chair Decision Appeal and Formal Objection sections<fantasai> github: https://github.com//pull/643 <fantasai> florian: This one noticed that we had a few sections next to each other that felt better refactored <plh> q+ <fantasai> ... in particular because we had both the notion of a group decision appeal and of a formal objection <fantasai> ... which might have different roots in history of how W3C worked <fantasai> ... but in practice work exactly the same <fantasai> ... have a decision, objection, goes to Council <fantasai> ... so instead of 2 things that do the same, we merged these two appeal paths and called them formal objections <fantasai> ... and also did some editorial rearranged to make things more clear <plh> fantasai: informally, we refer to both of this concept as formal objections <plh> ack hpl <fantasai> ... so this brings Process inalignment with how we discuss <fantasai> plh: Need to adjust something <fantasai> ... Group Decision while the WD was in progress <fantasai> ... FO could be delayed until the transition request <fantasai> ... and in the absence of that transition, Director could sit on it <florian> q+ <fantasai> ... If you change this to FO, then you're forcing the clock, instead of waiting for Transition <fantasai> ... the Team has 90 days to try to resolve the FO by consensus, otherwise has to bring it to the Council <plh> ack plh <plh> ack florian <fantasai> ... so that's a significant change, we can't delay anymore the FO processing until Transition request <fantasai> florian: Useful point, but regardless, this doesn't erase that disticition <fantasai> ... that's been erased by prior work on the Council <fantasai> ... so since now no longer useful to have two terms, merge them <fantasai> ... but yes, you're right, historically one required immediate action and the other didn <jeff> q+ to ask about 90 days and also Issue #1 <fantasai> florian: This is btw related to first thing we discussed, "I want to block but don't going to" is a possibility <fantasai> ... gives WG time to work through the disagreement <fantasai> ... without filing FO <fantasai> ... and then can file an FO later <plh> ack jeff <Zakim> jeff, you wanted to ask about 90 days and also Issue #1 <fantasai> jeff: This forced me to reread 5.6 <fantasai> ... would like to take a minute to talk about 2 issues not directly related to PR <fantasai> jeff: First, wrt 90 days that Team has to form Council <plh> --> https://www.w3.org/Consortium/Process/Drafts/#WGArchiveMinorityViews 5.6 Recording and Reporting Formal Objections <fantasai> ... what happens if after 88 days we're almost at a breakthrough, but ran out of time? <fantasai> ... and talked about idea of the Team being committed to ask for additional time <fantasai> ... has that come up as an issue <fantasai> florian: Hasn't come up as a separate issue, but in order to ask Council have to form it <fantasai> ... around 90 day barrier have to form the Council, the Council can then say so <plh> jeff: so the Council is allowed to send it back to the team? <plh> fantasai: yes <plh> ... see separate pull request <fantasai> jeff: Paragraph to make consensus work, that goes away? <fantasai> florian: Yes, because we fixed that earlier <plh> fantasai: ok to merge? <plh> Resolved: Merge https://github.com//pull/643 |
frivoal
added
Closed: Accepted
The issue has been addressed, though not necessarily based on the initial suggestion
and removed
Agenda+
Marks issues that are ready for discussion on the call
labels
Oct 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Closed: Accepted
The issue has been addressed, though not necessarily based on the initial suggestion
Director-free (all)
All issues & pull request related to director-free. See also the topic-branch
Director-free: FO/Council
Issues realted to the W3C Council and Formal Objection Handling
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the changes introduced by the director free project and introduction of the Council, Group/Chair Decision Appeal and Formal Objection are no longer meaningfully different. Merging them makes the Process shorter, easier to understand, and reduces the amount of specialized terminology we need to introduce.
Preview | Diff