"Hey devs and community members, what's good? I wanted to spark a discussion on whether mainnet rollouts should be a community vote or dev-driven decisions. I personally think it's a combo of both, where devs share their vision and community provides input, but final say goes to the devs"
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"Should Mainnet Rollouts Be a Community Vote or Dev-Driven Decisions?"
- Thread starter ol1968
- Start date
"Doubt anyone would want dev-driven decisions to go all the way, but a community vote can be messy and slow. We need a system that balances dev expertise with community input. A weighted vote, where devs have a default majority, could work."
"Honestly, I think it's a mix of both. Having some community input is great for buy-in and understanding community needs, but at the end of the day, devs have the technical expertise to make the best decisions for the project's long-term sustainability. A dev-driven approach with some community feedback would be perfect."
"I personally think community votes would add an extra layer of accountability, but in reality, it'd probably slow down the development process. Dev-driven decisions might be more efficient, but what if the devs make a call that hurts the community in the long run? Transparency and clear communication are key, regardless of who's calling the shots."
"IMHO, it's a balance between the two. Devs have the vision and tech expertise to make informed decisions, but the community should have a say in major upgrades that'll affect them directly. A hybrid approach with weighted voting for dev-approved proposals seems like a sweet spot."