- From: Michael Champion <Michael.Champion@microsoft.com>
- Date: Fri, 1 Dec 2017 22:21:20 +0000
- To: Brian Kardell <bkardell@gmail.com>, "public-w3process@w3.org" <public-w3process@w3.org>
- Message-ID: <BFA879E8-D37B-4049-8BB3-41FDA208BFDA@microsoft.com>
> , I have to admit that despite the flurry of conversations and concerns and even a few TPAC conversations, > I'm still not entirely clear where this leaves things right now. So, can someone help me clear things up? There seems to be no consensus in the AB or AC whether to double down and make the current STV system work better (e.g. by removing the misleading language from the process document saying AC reps have one vote per available seat), go back to the old system, or find some hybrid that combines the “new” ranked preference model and the “old” multiple vote model. For now, we are using exactly the same system as was used in the spring AB election – AC reps MUST rank candidates (no ties allowed), and their single transferrable vote gets applied in preference order, with “excess” votes for winning candidates and unsuccessful votes for losing candidates transferred to those lower in the preference order > On a scale of 1 to 10, I'm putting them both at 10. I very much desire this. I’m in the same situation. I have a slate of candidates in mind that I prefer equally but am forced to rank them. My support for whoever I rank #2 is much much greater than my support for whoever I rank #3, but there’s no way to express that. (The “No (other) candidate” option is a no-op), so abandon any hope that ranking it 3rd will have any effect). I consider this a potentially fatal bug in the system and curse myself regularly for not figuring this out in time to formally object to Process 2017. But to be fair, there are plenty of people around W3C who consider it a feature that fixes bugs in the old system. So, in the best tradition of consensus-driven organizations, we’re muddling along until it becomes clear either that people like you and me are mistaken that this is a bug, or it becomes painfully obvious that we need to fix the bug. From: Brian Kardell <bkardell@gmail.com> Date: Friday, December 1, 2017 at 1:27 PM To: "public-w3process@w3.org" <public-w3process@w3.org> Subject: Understanding where we are with TAG/AB voting Resent-From: <public-w3process@w3.org> Resent-Date: Friday, December 1, 2017 at 1:26 PM As someone interested in keeping the TAG and AB doing what I believe are good things, I have to admit that despite the flurry of conversations and concerns and even a few TPAC conversations, I'm still not entirely clear where this leaves things right now. So, can someone help me clear things up? There are 4 nominees for 2 seats. Let's say, hypothetically, that my ideal outcome is that two of them get reelected. On a scale of 1 to 10, I'm putting them both at 10. I very much desire this. But there are two other people too and, in the old system, I couldn't express anything about that, despite the fact that I do, actually, have a strong preference of which I'd like should one of my ideals not work out. I'm not the AC for my org, but if I was, today I'm honestly not sure I could tell you what my votes "mean". That's what I'd like them to mean, but I'm not sure that's actually possible to express? Can someone help me understand? -- Brian Kardell :: @briankardell
Received on Friday, 1 December 2017 22:21:51 UTC