alt Hacker News> All you've pointed to is devs working together and people filing bugs. All that requires is auth, no?
Collaboration is a form of socialization. GitHub made a social network on top of a SVN to create a forge that people can interact with each other creating issues, pull requests, reviewing and commenting on them, engaging in discussions, forking and improving upon each others works... These are not "just auth" and it's not something git solves by itself. I really don't know how to make this clearer either, sorry. Maybe it's this is the kind of thing that you see it and you get it or you don't, I don't know. For me and apparently for lots of people in this thread that makes sense.
I know git doesn't do this by itself, but then we're not talking about github vs raw git - perhaps that's where you're confused by what I'm saying.
All these other services have what you're talking about, and the only cross-repo/org work I can see here is:
* Aligned accounts (person X on one service is person Y on github), if you want that continuity across services
* Forking
And the whole forking/branching/merging side is handled by raw git.
That's why I've been asking what githubs huge centralisation gets us. It has a UI and features that are useful, great, those exist in other projects too, so what is the stickiness?