>>15
"Too many cooks spoil the broth"
This is a well recognized phenomenon in software engineering (and every other human endeavour involving more than one person).

What actually happens in your proposed scenario is these hundreds of would be git developers go and and write their features and some of them wander off somewhere else and their pets become unmaintained and trying to follow the git mailing list becomes impossible and git's heads keep growing and growing until you have an unmanageable trainwreck of bugs and complicated code.