Maintainers could also use that to distrupt things in the same way, to be fair.
A two-key-rule system would be neat. A repo can be in an org, but some big changes (removing/adding a maintainer, moving a repo, renaming an org, etc) need to have x of total maintainer accounts click an approve button within a few days of each other. Making big changes slow and tedious feels ideal when we're talking about the countless lifehours sunk into a project by maintainers, that's funded and supported by a company. Both of those parties benefit from cooling off periods and being a bit obstinant to eachother... without being able to slit eachothers throats.
A two-key-rule system would be neat. A repo can be in an org, but some big changes (removing/adding a maintainer, moving a repo, renaming an org, etc) need to have x of total maintainer accounts click an approve button within a few days of each other. Making big changes slow and tedious feels ideal when we're talking about the countless lifehours sunk into a project by maintainers, that's funded and supported by a company. Both of those parties benefit from cooling off periods and being a bit obstinant to eachother... without being able to slit eachothers throats.