My work on threativore and flairs was the stepping stone for something I wanted to achieve ever since reddit. A way for a community (instance in our case) to be able to vote on decisions, without having to rely on comment-votes and manual counting, but also without allowing every rando on the service to vote on your internal matters.
To this end, I have now deployed the governance community on our instance and it’s live, let’s say in testing mode. Please check the manual I just linked for more in-depth explanation of how it works.
As discussed in the previous thread, the initial plan is that only stakeholders can vote and open threads. Everyone who is supporting us with donation is a de-facto stakeholder, however 
threadiverse enjoyers cannot open new threads. Also after the discussion I decided to allow 
vouching for others, which any supporter at the higher tiers can do twice. Vouching gives voting access, so this means you can specify other people who you personally know are valid members of the instance, and that will allow them to take part in the decision making, even if they’re otherwise only lurking. Effectively vouching puts someone at the same level as a threadiverse enjoyer
On a voting thread, the bot will maintain a control thread and refresh the tallies every 15 mins, (so don’t expect instant updates.)
Currently most of y’all won’t have voting rights, because ko-fi tiers will only be applied at the next donation or the monthly charging time. Liberapay is handled more often, but it requires a manual step on your end which you can do on your own already.
If you have any suggestions for MVPs for our instance, please do suggest them.
Unfortunately no feedback from any UI developers until now so as to add threativore flairs to the UI itself. I guess I have to learn javascript as well one of these days…
Anyway, this is only the beggining. I want to add more voting options, more automatic ways to nominate others for MVP. And I still need to distribute the affiliation tags (they will be visible when you comment in a governance thread). Eventually I want to even allow threativore to be usable my comm mods than just instance admins.
There’s already a test thread in governance, so go ahead and downvote/upvote it. I plan to open a proper one soon, with a small decision I want to make. I wouldn’t suggest trying to open a thread yourselves yet until voting-enabling tags are distributed, as the bot will just lock it)
If I may make a suggestion, the apache voting process is probably one of the better methods of community voting I’ve seen. I’m a big believer in voting by consensus and also allowing people to articulate their passion (or lack of it) by their vote.
consensus votes are remarkably functional when people don’t coalesce and plot against it.
If you can find a way to effectively ward against that, it’s a great solution.
If I had infinite dev time I would implement something akin to loomio. In fact I have my own loomio hosted but it’s a big struggle to get people to use a different platform.
Ultimately I have to do something that works in lemmy and also with the fact that we’re not an affinity or even tightly knit