M2 Code Contributions

• Instructions
• Grading Rubric

Instructions

Each and every team member must make satisfactory code contributions as per the coding tasks they planned for Milestone M2.

• Follow the Workflow! All code contributions must follow the project workflow. No credit will be given for work that does not follow the workflow
• Use Your GitHub Account! For a particular team member to receive credit for code contributions, their account must have been used to make the commits and pull requests. If another team member’s GitHub account was used, that team member will receive the credit.
• Working Code Only! Broken code has no value in this course. No credit will be given for broken code.
• Sufficient Contributions. Each team member’s M2 code contributions
  • must be reflective of at least 6 hours of work by an average student,
  • must include the implementation of at least 2 scenarios, and
  • must be submitted in at least 2 pull requests.

Grading Rubric

• High-Pass:
  • Expectations regarding the quantity of coding work to be completed in the iteration were clearly met.
  • The project workflow was followed correctly for all tasks, including the correct use of topic branches, pull requests, and the inclusion of video demos in the pull requests.
• Low-Pass:
  • A borderline quantity of coding work was completed in the iteration.
  • The project workflow was mostly followed, with only a few minor mistakes.
• Fail:
  • A clearly insufficient quantity of work was completed in the iteration.
  • Significant mistakes were made in the performance of the project workflow (e.g., not using topic branches, pull requests that do not follow instructions).