|
-
Jul 1st, 2001, 03:48 PM
#1
Thread Starter
Frenzied Member
-
Jul 1st, 2001, 05:51 PM
#2
Im taken, but I will give you a few tips on how to get it started out right.
Make sure that everyone in your team knows what is going on all the time. If not, people get lost, and things go *flush* =).
Try to get people to check in as often as 2 or 3 times a week. If someone has to go on vacation, or some such, make sure everyone knows.
IMPORTANT: Before you write a single line of code, create the design docs. This has stuff on how everything works together, the aims of the project, all the way up to what spells you will have, weapons, etc. Get the basic subsystem functionality down before you even start. Plan the project.
Keep your code safe. If you are working on something, make a copy of the code, and use that. Make some directory on your comp to hold any code that has been finalized. If you get something working, have everyone else working on the project to approve it, and test it, before you add it to the Final Code Directory. Then, if one person changes something you can fall back to something. that works.
You get the idea. Hope everything goes well for you.
Z.
-
Jul 2nd, 2001, 01:55 AM
#3
Thread Starter
Frenzied Member
Would a use of a CVS Database help?
.. The rest seams pretty logic but I guess that somethings could be overlooked ..
=], Thanks for the info.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|