Skip to content
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

Closed
mnot opened this issue Aug 9, 2019 · 9 comments
Closed

Team-Appointed TAG Chair(s) #313

mnot opened this issue Aug 9, 2019 · 9 comments
Labels
Closed: Rejected Commenter Timed Out (Assumed Satisfied) Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C
Milestone

Comments

@mnot
Copy link
Member

mnot commented Aug 9, 2019

In the directorless branch:

Participants in the TAG chose by consensus their Chair or co-Chairs; in the absence of consensus, the Team appoints the Chair or co-Chairs of the TAG.

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?

@chaals
Copy link
Contributor

chaals commented Aug 10, 2019

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.

@dwsinger
Copy link
Contributor

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.

@jeffjaffe
Copy link

I think we can drop the tie-breaking clause, but I don't think it is a big deal either way.

@dwsinger
Copy link
Contributor

I suspect the existence of the clause makes it unlikely to be used; 'agree, or the team will step in and appoint'

@dwsinger
Copy link
Contributor

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")

frivoal added a commit to frivoal/w3process that referenced this issue Sep 11, 2019
@fantasai
Copy link
Collaborator

fantasai commented Sep 11, 2019

Agree with @dwsinger and @chaals that we should keep this clause.

(Happy to consider ways to break chairing continuity where needed, but that's a separate issue from whether to keep this backstop, since it applies to all chaired groups within W3C.)

@mnot
Copy link
Member Author

mnot commented Sep 11, 2019

Re chairing continuity, see #310.

@frivoal frivoal modified the milestones: Deferred, Director-free Mar 11, 2020
@frivoal frivoal added Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C and removed director-free labels Jul 1, 2020
@frivoal frivoal modified the milestones: Director-free, Deferred Jul 1, 2020
frivoal added a commit to frivoal/w3process that referenced this issue Jul 2, 2020
@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Jan 18, 2021
@frivoal frivoal removed the Agenda+ Marks issues that are ready for discussion on the call label Mar 24, 2021
@dwsinger dwsinger added the Director-free (all) All issues & pull request related to director-free. See also the topic-branch label Jul 26, 2021
@frivoal frivoal modified the milestones: Deferred, Process 2022 Sep 22, 2022
@fantasai fantasai added the Agenda+ Marks issues that are ready for discussion on the call label Oct 25, 2022
@fantasai
Copy link
Collaborator

Proposing to close this issue No Change, @mnot do you have any objection?

@frivoal frivoal added Closed: Rejected Commenter Response Pending and removed Agenda+ Marks issues that are ready for discussion on the call labels Oct 27, 2022
@frivoal
Copy link
Collaborator

frivoal commented Oct 27, 2022

Agreed to close in the 2022/10/28 Process-CG meeting.

@frivoal frivoal closed this as completed Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Rejected Commenter Timed Out (Assumed Satisfied) Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: TAG Appointments Issues related to appointing TAG members in a director-free W3C
Projects
None yet
Development

No branches or pull requests

7 participants
@mnot @frivoal @fantasai @chaals @jeffjaffe @dwsinger and others