GAM666/DPS901 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources
Game Name Goes here
Workflow
We will control our own branches off the project trunk. There you will implement your new code in a bug environment. Code will then be submitted to trunk bug free, and all branches will be updated to trunk revision. Teammates are not required to use IRC, but the tool is there for team contact and help from others.
Meeting Goals
Tuesday
When: 9:50 (after GAM666) Where: Tel Open Lab Goals:
- Mandatory
- Evaluate goals from last week (not meet/exceed) Why? Why not? Can we maintain pace?
- Define goals for this week
- Review code and playtest before trunk submission
- Update branches to trunk revision
Thursday
When: 9:50 (after GAM666) where: Tel Open Lab Goals:
- Occasional
- Mandatory
- Rollback trunk if bugs exist, update branches, re-evaluate goals
- Team collaboration and work time
ToDo
- Divide workload
(carl) my proposal would be dividing the game along these lines
- audio
- input
- video (world and impassable terrain)
- video (actors and movement)
Team Members
- Group Email
- David Seifried, Some responsibility
- Carl Desautels, Some other responsibility
- Denny Papagiannidis, Some other responsibility
- Sasha Atijas, Some other responsibility