I have two active open source projects, and have been hosting them at Google Code. Now I'm moving them to Github. I'm still tidying up odds and ends.
|Google Code (old home)||Github (new home)|
So let's start with some of the good things about Google Code:
Mercurial: I prefer Mercurial as my DVCS of choice, and it is well supported.
Decent Web Interface: Because code hosting sites are built by developers they tend to have idiosyncratic usability (architecture astronaut style), with Google Code being the least worst. For example on Github you can't even sort issues by priority. It is completely absurd.
Multiple repositories per project: The popular hosting services have an issue tracker, wiki, links etc per project. With the exception of Google Code, you only get one source repository per project. DVCS encourages a style of single purpose smaller repositories versus the large agglomeration that was more typical in the subversion and CVS days.
It is far more pleasant being able to use a single issue tracker, wiki etc for a group of related source repositories. Only Google Code does this.
So why leave?
- Downloads terminated: I have 14 files per release of APSW (most are Windows binaries since Windows developers rarely have compilers and related installed) and one for the other project. Google no longer want downloads, yet that is the primary way others use my projects. Google also do not believe in supporting Linux for Drive, not to mention that it is a terrible alternative.
- No future: There is no indication of any ongoing interest in Google Code and they refuse to take money for it. They keep shutting down services, and it is good practise to not be dependent on them. (No customer service, erroneous disabling of accounts etc.)
There are three choices for where to go:
- Sourceforge: No chance
- Bitbucket: I used them in the past, but they couldn't support personal and corporate use at the same time. They supported Mercurial, but Atlassian means an enterprisey design (I hate using Jira). Most importantly when I asked if they would guarantee availability of a download service for any period of time they said they would not. So they are out.
- Github: There are many things I don't like about Github, but at the end of the day they are the least worst, and only practical alternative.
This is how I converted my projects to github:
Use github pages to generate documentation into. However do not follow all those instructions - in particular the gh-pages branch needs to be created as an orphan as it has nothing to do with the master branch and its files. (Better instructions).
The pages didn't render correctly, which was because they returned 404 for stylesheets and images. You have to do some magic to fix it.
Use Google Code Issues Migrator to copy all existing issues over to Github and keep the same ids.
Grep the source tree for all mentions of `code.google` and fix them.
Edit the projects at Google Code to say they have moved
Before doing the real projects I experimented on a test repository to make sure that the documentation and releases worked. Sadly releases have to be done manually because there don't appear to be any usable command line clients (not even github's one) and none of the libraries I looked at did releases either.