Skip to content
This repository has been archived by the owner on Oct 5, 2024. It is now read-only.

Headcount #335

Open
sklirg opened this issue Apr 20, 2018 · 1 comment
Open

Headcount #335

sklirg opened this issue Apr 20, 2018 · 1 comment

Comments

@sklirg
Copy link
Member

sklirg commented Apr 20, 2018

It has happened that someone managed to bypass the counting party when leaving without informing them. This makes it so that there's one person who's authorized to vote, but isn't actually voting. One fix for this problem is to remove the voting rights for everyone after a larger break, but another could potentially be to implement a "headcount" feature.

The idea here is that the counting party (or the moderator) could ask for a headcount. This is done by starting a process which requires user interaction, e.g. by opening a modal which asks "are you here".

The ones not answering are (probably) not there, and their voting rights could be revoked. If they're actually there, they can authorize themselves at the counting party to regain their voting rights.

This could make checking in and out after breaks much more efficient. However, if people manage to leave without notifying the counting party and plan to keep on voting at home (or somewhere else), this solution doesn't solve that problem. (What could be done though, is to use the famous "Are you on VOIP"-tactic from WoW PUGS. Start a ready check (or in this case, a headcount) where the question is "Are you here?". Before opening for answers, inform the users what answer to actually answer (in the case of the WoW example, you get the possible answers "Ready" and "Not Ready". Everyone on VOIP is asked to respond "Not Ready", and everyone who responds "Ready" can then be assumed to not be on VOIP.)

It might be possible to implement this feature by tweaking regular issues a bit when I come to think of it. If the counting party could get a list of everyone who voted for each answer this feature is basically solved. When creating an issue, an additional option could be displayed which allows the counting party to receive a list of all votes for each alternative.

This turned out as quite a ramble. Feel free to comment if anything became too unclear.

@aslakhol
Copy link
Member

I think a good solution to the "voting from home" issue is simply to do a one-time-code announced in the meeting for every time the feature is used.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants