What kind of threshold should a vote have to pass before being implemented? Do we really want to be making changes based on a vote that only got one “Aye”? Ten Ayes? Over 50% of the user base?
What kind of vote engagement can we reasonably expect to achieve? Is it actually likely that 50% of the user base will engage with any particular vote? Are there any useful presidents out there?
Who should be responsible for counting the votes when they’re over? Perhaps the OP tallies the votes and edits the post?
Is there an easy test the mods can apply to a tallied vote to allow them to check whether it’s passed? Something that is not open to interpretation and results in a clear directive to make a change?
I’m also kind of testing out this discussion format as a way of generating things to vote on i.e DISCUSSION > POLL > VOTE seems to make sense.
We’ll see :)
You must log in or # to comment.
The current aye/nay system is cluttered and clunky. How about we allow comments in [discussion] posts and then have a separate [vote] post with a single comment for each option so people can choose up/down/abstain? Then nobody has to count anything, human or bot, or worry about typos, formatting, sarcasm, etc.
I also propose a minimum of 3 days, maximum of 1 week per each [vote], no time limits for discussion. You can choose when to start the official [vote] after discussion starts.
I like the idea of using lemmy’s builtin voting mechanism.
I think for yes or no voting questions, it would be simplest to express all options with a single comment that is an affirmative statement on whatever is up for vote. Then each user action (pressing the upvote button, pressing the downvote button, or reading the post and pressing no button) maps exactly onto the vote a person casts.