Team Programming, HOW??

CVS or Subversion or some source control system is vital.

Wiki could be handy, a forum or other type of dynamic website will do as well.

Basically you need a way to manage resources, and a way to communicate (passive and active).

In a group project we just upload our files onto an FTP server with an FTP client. Saves us the headache from CVS. The choice is yours.

I tend to stay away from CVS for all but the larger projects (more developers) I prefer a modular design, develop your project as modular as possiable, and assign a programmer to maintain that module. Then you use forums to piece together modules and deside what needs to be changed from the design end.

I believe modular design is key to a good (team) project, yet there is no need to avoid CVS, especially with tools like TortoiseCVS. Of course, most people, given the choice prefer Subversion.

PS. I should note that TortoiseSVN also exists.

With a version control you can try your teammates changes to their portions almost realtime without waiting for them to zip it and throw it on ftp or a forum, it's not just for code conflict resolution.

One thing that worked GREAT for my team was when we were all sitting in the same room, with a whiteboard where everyone could add new Todo's (we used 3 different colors for priority) and we had these small magnets in different colors (one for each team member) where you would put "your magnet" on the Todo you're working on.

I'm thinking of making a online version :) But maybe a wiki could be used?

Quote:

Original post by Khaosifix In a group project we just upload our files onto an FTP server with an FTP client. Saves us the headache from CVS.

In exchange, you have all the headaches of FTP and synchronizing versions of files, making sure everyone is up to date and doesn't overwrite a newer version.

Seriously, a version control system is indispensable for pretty much any kind of project beyond "Hello world".

Quote:

Original post by Arild Fines Quote: Original post by Khaosifix In a group project we just upload our files onto an FTP server with an FTP client. Saves us the headache from CVS. In exchange, you have all the headaches of FTP and synchronizing versions of files, making sure everyone is up to date and doesn't overwrite a newer version. Seriously, a version control system is indispensable for pretty much any kind of project beyond "Hello world".

I completely agree with Arild here. I had the pleasure of working with a group who refused to use my already avaliable and running subversion server. Everyone just coded around in 1 large spree, uploaded and exchanging like a there was no tomorrow. In the end, we had 2 database classes(Which did exactly the same except that one had the login info hard coded), 3 different versions of the forum files, and some other problems. (Also, the guy who renamed my database class was plain dumb. He hardcoded the login data so it only worked on his machine and never told anyone).

Running an FTP or whatever is going to seriously mess up the project. What if someone deletes all the files by accident? Yes, the joy of lost work!

Setting up Subversion(Which I recommend over CVS or VSS) takes about an hour and getting it all working with the correct privileges another hour. Plus you have the pros of being able to roll back files to previous versions, write scripts to see who/when/what is commited(Never did that, but I heard it was possible), etc.

Toolmaker