Tuesday, 17 March 2015

Google Code to GitHub, Subversion to Git

Google Code is shutting down.

Although there was no need to rush our decision (the site will not become read-only until 24 August), the FreeRCT dev team began discussing alternatives straight away.

The discussion started with where to move the project to (GitHub, SourceForge, Bitbucket, or self-hosted). Of course, moving the project to one of the aforementioned options also meant a likely change in the version control system (VCS) used (see: allowed).
  • GitHub (GH) primarily supports Git (of course), with some Subversion support that we did not think would be worth dealing with.
  • Bitbucket would give us more flexibility with its support of both Mercurial and Git; nevertheless, the interface is somewhat lacking when compared to GH, and searching for projects as an anonymous user is not as user-friendly (not helpful for project visibility).
  • SourceForge (SF) would allow us to stay with Subversion; of course, this would mean using SF's interface, something that none of the devs seemed particularly excited about. 
  • Some other sites and VCSs were mentioned, if for nothing more than to provide a bit of jocularity to the serious discussion. 
  • Finally, the team briefly discussed the possibility of going the self-hosting route. Although we may eventually go down this road, it was decided that there is no real need for it in the project's current state.
After receiving feedback from the rest of the team, it was decided to make the move to GitHub. Admittedly, the team was in a state of wonder as to how the entire process would go, especially with regards to how GitHub would handle Google's wiki format and the fact that we already had a Read-only mirror in place at GitHub.

Lucky for FreeRCT, we had the unique combination of our own LordAro, as well as Google's (admittedly fancy) 'Export to GitHub' functionality.

Operation successful: FreeRCT.

With the move to GitHub complete (minus a few small changes being made as I write this), the team can refocus its efforts on making this awesome game.

Hopefully this post gave you a good overview of what was involved in moving the FreeRCT project from one site and system to another. As always, you can continue to stay up to date on FreeRCT happenings through all your favorite sites, including checking here at this blog. :)

Until next time,
The FreeRCT Dev Team
"FreeRCT is really good value!"


  1. Don't forget to change the Google Code link at your freerct.org website to the Github link.

  2. how is this coming along? i check in every week or so but there is rarely a blog post... sorry if this double posts.

    1. We don't post at the blog very often, you may want to use an RSS feed to monitor posts instead.
      For details on what we are doing, visit the github site, or the IRC channel :)

  3. Almost a full year without an update on here or via twitter.

    Is this project dead?

    1. they moved to github and this is more or less just remnants of what use to be, on the github it appears the last update was around 19 days ago.

      without knowing what you are hear for, i recommend this
      it's largely what i was hoping for, a way to get rct/rct2 to play nice on a modern pc, thank you 4chan popular threads on the main page for bringing this to my attention.

  4. This comment has been removed by the author.