====== Final Project ======

~~NOTOC~~

^ teamX ^ Partners                                                         ^ Description         ^ Last Activity ^
| team1 | Casey B. (caseybm) \\ Preston (CapnAwesome)                     | //Lemonomics//       |               |
| team2 | Allyson (allysonjp) \\ Max (maxmorris)                          | //Minesweeper?//     |               |
| team3 | Luke (lugehorsam) \\ Zach (zachwilson)                          | //Rogue-ish//              |               |
| team4 | Otavio (otaviogaiao) \\ Tom (thwiechert)                        | //Pacxon//           |               |
| team5 | Kevin (kevinqiu) \\ Casey H. (caseyh)                           | //Super Tetris//     |               |
| team6 | Alex (alparayannilam) \\ Dan (damccormack)                      | //Space Invaders//   |               |
| team7 | Cat (morgcat11) \\ Harris (harrisBgordon), \\ Morgen (mowarner) | //Pacman//           |               |
| team8 | Mike (mikebeau99) \\ Eliot (eliotcowley)                        | //Asteroids//        |               |
| team9 | Henry (holsley86)                                               | //Automata//         |               |
 
//** GitHub Repositories: **//   \\
**''git@github.com:Vassar-cs203/teamN.git''**


===== Final Project Presentation Format =====

  * Wed, May 8, 12-2pm, OLB 105

  * Description and Demo of Game
  * Javadoc (interface) view of classes
  * Code (implementation) view of classes: fields, key methods
  * Testing
    * run your tests
    * explain in detail how you tested one of your methods
  * 10 minutes per group

  * Final writeup
    * 1-2 pages
    * each partner does own writeup
    * describe project, design, challenges, overall project experience. 
    * due: end of day Wednesday, May 8. (after group presentations)


===== Initial Setup =====
**One partner only:**
  * login to your CS account and ''cd'' into your ''cs203'' course directory
  * clone your GitHub repository: <code text> 
$ git clone git@github.com:Vassar-cs203/teamN.git
</code>
  * launch Netbeans and create a new project in your ''teamN'' directory (where the value of N ranges from 1 to 9, depending on your team number)
    * note 1: the Netbeans project you create will be your actual final project
    * note 2: you should name it accordingly: e.g., FinalProj, ZombieDice, Pacxon...
  * ''cd'' into your ''teamN'' repository directory and add your Netbeans project directory to your GitHub Repository: <code text>
$ git add FinalProj
</code> Note: be sure to specify the actual name of the Netbeans project you created---in my example, I used the name ''FinalProj''
  * check the status of your repository following the ''git add'' command: <code text>
$ git status -s
</code>
  * take a snapshot of your newly created final project: an initial commit to the repository <code text>
$ git commit -m "initial commit of final project"
</code>
  * check the status once more: <code text>
$ git status -s
</code>
  * finally, push your committed changes to the GitHub repository: <code text>
$ git push
</code>

\\ \\

//**Other partner(s)**//

Now the partner(s) who didn't perform the above steps can clone their own copy of the repository! 
  * login to your CS account and ''cd'' into your ''cs203'' course directory
  * clone your GitHub repository: <code text> 
$ git clone git@github.com:Vassar-cs203/teamN.git
</code> (where the value of N ranges from 1 to 9, depending on your team number)
  * launch Netbeans and open the project your partner just pushed to the GitHub repository!
    * you should find it under your ''teamN'' directory 

\\ \\ 

//**Team Development Cycle**//

Now that you and your partner(s) have your own local copies of your GitHub final project repository, your everyday lifecycle will generally involve some sequence of the following git commands: <code text>
$ git status -s
$ git add filename
$ git status -s
$ git commit -m "your descriptive commit message"
$ git status -s
$ git push
$ git status -s
$ git pull
$ git status -s
</code>
Note: you can never check the status of your project too much. When in doubt, check the status!  If you need more status, drop the ''-s'' option: <code text>
$ git status
</code>

The git add and commit commands add new files to your local copy of the repository, and take snapshots of the state of your project at the time you commit. The git push and pull commands are how you share your local changes with your project partner(s), through the remote GitHub repository. 

Learning to use Git, and general version control concepts as part of a team, are an important part of this final project. I encourage you to consult git resources and tutorials, ask questions, and share what you learn about using git with the class!