================================================================
  CS314 Spring 2016  Grading Rubric                   
 Assignment 1 (A1): Team Development using Eclipse and Git
================================================================

Student Name	: ___________________________  

Total Points (out of 60): ______________

===============================PART 1===========================
Team Portion of Grade: Submission: 20 possible points.
================================================================
1. The names of all team members must be at start of each file
   (as comments on java files and at the top of overview.txt).
   -1 if names missing 

2. 10 points
   + The package should be in directory cs314_A1 and be named cs314_A1
   + On extracting from the jar file, all submitted files
   (AdventureGameView.java, AdventureGameModel.java, ... , overview.txt)
   should get unpacked into directory src, package cs314_A1
   + The cs314_A1 package should contain all of the java files, and
   the src directory should contain the overview.txt file.
   + No class files or other unneeded files are in your jar file.

3. 5 points
   + Compile: Files should compile successfully and without warnings.
   + Run: Your program should start without warnings and take user input 
   without crashing.

4. 5 points
   Overview.txt file: 
   + Names of all team members.
   + Specific contributions by each team member.
   + Time spent by each team member.
   + The CSU Honor Pledge:
     "I have not given, received, or used any unauthorized assistance." 
     with the team members' names listed below.

Error code key:
--------------------
E1: missing source files
E2: incorrect packages or structure
E3: extra files included
E4: errors with compilation or running program
E5: problems in overview.txt file
E6: team names not included in all source files

=============================PART 2=============================
Individual Portion of Grade: Development Process: 40 possible points.
================================================================
1. 10 points
  - 5 points for committing directly to the master branch
  a.(3) GitHub logs for the team repository show at least 1 branch for each student on 
    the team.
  b.(2) Branch name is descriptive of the changes made, including a way to tell which 
    student is working on it (e.g. GGfixWarn, JBcomment, SMcomment).
  c.(1) Branch commits occur often, with a small amount of changes in each commit.
  d.(1) Branch commit logs are descriptive of the changes made.
  e.(1) Multiple pushes have been made to each student branch.
  f. Merges from other teammates' branches to the student's branch have been made.
  g. Merges from the master to the student's branch have been made.

2. 10 points
   -4 points for making a pull request and merging without asking for review
   -2 points for merging someone else's pull request review
   -2 points for not adding a description in the pull request
   GitHub logs for the repository pull review system show the student has requested
    reviews of their proposed changes to the master.

3. (10) GitHub logs for the repository pull review system show the student has reviewed 
    their teammates proposed changes to the master. 
4. (10) GitHub logs for the repository show that all student branches have been merged 
    into the master.

Error code key:
--------------------
2E1: working directly on the master
2E2: pull request created and merged without asking for review
2E3: merged someone else's pull request
2E4: no description on pull request
2E5: branch name doesn't indicate student working on it
2E6: no comments on any teammates' pull requests
2E7: no pull request created
2E8: didn't create a branch