HTTP is the future for git and github. It has several benefits and no downsides. 1. No SSH keys required (if you've worked with people on windows machines or n

HTTP is the future for git and github. It has several benefits and no downsides. 1. No SSH keys required (if you've worked with people on windows machines or newbies to the command line, you'll recognize this is a massive win) 2. The same URL can be used for anonymous clones and private pushes. So if you are granted commit access, all you have to do is `git push` — no more changing remote URLs. 3. We can use the same URL for the web as we can for clones. This is a nice hidden usability win. We're waiting for a couple of things (1.7.2+ to become default distribution, and caching of HTTP credentials) before we make a complete push. That isn't to say we're deprecating ssh or have any plans to. It just means that we'll be increasingly pushing HTTP as the default.