[Quickget-develop] Before developping project

[Aegir S. <Aeg...@Su...>]

Hi, team:

I know you are anxious to begin developping the software. But we should 
enforce some rules to make our software better.

1. Communications
Ramit has discussed with me and emphasized the importance for the 
communication. I agree an instant messenger will give much more 
convience. I think Yahoo messenger and MSN messengers will be the best 
choices.
My Yahoo Messenger account: aegirsun
MSN account: aeg...@su...
If you have accounts for these tools, could you tell others your 
accounts? So we can discuss the issues in a timely manner.

2. Coding Convention
To make us following the same coding style, we should all follow a 
coding convention. I think java's coding convention is good enough to 
follow. You can get a copy of java coding convention at 
http://java.sun.com/docs/codeconv/.
To other bad smells in our code, we should try to avoid them and 
refactor them when we find them.

3. Check in the source when it works well
Do not check any test code into the production cvs. And before checkin 
the code, please make sure the source code can be compiled and passed 
basic acceptence test ( I will make some basic acceptance test in the 
next month). If you checkin cannot be compiled, it will block other 
developers. And in some cases, I will rollback the change. BE CAUTION, 
FORCE UPDATE IS VERY DAGEROUS.

4. Code review / Pair Programming
Code review is a good method to assure the program quality. And I think 
if you do pair programming, you code can be reviewed by your patener. 
Now, it is not mandatory in this phase. But when the project goes into 
rump down phase, we should enforce the code review policy.

Maybe I have missed something here. And welcome to add your ideas to 
this list.

Regards,
Aegir