Moving to Github

Here at Vurve we're big fans of the open source community at large. Our technology stack is built of the backs of numerous open source libraries and frameworks, and hacking on open source projects is a great way to hone your programming chops as well. Over the last few years, Github has emerged as a phenomenal service and tool for open source collaboration.  In the olden days, you had to sign up for mailing lists and join IRC channels if you wanted to be kept up to date with your favorite project. The process has been streamlined, and it's very easy to share patches and keep up to date with commits to projects with Github.

Just this last Sunday, Vurve made the decision to switch our primary code hosting from an internal SVN repository to Github. The process was surprisingly easy, and for most repositories this proved to be as simple as setting up a comprehensive svnauthors file, checking your projects out of svn with git-svn, adding a new remote (in this case, Github itself), and pushing your repository again. The process we followed for the migration is detailed on Github's wiki here.

One of the many reasons why we wanted to move to Github was also to share some of the code projects we've been working on internally, and to be involved in the development of the technology that powers our services. Keep an eye on our Github page!

Mike, Open Source Anarchist

Comments

[phil]

We just moved from Assembla to Github earlier this month. Wondering why we waited so long.