Use governance for software development processes

Hi So this is a thought on software development processes, and governance, and where they intersect. • Github is currently a hard dependency, more or less • Github permissioning limits the decentralization of this work • Permissioning could be related to VotePower of validators or to a governance proposal Imagine a governance proposal to determine the contents of this file: github.com cosmos/gaia/blob/main/.github/CODEOWNERS#L4 ``` # CODEOWNERS: https://help.github.com/articles/about-codeowners/ # Primary repo maintainers * @alexanderbez @zmanian @yaruwangway @crodriguezvega @jackzampolin @mmulji-ic @glnro @jtremback @mpoke @sainoe @MSalopek @smarshall-spitzbart # Governance Process and Docs maintainers docs/governance/* @uditvira @LexaMichaelides @yaruwangway ``` How could we make it such that Gaia chooses her own maintainers? • gov props that choose CODEOWNERS • all validators are also CODEOWNERS • validators meeting a certain VotePower threshold are CODEOWNERS How could we make it so that gaia no longer has a strictly defined…

Excerpt (1199 of 1218 characters). Read the whole post on the forum ↗

How could we make it so that gaia no longer has a strictly defined github repository?

You mean here to decentralize the repo of Gaia? Such that there is not one central repo anymore, but more distributed over various locations?