I have been using googlecode for some of my recent open source development work, and I was surprised how googlecode speeds up development. The SCM is very fast and gave me no troubles, it is easy to create wiki pages and documentation for projects etc. etc. Although it offers limited features, compared to sourceforge for example, but the real power is in its simplicity. Sourceforge offers more features like, hosting web pages and shell services and if you are smart you can also create your own little maven repository for your artifacts; one might argue that all these features make sourceforge very complex. But recently sourceforge has become slow as hell, and it is bit of a pain to manage your work, SCM is slow, web pages are not served with a desired speed, shell services (although more secure) but slower and the whole shell-creation process takes too long. So to cut the story short, I finally decided to migrate some of my work from sourceforge to googlecode, simply because googlecode is faster and simple.
In the beginning I had no clue how to achieve this task. But it was much simpler than I anticipated. My only concern was to get the code migrated fully, safely and with all the version history. This is done by synch'ing the project's SVN repository on googlecode with the repository on sourceforge. First I reset the googlecode repository to enable svn synch'ing. This is done under Administrator->Source tab on your project's homepage on googlecode. Then I began the synch'ing process.
The first step is to initialize the googlecode's subversion repository
svnsync init --username [user] --password [pass] https://[project].googlecode.com/svn/trunk/ https://[project].svn.sourceforge.net/svnroot/[project]
After this we just start synch'ing the repositories.
svnsync sync --username [user] --password [pass] https://[project].googlecode.com/svn/trunk/
The above command will fetch all the code, with the version history and including tags and branches.
And this is all to it :). For more information on the svnsync refer to the subversion redbook. Read More