---
# System prepended metadata

title: Contract

---

# Contract

### Team Name
Tinglong and Friends
TAF

### Extensions

**Making Characters extensible**: 
create completely new characters
based on a single configuration 

**Game Genere**

Scrolling Platformer/Puzzle

### CONTRACT

  1. Team meetings: 

        (a) when and how often to meet (at least once a week);
        (b) how to communicate action items made during the meeting;
        (c) policy for a team member to give advance notice of missing a team meeting and work required to make up for it;
        (d) policy for handling disagreements, major decisions, or priorities during the meeting

 2. Communications:
      (a) choose a preferred channel of communication (e.g., Zoom, e-mail, WhatsApp, Slack, etc.);
      (b) decide on an acceptable response policy (e.g., respond within 24 hours);
      (c) policy for keeping everyone up-to-date on major decisions, changes, or updates 
      
      
  3. Helping each other: 
      (a) confirm each team member will ask for help when needed;
      (b) confirm each team member will "go above and beyond" as needed to support the team and even other teams
      

    

  4. Commitments:
      (a) confirm each team member will do work to the best of his/her ability and on time and provide commitments others on the team can rely on;
      (b) policy for resolving failure to meet commitments;
      (c) policy for reaching out to instructors if commitment issues cannot be resolved within the team (e.g., after 2 tries, or after a team discussion)
      
      b: 
      
1a. Status meetings at least once a week, hopefully twice a week. Try to pair program as often as possible. https://docs.google.com/forms/
1b. Issue tracker on gitlab
1c. Use the issue tracker between meetings to keep each other track
1d. We should discuss design decisions that affect everyone so that all inputs are considered. Pros and Cons lists
      
2a. Slack

2b. Respond within 24 Hours... or else

2c. Message about design decisions (?)
When questions about someone's code or refactoring their code: private message on Slack.
Announce major changes on Slack, Gitlab issue tracker

3a. Everyone will communicate with each other when they need help and teammates will provide help when others need it.

3b.Private message on slack and speak to them about how they're doing. Try to reassign roles to best fit their work schedule/preferences

4a. All teammates will work on the project to the best of their ability and communicate updates to the team regularly. 

4b. Teammates will try to step in and make sure any outstanding issues get finished. 

4c. If the situation gets particularly bad then the instructor or TA will be consulted in order resolve the issue. 