The second phase releases Before continuing stage 2, please do the following# Read [[Hints for Using SVN to collaborate on school projects]]# Update your team's wiki page with your team's repository path information under '''Repo Path'''# Create a draft directory with your seneca id under the branch sub-directory of your game without sound or input controlteam's repository. This will be your home directory for development; for details see: [http://zenit.senecac.on. ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Directory_Structure Directory Structure]# One of your team members should export svn://zenit.senecac.on.ca/btp300_113/trunk into the trunk of your team's repository#: For detailed steps see [[Hints for Using SVN to collaborate on school projects#Start_the_project_by_continuing_an_existing_work | Start the project by continuing an existing work]]

This Each team member should have their own successfully compiled version of the assignment 1 in their own workspace in the branch sub-directory of their team's repository.Branch submission path: svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment1 : ''Start doing the above by branching the Framework into svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment2. See here for help: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Preparing_Branches.2Fworkspace_for_development Preparing Branches/workspace for development]''  The source code for the upgraded sample should include the following updates:* your own name in the caption for the dialog box* your team name in the window title  Merge all of the team members' Framework workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk] for details  The purpose of this first phase of the project is twofold:* to define your last opportunity game in both scope and detail and thereby to amend give your original proposalinstructor some idea of your design, modify so that your designinstructor can give you some feedback whether what you intend is too simple, too complex, or about right* to show your instructor that you are ready to work with your own branch of your team's repository and obtain ready to start modifying the framework to suit your instructorteam's feedback design. Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page. Your team should arrange a time and date to meet with your progressinstructor to review your proposal and to identify the different responsibilities of the team members. This meeting should take place during week 6 of the semester.