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

Enable AB/TAG to remove one of their members #986

Merged
merged 1 commit into from
Mar 26, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 24 additions & 1 deletion index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1322,15 +1322,38 @@ Verifiable Random Selection Procedure</h5>
The incomplete terms are assigned in result order.
</ol>

<h5 id="AB-TAG-removal">
Removing AB or TAG members</h5>

Individual participants of the [=Advisory Board=] or the [=Technical Architecture Group=]
can be <dfn export lt="remove|removal">removed</dfn> from those groups
if they are found by their peers
to be grossly neglecting their duties,
or to be acting in a way that seriously hampers the group's ability to function normally.

A chair of the [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be explicit detail here about who is invited to that hearing; both who must be invited (I'd expect the relevant body, including the individual) and who is allowed. Also, whether this is publicized or not. (I would expect not, but it shouild be explicit that it's confidential, perhaps?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

created #1007 to follow up on that

on the potential [=removal=] of a participant
if requested by at least three of the participants in the group.
After giving the individual in question
an opportunity to defend themselves,
a vote on the proposed [=removal=] is held.
If at least three quarters of the participants in the group,
excluding the individual who is the subject of such vote,
then vote in favor of the proposal,
the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
Comment on lines +1332 to +1343
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "holding a different opinion" or "preventing a Council from reaching a decision by vote" potentially something that could be considered "hampering the group's ability to function"?

If so, I'd be (a tiny bit) concerned about an in extremis potential abuse of this mechanism to evict an AB or TAG member in order to remove them from a Council (assuming that the opportunity for dismissal had passed) in order to unlock a Council vote.

It's complex to do the maths on this but I suspect that there could be a scenario in which a majority of a Council could not be found but a three-quarters majority of the AB or the TAG could be found to remove one of them.

For practical purposes, this is a highly theoretical, i.e. unlikely to ever happen, matter of minutia, so doesn't seem like reasonable grounds for blocking the PR, but it would be good to know if anyone did work through the voting numbers given this three quarter majority requirement, and other contexts in which AB or TAG might participate in votes.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nigelmegitt I'd refer you to the documentation on Councils, as the situation you describe would not really make sense in the context of how councils are run. It's entirely possible for a council to proceed if someone (or multiple people but not enough to amount to overturning a vote) holds a minority opinion. You can find the details here: https://www.w3.org/policies/process/20231103/#council-deliberations

If someone decided to be so disruptive to any AB/TAG process, council or otherwise, that the bodies couldn't conduct their expected responsibilities, that seems to be a valid premise to initiate this procedure. For it to pass, there is still the requirement of 3/4 of the group voting in favour, which is a significant bar. I'd add that in the case where someone is this disruptive, there is an impact on the membership as well, even if the membership did vote for them.

The minutes for today aren't available yet, but I will share what I said in support of this change: this is an edge case, and hopefully the most edgy of cases. There are a million steps that come before a decision like this, and I hope we never have to use it, but it is good to have it in the situation where we need it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another observation:

Membership of each Council instance is fixed at formation,

Making someone not be a AB/TAG member anymore doesn't remove them from the council. Now, it would possible to form a new council without the excluded individual(s) by using the following provision:

However, if participation in a Council falls so low as to hinder effective and balanced deliberations, the W3C Council Chair should dissolve the Council and call for a new one to be convened.

but if that's just to get rid of a person or two, that wouldn't be a case of "falls so low as to hinder effective and balanced deliberations", and would be pretty solid grounds for escalation / appeal.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's entirely possible for a council to proceed if someone (or multiple people but not enough to amount to overturning a vote) holds a minority opinion.

@wareid Sure, but that's a slightly different scenario. I am considering if the Council is split, and removal of one person causes their opinion to become a minority opinion. And the point is that a Council has a different membership to either TAG or AB on their own, so TAG or AB could hypothetically remove someone even if their removal would not have happened had that decision been made by the collective members of the Council.

However @frivoal makes a good point that removal from TAG/AB doesn't imply removal from a currently operating Council, which has its own distinct removal mechanism.

Is it worth raising an issue to clarify that removal of a member from TAG/AB does not remove them from any Council of which they are currently a member? At the moment this is implied by omission, but it could be noted explicitly for the avoidance of doubt.

I completely agree this is an exceedingly edgy edge case, and as I noted, more a question of wanting to know someone thought this sort of scenario through, rather than blocking the PR. Which we now seem to have done in this thread 😀.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree this is worth clarifying.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's follow up about this aspect in #1006


<h5 id="AB-TAG-vacated">
Elected Groups Vacated Seats</h5>

An [=Advisory Board=] or [=TAG=] participant's seat is vacated when:
An [=Advisory Board=] or [=TAG=] participant's seat is <dfn lt="vacated|vacant">vacated</dfn> when:

<ul>
<li>
the participant resigns, or

<li>
the participant is [=removed=], or

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it not the intent that this would replace the ability below (in lines 1362-1366) for the CEO to dismiss the participant? I would have expected those lines to be removed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I strongly object.

It's one thing to create a supplemental mechanism for one body to remove one of their members, to prevent a situation that has yet to happen, as a way to afford multiple paths to resolving problems so you aren't bottlenecked on one single path, and it's another thing entirely to strip the existing authority. This was presented in the 20 March AB meeting as a supplemental mechanism.

Furthermore, W3C has a Board of Directors who oversees the CEO and their actions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how this was presented as a supplemental mechanism - the minutes haven't been released yet so I can't link to them, but I said "I am def in favor of switching this to AB itself managing", and there were several others who I thought agreed.

How is the Board (who have precisely this 3/4-vote-of-its-own-membership-to-eject rule) and their oversight of the CEO relevant?

Or maybe more to the point: in what case would it be critical for the CEO to be able to eject an AB member, without the support of 3/4 of the rest of the AB?

<li>
an Advisory Board or TAG participant changes affiliations
such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
Expand Down