As a team,
 - choose a Team Name that is more fun/interesting than the number I provide for you
 - create a Team Contract for the Final project that describes your team work goals and responsibilities
 - use Markdown format and push it to the doc/ folder of your shared team repository

Individually,
 - submit a copy of this form to indicate your agreement with the Team Contract


The contract needs to be written as a team and include specifics to address all of the following issues:
  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)

As a reminder, here are the expectations for each student for this project:
    https://www2.cs.duke.edu/courses/compsci307d/current/admin/individual.php