Have a run-off option for polls

[matgb]

Title:
Have a run-off option for polls

Area:
polls

Summary:
It should be possible to have polls where users ranks options in order of preference (instant runoff or preferential voting).

Description:
Currently we allow for simple plurality voting (radio buttons) and approval voting (checkboxes), but not for preferential voting. As a polling theory geek (involved in the UK campaign for reform) this makes me sad.

We should be able to have polls where a list of options is given, and voters can rank them in order of preference. When the poll is closed, a counting algorithm can be run to reveal which option wins after losing preferences are reassigned.

The code, I think, partially exists for this on LJ as they used it for the advisorty board elections. I don't think it was a good implementation, but it was workable and could probably be improved.

Drawbacks are mostly coding and processing time, as calculating a result will require backened work, especially true if the current result is showing. The LJ implementation is poor and would need improving.

Advantages are that polling geeks like me are very happy, and users can use polls in a more expressive manner. Prefential voting is a good way to organise outings and similar, so good for a journalling site; eg ten people plan a meal together, do they want pizza, burger or that new veggie place, etc...

Poll #4091 Have a run-off option for polls

Open to: Registered Users, detailed results viewable to: All, participants: 46

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
33 (71.7%)

Should be implemented with changes. (please comment)
6 (13.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (13.0%)

(Other: please comment)
1 (2.2%)

Comments

[matgb]

The biggest problem in Livejournal's code was that they restricted people to a finite number of picks from a list of candidates, rather than numbering their votes. The handling of tied eliminations was also sloppy, eliminating all candidates involved in a tie; preference tends to be a countback method and/or conditional eliminations.

Agreed. I like the idea of caching the results if the process takes calculation as well.

Need to work on a 'how this would display' mockup at some point, but can leave that until it's agreed for implementation and put ideas into Bugzilla.