(I made dev forum public, because there’s not really any reason to be secretive about anything we have going on)
I want to move at least S44Main.sdd to github. SVN sucks and so does Sourceforge. Github has a beautiful interface for issue tracking and collaborative work: next time (if ever) someone comes along with new sounds or something they want implemented, they can just submit a pull request to us. all we have to do is review to make sure it isn’t awful, and hit ‘accept’ … blammo, contribution accepted.
git is also really nice for when you have a large body of work (like, say, Lua unit scripts) that you want to work on in parallel to the main build without mucking up main. Branches can be purely local, and switching between them is painless and fast. It also makes making builds easier, since prepping it just requires copying S44Main.sdd and removing the .git directory, rather than asking SVN to do an export (which takes a good 10 minutes on my old laptop).
I know that I’m probably the only current contributor (excepting koshi) who uses git a lot. I’m also suspecting that I’m the only one (again, excepting koshi) who prefers command line stuff to GUIs – I’m doing all my coding in tmux and vim these days
Fortunately, the git GUI situation has improved a lot in the time since Spring moved to git. The nicest windows one is probably GitHub for Windows. There’s also TortoiseGit, which has a very similar interface to TortoiseSVN.
The key commands for interacting with S44-as-git-repo vs S44-as-svn-repo are very similar: git pull == svn up, git add == svn add, git commit + git push == svn commit. that’s pretty much it. GitHub for windows abstracts most of this with a “sync” button.
I’ve already created a Spring 1944 organization and repo for S44Main: github.com/spring1944/spring1944 – take a look!