Google code or GitHub for project hosting? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question?开发者_StackOverflow社区 Update the question so it can be answered with facts and citations by editing this post.

Closed 9 years ago.

Improve this question

Is Google code similar to Github where you can put your source code for collaboration?

Which is the de-facto SCM it's using?

And which one is recommended for project hosting?

---

Update 2013:

All major repo hosting services supports git, and supports smart https access (see below):

• code.google.com (with cases like this one, July 2011)
• bitbucket.org
• tfs.visualstudio.com (!, as explained by Scott Hanselman)

Currently (July 2013), the main difference (between GitHub and other services) is in term of release management, more specifically:

• integration with Travis CI (continuous integration, possible more or less with all services)
• release artifacts: See "GitHub Release Your Software (July, 2d 2013)":
  The ability to associate to a tag up to 100MB of binaries.

---

Initial answer (September 2010)

One big difference is the support by GitHub for smart http, as explained in the ProGit "smart http" section, supported since April 2010.

Being behind a firewall at work, that is more than useful to actually push anything to the remote repo!

I don't think "Google Code" support it officially, even though some contributors try to push that feature.

---

Yes, they are similar but support different versioning systems. Also the collaboration style is different. While Github (and Launchpad and BitBucket and all the other DVCS hosters) focus more on active collaboration between forked projects, Google Code's primary way of collaboration is through tickets.

So none of them is per-se better than the other, but perhaps fits your project management and contribution/collaboration style better. The whole debate between centralized and decentralized code versioning systems is related to that.

---

Some features that you should consider:

• Open source:
  Google: Always open source.
  Git: Open source for free account, but you can pay to switch to close source.
• VCS: Both google & github support Git (and others)
• Wiki: Google wiki is poorly supported, unless you love to write with wiki tags. You can find many project in Google project hosting has there wiki in Git hub.

  

• Statitstics: Github provides many nice statistics chart, while Google provides only a list of updates Git:

Google:

---

AFAIK Google code is yet to support git natively. At least as far as I can tell by the comments on the ticket open for this.

So if you are using or would like to use Git then Github will be naturally more suitable.

On the other hand if you are using SVN and would like to continue to then Google code might be a more natural fit.

I have found Github projects easier to set up and get going but that is fairly subjective. Some of my friends also claim that Github's support/ecosystem is better than Google's.

---

Use GitHub. GitHub gives each account its own namespace for project names, so you don't have to worry about your project names having already been taken by people's projects. If you're using Google Code, however, then you do have to worry about this.

---

If you need private repos, you won't get that with Google Code. At least not yet; see this open issue: http://code.google.com/p/support/issues/detail?id=1829