That is why it is always a good idea to get some kind of version control system in place and a few different developers working on it. You can't be expected to spend all of your time working on this project and fixing all of the bugs that will pop up.
It takes about 30 minutes to apply for a sourceforge page, and it takes them 1-2 business days to approve the request. They will give you bug trackers, so you won't need to sift through forum posts to try and find bugs that need to be fixed; they will give you a release system, so you can upload releases to the sourceforge mirrors and not have tons of people downloading from your website. They also give you a forum and other things, but it may be better to just redirect people here for any game discussion and leave that forum to discussing bugs or development related things.
Sourceforge also will provide SVN and/or CVS support. Most programmers would probably be comfortable with one of those rather than alternative systems like Darcs. Since you have used SVN in the past, it may be good to just go with that, but if you do decide to go with something like Darcs I'm sure the programmers will be able to figure it out.
This project is already to the point that a sourceforge site would help, a few posts back I reported a bug which someone else already found. If we were using the sourceforge bug tracker I would have been able to search for it before reporting a bug that was already reported, and you would be able to get a nice list of all the bugs that need to be fixed. All the developers would need to do then is go down the list fixing bugs and marking them fixed.
Though the creation of this sourceforge page will help us all get organized, the main thing preventing us from working on the game at this point is the fact that everything is in game.cpp. That stupid file crashes my IDE half of the time. I already have that new system in place and ready to go, we can keep the same overall design of the project (everything can call everything, lots of global variables), by splitting up the project in the way I showed in that file I linked to in one of my previous posts. This will prevent us from having to make any major changes to the code and risk breaking more things. Really all we would need to do is copy the functions into different files at that point.
I also have some experience working with GNU automake, autoconf, etc. That is the preferred system for these kind of things. We could easily make the project work with that system (and have other makefiles in place for windows). The first thing that we need at this point, however, is a sourceforge page.