Open source governance keeps creating forks
Organic Maps now has a fork called CoMaps, created specifically over governance concerns about the original project. The Flipper Zero thread shows a similar anxiety: the official post says they've 'allocated resources to maintain firmware,' which commenters immediately read as 'we're putting it on life support.' Elm's thread questioned whether the language is even worth adopting in 2026 given its slow development pace.
The pattern: when a community loses trust in the people controlling a project, either through ownership changes, slow development, or opaque decision-making, they fork or abandon. The trigger is almost never technical. It's always governance.
This has an asymmetric cost. Forks dilute the community and fragment contributions. The original project loses momentum. The fork usually starts enthusiastic and often stalls too. Nobody wins cleanly.
So what?
If you maintain an open source project that has real users, governance transparency is now load-bearing infrastructure. Announcing 'minimal maintenance mode' without warning is how you turn your user base into a competing project's contributors. A clear roadmap and a public process for community input are worth the overhead.