-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Possible design flaw in multiselect polls #863
Comments
Makes sense. So let's say every user gets a total score of 1 and they can split it across options (or not). Percentages should be based on the scores rather than the total votes for that option 🤔 |
Percentage should be based in total votes for each option IMO. Weighted poll can be a different config, I can't think of many examples for that off the top of my head. |
Can you elaborate this? As of now, percentage for an option is calculated as |
% of each vote = total number of votes for that option / total # of users who voted. |
Makes sense. The total would be higher than 100% overall - but that's fine I guess? |
Currently raven splits a user's vote to equal amount for all options selected.
IMO in most cases the multi-select polls are done to find # of people voting for each individual option.
E.g.
In such cases, a single person voting 1 option will give a lot more weight to that single option.
The text was updated successfully, but these errors were encountered: