- What does GitHub Enterprise buy us? Which of these issues would that fix?
It's a self-hosted GitHub. It would allow us to have private repositories (good for deploys, ops, etc.) and manage our own user database (we could integrate with our own auth system) and probably waives the 13 and under rule above. The price is too steep since its a per-seat license. A nonstarter if the WMF is going to have to pay for every potential developer who wants to attach.
As mentioned before, we can't use github enterprise at all, since it doesn't allow for hosting public repos. Let's ignore that it even exists.
We do need a GitHub strategy -- to make our projects more discoverable, make use of more contributions, and participate in the GitHub reputational economy. So we must figure out the right ways to mirror and sync. But I doubt our own long-term needs would work well with using GitHub as our main platform.
I'm 1000% with you on this. We should definitely at some point mirror our code in GitHub like the PHP project does <http://www.php.net/git.php>. Being able to publish and handle pull requests coming from GitHub would be a nice feature in Gerrit or any replacement. It'd be nice if others can have their own MW extensions or versions of extensions and core on GitHub and pull from us (and us from them) esp. for extensions that may need some love or have changes that don't satisfy the WMF code quality bar.
Well, we can enable replication from Gerrit to Github. We haven't done so, yet, but it's a feature that's available.
- Ryan