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

W3C Council should be limited to one vote per member organization #327

Closed
dwsinger opened this issue Sep 10, 2019 · 8 comments
Closed

W3C Council should be limited to one vote per member organization #327

dwsinger opened this issue Sep 10, 2019 · 8 comments
Assignees
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling
Milestone

Comments

@dwsinger
Copy link
Contributor

forked from #293

should we require that there is only one vote per member on the council, in the case that a member has more than one representative on the Council? (This might happen due to AB+TAG or in the relaxation of TAG rules over change of affiliation)?

There are cases where a member has 3 votes (when the relaxed TAG rule means that they temporarily have two TAG members, and they also have an AB member).

@fantasai
Copy link
Collaborator

If it comes down to a formal vote, yeah, I think it makes sense to have this restriction.

@dwsinger
Copy link
Contributor Author

Change

Decision of the W3C Council should be unanimous. If despite careful deliberation the W3C Council is unable to reach consensus, the Chair of the W3C Council may instead resort to voting. In that case, the decision is made by simple majority, with the Chair of the W3C Council breaking ties.

to

Decision of the W3C Council should be unanimous. If despite careful deliberation the W3C Council is unable to reach consensus, the Chair of the W3C Council may instead resort to voting. In that case, the decision is made by simple majority, with the Chair of the W3C Council breaking ties. A W3C member that has more than one representative on the W3C Council (e.g. because they have both a TAG and AB representative) has only one vote.

@frivoal frivoal modified the milestones: Deferred, Director-free Mar 11, 2020
@frivoal frivoal added Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling and removed director-free labels Jul 1, 2020
@frivoal frivoal modified the milestones: Director-free, Deferred Jul 1, 2020
@cwilso
Copy link
Contributor

cwilso commented Aug 13, 2020

If there is a consensus that multiple Council reps with the same affiliation should not have separate votes (FWIW, I disagree, as both TAG and AB members are supposed to be serving independent of their affiliation, but my disagreement is not an Objection) - the process should simply prevent such same-affiliated members from getting selected to the Council, because otherwise their votes will always be nullified.

@fantasai
Copy link
Collaborator

fantasai commented Jan 14, 2021

@cwilso The Council largely works by consensus, this is just about formal votes. It doesn't mean that both members can't have a say in what's happening. (Note, we apply the same rules to WG participation.)

Wrt “because otherwise their votes will always be nullified”, they don't get nullified unless the two reps from the same company can't agree on which way to vote.

@dwsinger
Copy link
Contributor Author

I think we need to be super-careful about the appearances here. I really hope that voting is rare on the council, but if there is dissent and a vote is needed, I fear we need to be scrupulous to avoid even a whiff of anything. I completely agree with what Chris says about the participants being individual experts, but an organization that pays their salary may be behind them, and we can't ignore that that may have some influence (as well as normal loyalty to one's employer).

@jeffjaffe
Copy link

I agree that we need to be careful about appearances so I support limiting each organization to a maximum of one vote per council.

@frivoal
Copy link
Collaborator

frivoal commented Jan 16, 2021

I think it is fine for two members of the council to come from the same org, and it is fine for both these people to express opinions. There's not particular need to require them to speak with one voice. In the end, we hope the council will come to consensus, and when everybody agrees, it doesn't particularly matters how many people are in agreement: it's all of them. If we fail to have a consensus, need to vote, and these two people from the same organization vote in different ways, that's also not really a problem. It's unfortunate when any two members disagree, but there's nothing particularly concerning about them coming from the same company.

The only problematic case is when we lack consensus, need to have a vote, and they both vote the same way. If we end up on one side of a threshold when counting both, but on the other side had we counted only one, there could be an appearance that one company is having excessive influence.

So:

If the council needs to resort to a vote, and if two members of the council who share the same affiliation cast an identical ballot, then for the purposes of evaluating whether a majority has been reached, their ballots count as a one vote, not two.

@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
Copy link
Collaborator

frivoal commented Sep 22, 2022

@frivoal frivoal closed this as completed Sep 22, 2022
@frivoal frivoal added Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion and removed Needs proposed PR labels Sep 22, 2022
@frivoal frivoal modified the milestones: Deferred, Process 2022 Sep 22, 2022
@frivoal frivoal added Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice and removed Commenter satisfied/accepting conclusion confirmed as accepted by the commenter, even if not preferred choice labels Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Accepted The issue has been addressed, though not necessarily based on the initial suggestion Director-free (all) All issues & pull request related to director-free. See also the topic-branch Director-free: FO/Council Issues realted to the W3C Council and Formal Objection Handling
Projects
None yet
Development

No branches or pull requests

5 participants