As of July 21, Duality has move from google code to GitHub. Although google code and SVN provided a great platform for “personal” Open Source projects, Git(Hub)s focus on collective development and decentralized version control eventually convinced me to move. Although Git and GitHub seem to be quite popular these days, both were pretty new to me and I had no idea where to start; so I did a lot of superficial google research and forum inquiries.
The first thing you’ll need is a decent Windows client for Git and I’d strongly recommend to at least take a thorough look at SourceTree. It’s available for free, doesn’t require you to separately install Git and has a really nice interface that eases your daily workflow if you’re not a console ninja. Once you’ve got the tools, you’ll need to know how to use them. To acquire some basic knowledge, I’ve found this website quite useful.
So, what does that all mean for Duality?
- It’s a lot easier to maintain a personal / “flavored” version of Duality locally while still receiving official updates – thanks to Git.
- You’ll be able to directly contribute to Duality by submitting source code. Simply fork the Duality project on GitHub, introduce changes and then file a Pull Request. I’ll review your code and consider it to be included in the official master branch.
- Since Git hasn’t been designed to handle large binary files, most binary downloads are no longer part of the repository but stored elsewhere. You’ll find them all on the Downloads page.
- Issue Tracking remains mostly the same, but looks a little different.
- The Duality Wiki is now editable by everyone on GitHub, not just direct project contributors. What are you waiting for? Go write some articles! 😉