Streamline Council formation and provide safeguards #925
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
A major source of dissatisfaction with the current Formal Objection handling process is the time it takes to initiate Councils. This brings the following improvements: * This makes it clear that the administrative steps for forming a council are expected to happen in parallel with the Team's effort to resolve and/or document the objection, which should cut the waiting time (and matches what the Team is moving towards anyway). * Currently convening a Council *must* start within 90 days of FO registration, and *should* be complete within an extra 45 days. not only is this long, it means there is no actual hard end date. After this change, the hard deadline is 90 days. * Previously, nothing happened if the deadlines were exceeded. This empowers the AB and TAG chairs to complete council formation once we're past the deadlines.
frivoal
added
the
Director-free: FO/Council
TallTed
suggested changes
Oct 7, 2024
fantasai
approved these changes
Oct 8, 2024
TallTed
reviewed
Oct 8, 2024
tantek
approved these changes
Oct 9, 2024
There was a problem hiding this comment.
Thanks for these process streamlining improvements. LGTM as-is, and I am also ok with the variants of suggested edits, leaving them up to the judgment of the Editor as to pick and choose which suggestions help most clearly communicate the intent and function of this part of the Process.
|
The Revising W3C Process CG just discussed
The full IRC log of that discussion<fantasai> Subtopic: Streamline Council formation and provide safeguards<fantasai> github: https://github.com//pull/925 <fantasai> fantasai: Anyone with general comments? <fantasai> [Tantek has marked approval in the issue] <fantasai> Moving on to discussion about phrasing. <fantasai> [Discussing making a new subsection for convening the council and starting the deliberations section at the following (untouched) paragraph] <fantasai> PROPOSED: Accept this PR in principle and allow Florian to make wording tweaks as he sees fit; further tweaks can be follow-ups. <fantasai> RESOLVED: Accept this PR in principle and allow Florian to make wording tweaks as he sees fit; further tweaks can be follow-ups. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
frivoal
added
the
Closed: Accepted
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A major source of dissatisfaction with the current Formal Objection handling process is the time it takes to initiate Councils. This brings the following improvements:
Preview | Diff