First of all, working on larger changes is now much easier for external developers who are not part of the stable ezQuake developer team. Github allows anyone to create a public branch (fork) of ezQuake's code and submit changes to it. (Note: this does not mean all your coding, like experimental changes, must be public.) This allows for much better cooperation with the ezQuake team:

+ You don't need ezQuake's team permission to commit code changes to your own branch. Your fork is yours. You can do whatever you want in there.
+ You don't need to send us patches via e-mail anymore. You just publish your changes in your own public forked repository.
+ You have a solid place to discuss your changes with anyone. Your changes are public and anyone can submit comments even on every single changed line (!)
+ You can submit a "pull request" to ezQuake and if the team likes your changes, they can easily merge them from your repository into the main ezQuake source code repository instantly.
+ You get all the standard benefits git gives you, like ability to work offline, fast branching, stashing, and so on.

In recent years a couple of developers contacted the ezQuake team with their ideas for larger improvements in the source code. Often the single central code repository didn't offer as many possibilities for cooperation as would be useful in given moment. The ezQuake team hopes the concept of "Social coding" of github.com will change this.

ezQuake @ github