| I'm doing a Java project with a few other people for school, and I am about to tear my hair out. We don't actually have that much code (actually a trivial amount :P), but it's split up into a bunch of different files, and it's becoming impossible for anyone to do any work without everyone else present, because no one knows what changes other people are making. Yeah, it's mostly a planning problem, and I've ironed that out (Hah! A geek with a take-charge attitude! I feel dirty...), but I'd like some advice on versioning from the UFie community. Essentially, the problem is this: e-mail is not a good version control system. I, as the systems geek in the bunch, would like to set up some central source where everything could _go_, so I don't have to call people up to yell at them to e-mail me their bugfixes. Our deadline is almost up, and I think most of our work is now going to be done in a central spot, but for future notice... what would be something good to set up for version control? An ftp server? CVS? (or is that overkill?) Mind you, I'm the only one who isn't in the thrall of the Great Bill, so any server would need a windows client, preferably a graphical one... Or is any sort of central thing overkill, should I just set up a central GMail account? The thing is, when you're done with your coding, it's much easier/more efficient to hit 'sync files' (or type it, or whatever..) than to pop up a mail client, send a file with attachments, title it descriptively, and hope your changes get caught by other people making modifications. |