Behind every FOSS governance problem is seemingly a tech dude who holds the keys but just doesn't care
Follow
Like, I've seen and been involved with tons of governance issues in FOSS communities over the years, and I've lost count of how often it's just a situation of "everyone in the community is working really hard to make this work, and solving all the difficult problems, and then the entire effort grinds to a halt because of one singular white tech dude at the top being uncooperative or 'not seeing the problem' or being unwilling to delegate responsibility"
I would encourage you to identify who the tech dude is in *your* FOSS community with a governance problem, and start drawing more attention to their role in the issue
Perhaps the most frustrating part of this all is that if the situation continues for long enough, lateral violence often starts happening - nobody can hold the dude at the top accountable, therefore people start trying to hold *each other* accountable, even if nobody involved in those conflicts actually has the power to do anything about it