Good ideas and conversation. No ads, no tracking. Login or Take a Tour!
I'm not sure if it's about competitiveness. Communicating is a lot slower and more frustrating than hacking. In the old days, forking came at a cost; keeping up with upstream changes to a project that was actively developed was a huge pain, so it was easier to try to get your changes accepted upstream, even if you had to do some work to convince them to take it. With git, it's only inconvenient when upstream changes something you changed too, and that probably doesn't happen often, so the easier thing to do is just maintain your fork.