Issue Details (XML | Word | Printable)

Key: JCPNEXT4-12
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: sean_sheedy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
jcpnext4

Voting change to provide protection against unqualified candidates

Created: 21/Sep/11 06:33 PM   Updated: 08/Apr/14 07:43 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: pcurran and sean_sheedy


 Description  « Hide

818-822 - It would be simpler to allow each member to vote yes or no on whether each candidate should hold a vacant seat. The candidates who get a simple majority of "yes" to "no" votes will get seats in order of who received the greatest proportion of yes to no votes. Should not all seats be filled but candidates remain because they did not receive a majority, that suggests a vote of no confidence for those candidates and the seats should not be filled. This prevents situations with marginal candidates, such as where there are two candidates, two seats, and candidate two gets only one vote but still gets a seat.

PC> Interesting suggestion, and far too late for this JSR. I suggest we factor this into the "EC merge" JSR. Please log a separate issue to ensure that we don't forget it.



pcurran added a comment - 21/Sep/11 09:17 PM

Sorry - no need to log a separate issue - this one will do. We'll defer it (haven't yet figured out how to tag issues as deferred - and will definitely take it up again since c,early it deserves further consideration.


pcurran added a comment - 06/Jul/12 07:23 PM

Too late now for the EC Merge too (sorry about that.)

However, it's still an interesting suggestion. I'm moving this issue to the newly-formed JSR 358 project, for consideration in that JSR.