> This is one reason us corporate software pushers can't use github and the likes. We need stuff to be hosted on a network we control.
cringe This is very corporate reasoning in the most pejorative sense of the word.
> Each hour we lose is potentially multiplied by the number of staff as we would push and pull hundreds of times a day.
You clearly haven't used git. 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.
> 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.
> 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.
The 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.
cringe This is very corporate reasoning in the most pejorative sense of the word.
> Each hour we lose is potentially multiplied by the number of staff as we would push and pull hundreds of times a day.
You clearly haven't used git. 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.