-
Notifications
You must be signed in to change notification settings - Fork 132
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
Team-Appointed TAG Chair(s) #313
Comments
In the hopefully unlikely case that the TAG doesn't reach consensus reasonably efficiently I think it is reasonable to have a shortcut mechanism. One of the things that happens without a consensus is that if there apparently is no chair, there is no obvious way to decide the discussion should stop and a decision be made (since doing that is reaching consensus). This therefore provides a forcing function - the team notes there is no consensus and appoints a chair, so any minority is going to go to the team to put their case anyway. That said, I am not sure the clause helps much. It ignores the social reality that there is a lot of pressure to accept an incumbent or "establishment-proposed" chair, and traditionally the actual chairs have been changed by "back-room wrangling". I expect that to continue to be the reality, making the mechanics of choosing a chair somewhat artificial in any case. |
There are ways of alleviating that. For example, 3GPP says a chair may only serve a third term if they are unopposed at the election. Any other nomination invalidates their nomination. |
I think we can drop the tie-breaking clause, but I don't think it is a big deal either way. |
I suspect the existence of the clause makes it unlikely to be used; 'agree, or the team will step in and appoint' |
I think we should keep the fallback. (And fix the typo, chose->choose "Participants in the TAG chose by consensus their Chair or co-Chairs") |
Mentioneed in w3c#313 (comment)
Re chairing continuity, see #310. |
Mentioneed in w3c#313 (comment)
Proposing to close this issue No Change, @mnot do you have any objection? |
Agreed to close in the 2022/10/28 Process-CG meeting. |
In the directorless branch:
This seems... needlessly paternalistic. I'd very much hope that the people who put their hands up to work on the TAG are mature enough to come to consensus on who will lead their discussions, rather than having it imposed by the Team.
Can't we just drop this clause?
The text was updated successfully, but these errors were encountered: