1
edit
Changes
no edit summary
*Effective team work should produce '''high-quality code''' base. Team work is not an excuse for being lazy.
*Select a team leader who is responsile responsible for merging branches with trunk.
*Divide the work of A1 Release 0.2 among the team members. Each team member should be responsible for developing one specific C++ class (e.g. CButton).
*Each team member should create a branch to work on that class.
*A branch should be labelled by the name of a team member (e.g. john).
*Everyone on the team can '''debug''' the source code in any of the branches. (*Warning: The number of bugs fixed for a particular class reflect the '''quality''' of code initially developed (contributed) by the team member. This could affect the final marks that a team member could receive. In brief, each team member should '''work as hard as other team members'''. Do not contribute '''poor quality''' code to the code repository (i.e . the shared code base). At the end of the project, a group evaluation scheme will be used to asses the performance of each team member.)