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 :)

  • benwebb@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    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.

    • sneakyninjapants@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      I think this would be useful too, but currently that way of voting raises the issue that anyone outside this instance could vote on that issue as well and there would be no way of determining how many up/down/abstain votes came from users of this instance alone. A bot that could filter users of this instance would solve that though. If a separate community was created solely for voting (as opposed to discussion), there might be a way to make it private for users of this instance which could solve the problem also.