1
edit
Changes
→Collaboration Requirements
== Practical Guidelines Instructions ==
*READ the SVB book at red-bean.com. (FYI - Resources on the course wiki page.)
**Understand the concept of source code version control.
** Subversion Branch Merge Tutorial [http://www.youtube.com/watch?v=4WC44T89VrY&feature=relmfu]
*Download and install TortioseSVN. Read the documentation whenever needed.(FYI - Resources on the course wiki page.)
*Each team should receive SVN accounts on zenit.senecac.on.ca.
** svn://zenit.senecac.on.ca/btp300_123arepXX, XX - one numeric digit
** svn://zenit.senecac.on.ca/btp300_123brepXX, XX - one numeric digit
*Set up the following directory structure for your SVN code repository
<pre>
== Collaboration Requirements ==
*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 assess the performance of each team member.)