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

Filling appointed TAG seats that have been vacated #311

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

Filling appointed TAG seats that have been vacated #311

mnot opened this issue Aug 9, 2019 · 11 comments
Labels
Closed: Invalid Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Director-free (all) All issues & pull request related to director-free. See also the topic-branch
Milestone

Comments

@mnot
Copy link
Member

mnot commented Aug 9, 2019

In the Directorless branch:

When an appointed TAG seat is vacated, the TAG Appointment Committee appoints a replacement.

This doesn't say which TAG Appointment Committee does so; is it the one that originally appointed that person, the last operative TAG-AC, or a newly formed one?

@dwsinger
Copy link
Contributor

I think a new one has to form at that time. They are episodic and don't exist between elections, normally.

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

This is covered as @dwsinger says in the 2nd paragraph of https://w3c.github.io/w3process/director-free/#tag-appointment-committee

I think the confusion comes from a lot of "the" instead of "a". I'll ask @frivoal to fix those...

@frivoal
Copy link
Collaborator

frivoal commented Sep 11, 2019

Done. Please reopen if that's not good enough for some reason.

@frivoal frivoal closed this as completed Sep 11, 2019
@mnot
Copy link
Member Author

mnot commented Sep 11, 2019

Just for reference / context; the IETF does it slightly different with the NOMCOM. There's always at least one sitting NOMCOM, and the rules for determining which is used are documented here:
https://tools.ietf.org/html/rfc7437#section-3.5

AIUI the thinking is that by using the same people that made the original appointment, you're more likely to get continuity / context.

@frivoal
Copy link
Collaborator

frivoal commented Sep 11, 2019

I guess that is another possibility.

However, the IETF NOMCOM has more bodies to nominate people onto, so it is already expected that its members will have to work at multiple nomination events, and adding just one more doesn't seem to be a problem. Here, most of the time, we expect to need it once a year for a single body, and only more often if TAG participants vacate their seats. We could keep it open until the next one is formed, but most of the time that would make no difference, and for the few times where it would, I'm concerned concerned that confirming that the people who were on it for the intial round are still available for the new round isn't less work that forming a whole new NOMCOM.

@frivoal frivoal added this to the Deferred milestone Mar 11, 2020
frivoal added a commit to frivoal/w3process that referenced this issue Jul 2, 2020
Helps clarify w3c#311
@mnot
Copy link
Member Author

mnot commented Feb 15, 2021

However, the IETF NOMCOM has more bodies to nominate people onto, so it is already expected that its members will have to work at multiple nomination events, and adding just one more doesn't seem to be a problem.

Not really; a NOMCOM makes all of its (normal) nominations at the same time.

@samuelweiler
Copy link
Member

...We could keep it open until the next one is formed, but most of the time that would make no difference, and for the few times where it would, I'm concerned concerned that confirming that the people who were on it for the intial round are still available for the new round isn't less work that forming a whole new NOMCOM.

@mnot addressed part of this (quite correctly); I'm going to take on another piece.

I'm not worried about "confirming availability" - spinning up a new nomcom would necessarily involve that same step - plus quite a bit more. (And in my experience of serving on more than one IETF nomcom, "making sure people are (still) available" is not a huge deal. Spinning up a new nomcom is (at least in their process) quite a bit heavier-weight - and slower.)

@dwsinger
Copy link
Contributor

However, the IETF NOMCOM has more bodies to nominate people onto, so it is already expected that its members will have to work at multiple nomination events, and adding just one more doesn't seem to be a problem.

Not really; a NOMCOM makes all of its (normal) nominations at the same time.

Now I am confused. You're saying that the IETF NomCom stands until the next one forms, to deal with resignations and off-cycle replacements, and then you say that it makes all its nominations at the same time.

We only have a few TAG seats. Mid-cycle resignations are moderately rare. The committee doesn't form if the election is within 2 months, and in the remaining 10 months we can choose any TAG participant since none are up for re-election/re-appointment.

Eligibility and willingness to serve may have changed, as well. I suppose we could say after

When formed to fill vacated seats out of a regularly scheduled election, a TAG Appointment Committee is formed as soon as possible after the seat is vacated, unless a regular Call for Nominations is scheduled within 2 months.

that

The initial composition of the appointment committee in this case is the membership of the prior appointment committee, adjusted as needed to compensate for those no longer available, eligible, or willing to serve.

I'd be OK with that.

frivoal added a commit to frivoal/w3process that referenced this issue Jul 21, 2021
Helps clarify w3c#311
@frivoal frivoal added the Director-free (all) All issues & pull request related to director-free. See also the topic-branch label Jul 28, 2021
@frivoal frivoal modified the milestones: Deferred, Process 2022 Jul 28, 2021
frivoal added a commit that referenced this issue Oct 7, 2021
Helps clarify #311
frivoal added a commit that referenced this issue Jul 13, 2022
Helps clarify #311
@frivoal
Copy link
Collaborator

frivoal commented Mar 2, 2023

(Tagging as invalid, as this issue is no longer relevant: the TAG Appointment Committee it was about is no longer our approach to TAG nominations)

@frivoal
Copy link
Collaborator

frivoal commented Mar 3, 2023

@mnot as you opened the issue, I'd like to confirm: are you OK with this issue being closed, for the above reason?

@mnot
Copy link
Member Author

mnot commented Mar 3, 2023

Well, it appears to be overcome by events, so I suppose yes.

@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter Response Pending labels Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Invalid Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice Director-free (all) All issues & pull request related to director-free. See also the topic-branch
6 participants