I've started drafting an "Open Governance Definition" (whose development I recommend in the article), and think such a definition would be complemented by a shared understanding of governance models.
Drupal wrote about it ages ago too, so it's not 'hey look at this new problem I have' - we just haven't built it into governance structures in a neat way yet.
Hey Amye (and Andrew) - I'm actually really interested in this blog post as well, as this is what we designed Nivenly's co-op governance model to accomplish, including the bits about being resilient to re-licensing and corporate capture. ❤️
Comments
We lack a language for crystalizing governance model types in OSS, an equivalent to groups like "copyleft" or "permissive" in OSS licensing.
Not making a choice on governance is actually a choice, and I don't mean that snarkily.
There’s a reason no one has built it — like OSS licenses, there are many nuanced differences, and the texts of each evolve over time.
Rather than start anew, maybe build an index of ‘em?
That was built that into OpenStack’s governance and then refined in Kubernetes … :)
It is built into a few of them … what’s lacking?
(That I know of, but I'm only just starting to poke around again.)