Code Workflow
Contact us if you wish to contribute via email (or sneaker net), we'll handle the repo's for you!
ANTz team uses a 'Forking Workflow' with each developer having their own pair of repositories individually organized using 'Gitflow Workflow' conventions.
To contribute, fork the project to your own repo, make code enhancements and then submit a merge request to the central repo: https://github.com/openantz/antz
The central repo has branches for core platforms: MSW, OSX, Linux.... Additionally, there are separate forks with projects for building libraries or other custom systems. If you don't know git then try Atlassian SourceTree.
Below are excerpts and images from Atlassian tutorial Comparing Workflows.
"The Forking Workflow... gives every developer a server-side repository. This means that each contributor has not one, but two Git repositories: a private local one and a public server-side one.
The main advantage of the Forking Workflow is that contributions can be integrated without the need for everybody to push to a single central repository. Developers push to their own server-side repositories, and only the project maintainer can push to the official repository. This allows the maintainer to accept commits from any developer without giving them write access to the official codebase." - Atlassian tutorial Comparing Workflows.