Github still holds quite a lot of nines in terms of uptime. It's just that it's extra visible when something big like Github goes down.

The important part you should consider is to switch go git. I'd recommend starting to use Github, and if you find that it's down too much, look at alternatives or at hosting a solution yourself.

It took about a day of mucking around, but we got a VPS up and running and we're using gitlab. (the software github is based on)

It works well for us. We just have to pay the price of a VPS and updating the system occasionally.

I've found that Github makes it so easy to work with clients of mine that the positives still outweigh the negatives.

That said, I have two pushes for two clients this morning that may not make it through in time for the status meetings.

If you have a company full of people, it may still be worthwhile to have a couple of them really learn git, and setup a git server internally.

[Edit: And my pushes made it through anyway. Still happy w/ github]

When moving from svn to GitHub what you're actually doing is moving from a centralized svn system to a centralized git system.

The big difference is that in the second case you can keep working on your local repo without touching the central repo, at any time add new remotes to your local repo and pull and push from your peers.

If GitHub is down, you just keep working. If your svn server is down, you just pile your local work waiting for it to come back up, the tool will not help you in that case.

Moving from svn to git is a no brainer, even if you keep using it as if it were svn most of the time.

Apparently they have been ddos'ed multiple times recently. I wouldn't have noticed, if it didn't appear on HN though. My impression is that they have people who are quite capable of dealing with these issues. I would rather have a provider that gets under attack, but has the resources to mitigate it, than one that is rarely attacked, but would be destroyed by it.

Well if you're only using GitHub for hosting the repo then you can still work with your copy of the repository while GitHub is offline (since you're in distributed not centralise version control territory).

Git has a file protocol so you can also just sync your changes between one another via a network share of your repo. Or SSH or email each other pull requests.

Upside > Downside. I'll take 15 minutes of DDOS outage / month over hosting my own stuff anytime.

If you're too concerned, there is a self-hosted option, GitHub Enterprise.

Git works pretty damn good offline as well, sure you can't push to the server but its not going to be a show stopper if GitHub goes down for an hour.

I don't think so. I am still able to do all work through the command line (merge, commit) etc.