4 ms·
> Even if github were to disappear, it would be absolutely trivial for a team to switch to an alternative central git repo for everyone to work through. Except
by pifflesnort 14y ago
> Even if github were to disappear, it would be absolutely trivial for a team to switch to an alternative central git repo for everyone to work through.
Except for all the tooling built into github that would have to be replicated locally somehow.
I guess you could switch to: http://www.atlassian.com/software/stash/overview http://www.atlassian.com/software/stash/overview
That wouldn't be "trivial", and if that's the backup plan, you may as well start by using Stash and skip github entirely.
- andreyf 14y ago> Except for all the tooling built into github that would have to be replicated locally somehow. What tooling? The issue tracker and code comments? I imagine the uptime requirements aren't >99% for those, but if you absolutely need them all the time, that's what github's enterprise service is for.
- pifflesnort 14y agoYes, the tooling that's required if you're actually collaborating instead of working in personal silos. There are better options than Github's overpriced virtual machine-based mess of an 'enterprise' offering.
- hp50g 14y agoThe issue tracker uptime is higher than the VCS in a corporate environment. Its more an ALM tool for us as it has use cases, defects, project planning running off it. That means the front line support, dev team, project management team, business analysts and management all use it 24/7 (in our case from 5 different countries). github enterprise is a crappy solution for the above as well and is hard to support and expensive too.