Comments (13)
This looks like another issue that may or not reflect a real problem, and there is no obvious consensus on how to solve it if it is a problem. I suggest the Process CG to advise the AB to advise the Team to remove "No (other) candidate" from the election form. We have plenty of real problems that might possibly have consensus solutions to address.
from w3process.
I think Michael is right; if there is such an option in the election, then once "and no other candidate" is elected, that seat and all subsequent seats are vacant. This corresponds to the voters' choice. This, by the way, has another consequence: even if the number of candidates is equal to or less than the available seats, the election must be held, in case the electorate prefers "and no other candidate".
We could certainly makes these changes to the Process.
However, this raises two major questions:
- We are a 'small community'. The effect of telling some number of candidates "the membership thinks that leaving the seat vacant is better than having you elected" has to be assessed. This could easily be seen as insulting, and is likely to have a discouraging effect on standing in the first place; some are already offput by simply losing, and losing to an empty seat is much worse.
- What happens next? Is another election called, or are the seats vacant until the next regularly scheduled election? If another election is called, is it presumed that the rejected candidates would not stand again, or are they barred from re-standing for the same vacancy? How many rounds of re-try do we do?
The first is a community management question; the second is policy, and both well outside the remit of the Process CG. I think they should be referred to the AB (who might, in turn, choose to refer them to the AC).
There is a question about what should happen at elections until such time as these questions are answered. Should the option remain on the form in the absence of defined handling and in the absence of guidance on how to use it, and what it means, to the electorate (the AC)? I think it should not -- formal processes should not have the possibility of branching onto an undefined road. I am not sure whether it's the Process CG's job to give such advice to the team (remove the option until its meaning and handling, and the consequences of using it, are defined, understood, and accepted); I rather think that's the AB's job.
from w3process.
When the "TAG/AB election experiment on voting" was announced to the Membership in September 2014 the "no other candidate" choice was described as follows:
Both STV ballots will include a "No (other) candidate" choice (see [4]).
A vote for "No (other) candidate" is a vote for a hypothetical alternative.
With this option, any candidate with fewer votes than the hypothetical
alternative would not win - but since this is experimental data not the
official election, it will not affect the actual outcome.
...
[4] http://en.wikipedia.org/wiki/None_of_the_above
from w3process.
And indeed as part of the experiment it had the possibility to teach us something. As part of the official ballot where we don't have a process that causes "any candidate with fewer votes than the hypothetical alternative" not to win, that's a problem.
from w3process.
fwiw, "no other candidate" is marked as having withdrawn prior to tabulation, to cause the tabulation software to elect candidates to fill seats; thus, it isn't tabulated and we don't even learn something (that we'd prefer not to know, anyway)
from w3process.
The AB may ask us to make this option effective, i.e. if "no other candidate" wins a seat, the election leaves that and all other unfilled seats, vacant. We would need to work out what then happens. The TAG/AB remains one member short until the next election, or is there an immediate other election? And so on.
from w3process.
I would suggest that the seat is vacant and that another election is called. There are only two elected bodies - the AB and the TAG, and I believe it is helpful to fill the seats.
Note that this implies removing the procedure whereby if there are as many candidates as seats an election is not held.
I also note that the only way to reach this outcome is to have a candidate that more people really don't want than there are voters prepared to accept, and to have only as many candidates as seats in the first place.
I doubt that this situation will occur much in practice - hopefully never, and it seems likely that this will be true. But if it is considered necessary by the membership, it is a useful thing to have.
from w3process.
Whether or not it occurs in practice, we need to either take it out of the election form or add processing No Other Candidate votes to the process.
The simplest way forward would be to leave the seat vacant and call another election if No (other) Candidate wins.
Or leave it vacant until the next scheduled election if we believe the AC will get election fatigue or that that the election captured their intention to prefer an empty seat to the candidates who got less support than No (other) candidate. I think I lean toward waiting until the next election ... since these are advisory roles not formal governance roles, nobody is disenfranchised because they have no representative in in a legislative body. Also waiting allows time for emotions that might have driven AC members to blackball some candidate to cool down.
from w3process.
fwiw, if this route is taken, it's only worth doing if it is expected it might be used and have effect. And then all the outcomes need consideration (not just the immediate formal process ones), including the effects on the rejected candidate(s), their companies, their culture, and the effect on the likelihood of other possible candidates not standing as a result of observing the humiliation. I would expect to formally object to introducing use of this.
from w3process.
I have tried multiple times to get it removed from the ballot, and 3 times failed to get consensus on that at the AB.
from w3process.
Closing, and requesting the team to remove the option from the ballot
from w3process.
This is quite unfortunate, as I believe this is relatively easy to implement with process changes, and would show clarity in support.
from w3process.
@cwilso I agree that it would be useful, but unless there is an apparent consensus I'm no longer continuing to advocate this.
from w3process.
Related Issues (20)
- "Wide review" is too easy to confuse with "horizontal review" HOT 7
- Veto by inaction HOT 16
- word order "W3C Group Draft Note" -> "Draft W3C Group Note" HOT 26
- living standard / candidate review snapshots need to address wide review issues HOT 12
- Council Composition requirements include Tim Berners-Lee, TAG life member HOT 5
- Disciplinary action HOT 3
- Stop citing the "superseded" TAG charter HOT 2
- Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" HOT 8
- Are the rules for updating Registry Definitions appropriate? HOT 23
- W3C Decision needs better cross-referencing HOT 3
- What kind of Group is for what kind of work? HOT 1
- TAG Appointment Process Shortcomings HOT 25
- AB Role in TAG Appointment HOT 13
- Are TAG Appointments mandatory for the Team to fill?
- Ground the different types of groups / maturity stages in Problem Statements HOT 4
- Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned HOT 1
- Affiliation constraints on TAG membership HOT 17
- The minimum time commitment for participation in the elected bodies is undefined HOT 4
- Chair should be required in charter HOT 38
- Run link checker on Process Drafts HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from w3process.