I've been thinking about ways that those of us who will be doing DLL modding can collaborate better. I'd brought up the idea of reviving the old CCCP (Civilization Core Community Project) earlier but it was pointed out that people found it hard to continue that and other DLL projects. Even those most of us make our code public the best tool available to us before was SVN and SourceForge but its still quite a pain to make and create such projects and pulling in code you want from another mod is a whole bunch of Winmerging. I've also been thinking that the old CCCP concept was too centralized, it's not practical to have that many people working on one code base. I think their may be a better way. It seems that the popular unix source control program git has finally got a windows GUI front end now. It's called msysgit and while its still in beta looks like it could do the job. If we put a copy of the raw SDK along with any patches/expansions as the 'root' and we all then fork off it we can have many little branches with fixes and improvements. People can then cherry pick and pull in these branches to their own DLL's and best of all we can update our DLL's when new official patches/versions are available by pulling in from the trunk. And this can all happen without any central clearing house or bottle neck. Now I don't have much experience with Git so this is all somewhat speculative as to the benefits but from what I've read of git the kind of uncoordinated community development is exactly what its geared towards. If anyone more familiar with git and how it really works in practice could put in their two cents? Would it be worth the time to learn and use? Are their any major hurdles I'm not seeing?