Yeah, this is true. If someone pushes something they shouldn’t though, it can just be reverted and their privileges get taken away. It’s far easier to fix mistakes/issues than it is to make up for the community not contributing.
The alternative of having a single person be the choke point / bottleneck for a whole open source project just isn’t sustainable. I mean, Armory is still pretty small and we’re already hitting it now… You and I would both like to contribute to the docs @BlackGoku36, but it’s unclear if those contributions would get accepted in time to avoid becoming a mess of merge conflicts.
For example, while it’s not the docs, my pretty uncontroversial pull request to add more detail to the issue template has no merge conflicts. It’s still been sitting there without even a comment, unaccepted or rejected for over a month.
Don’t get me wrong. I’m extremely impressed and grateful for what Lubos has pulled off already. I’d just like for us all to be able to help.