Newcomers often ask the same reasonable question: "Who is actually in charge of Malairte?" The honest answer surprises them. Nobody, exactly. Decisions in an open-source project like Malairte are made through a process called rough consensus, and understanding it is the key to participating in governance without frustration.
What rough consensus is not
It is not a majority vote. Counting hands tends to split a community into winners and losers, and the losers drift away. It is also not a dictatorship, even a benevolent one, because no single person can hold the whole project hostage. Rough consensus sits between these extremes.
What rough consensus actually means
Rough consensus means a proposal moves forward when the people who care about it have been heard, the serious technical objections have been addressed, and no one with a sound reason is still strongly opposed. The emphasis is on resolving objections, not on counting supporters. A handful of quiet "I am fine with this" responses, combined with no remaining serious concerns, is enough. A loud crowd of enthusiasm means little if a real safety objection is left unanswered.
Why projects work this way
- It forces discussion to focus on the merits of an argument, not the popularity of the person making it.
- It protects against a vocal majority steamrolling a valid technical concern.
- It keeps the door open: a good objection from a newcomer carries the same weight as one from a veteran.
How to take part well
If you want your voice to count, raise specific, technical, addressable objections rather than vague unease. "I do not like it" stalls nothing. "This change breaks compatibility with older wallets, here is how" must be answered before the proposal moves. Frame your concern as something the group can resolve, and you become part of the process rather than noise around it.
The community organiser's role
At meetups and in chat, organisers can teach this culture by example. When a heated debate breaks out, a good moderator separates real objections from personal friction and asks, calmly, "What specifically would need to change for you to be okay with this?" That single question turns an argument into progress, and it is the heart of how rough consensus keeps a decentralised project moving without a boss.