Did like the way @Murch explained it later on though. The only thing that I know based on my own FOSS experience that doesn't work is "loosely organized". With the only exception of a security maillist, you have to be either organized like you're a shitcoiner rugging people, or be not organized at all. The process is open, that's all that is needed.

Open processes are very well defined in Bitcoin Core, from CONTRIBUTING.md to doc/release-process.md. If next time all maintainers are in a single spot and get taken out by some asshole with a bomb, anyone can continue the work, save for having bitcoin/bitcoin membership, third party tool like transifex control. However, with b10c's mirror scripts, bitcoiners can always move on, no matter what happens.