* Your St. Olaf username: (select name) Abusharkh, Mazen Bauswell, Deandre Beleznay, Soma Caballero, Jesus Cabbage, Jacob Cao, Annie Cardell, Magnus Eanes, Spencer Ge, Muchen Gurung, Kshitij Ireland, Brenden Jones, Peter Jorenby, Ben Kosherbay, Ru Lee, Andrew Manning, Schyler Meier, Danica Mwendamberi, Tari Nesbit, Ross Raduege, Andreas Scott, Collin Shah, Deepak Skalski, Harrison Steenson, Abby Swan, Nathan Thiede, Brodie Valent, Hugo Vo, Thong Yadav, Nikesh Prof. Brown

* Your project team: (select team) books/Big Bad Bob's Bargain Bookstore (cabbag1,eanes1,thiede1) inv/Jesus Caballero (caball1,nesbit1,swan1,cardel1) maze/Mac and Trees (meier3,scott3,skalsk2,jorenb1) pantry/Too Many Cooks (belezn1,valent1,radueg1,irelan1) pausec/Order of the Lion [customers] (abusha1,leeas,shah2) pausek/Order of the Lion [kitchen] (gurung1,kosher1,yadav1) po/Post Office Team (cao1,ge1,vo4) stogame/Code Goats (steens1,mannin1,jones10) indiv/Individual project (mwenda1,bauswe1)

* Checklist of final deliverables - check all that apply

1. We have added and updated documentation in our project code, which focuses on the structure and strategy of the code. The documentation needs not be "deep" or extensive, but it should help a reader/later developer of your code.

2. We have pushed final versions of our project source to our team's assigned stogit repository in the mca-i18 group (see repo assignments). This includes

   1. mobile app

   2. Java backend server

   Notes:

   • If you did your work using a different git repo other than your team's project repo in the mca-i18 group, make a fresh clone of your repo (e.g., on a Link machine) and push to your team's repo. For example, suppose that

     • proj is the code (e.g., books or pantry) for your assigned stogit repo
     • your-other-repo is the URL for your non-mca-i18 repository, e.g., git@stogit.cs.stolaf.edu:email/proj.git or https://github.com/email/proj.git
     Then you could carry these instructions out on a Link machine where

     mkdir finalproj
     cd finalproj
     git clone your-other-repo   proj
     cd proj
     git fetch
     git remote add mca-i18 git@stogit.cs.stolaf.edu:mca-i18/proj.git
     git pull mca-i18 master
     git push mca-i18 master
     

     This will submit both your team's source code and git commit history, (both required).

     If you want any branches besides master to be considered for grading your project, pull/push those branches too, e.g.,

     git checkout devel
     git pull mca-i18 devel
     git push mca-i18 devel
     

   • If you used multiple repos for your development,

     1. request additional stogit repo(s) in the mca-i18 group using this form, and

     2. after any additional repo(s) has been created for your team, follow the instructions above to submit your work in additional repo(s).

3. Our project's main git repository mca-i18/proj includes a file README.rab in the master branch top level directory that provides build information, descriptions of branches other than master, additional repositories that are part of our submission, and other relevant information about our project submission.

4. We have submitted final PDF versions of our features list, ER diagram, technology list, and a PDF of our final presentation slides using this form.

   1. We have shared any google docs/presentations/etc of the above and any other relevant items with rab@stolaf.edu, and added their URLs and descriptions to the file README.rab.

5. We have submitted our project database by one of the following methods

   1. Our database is the assigned Postgres schema for our project listed in this Piazza posting.

   2. We have submitted an SQL dump of our database, and added information about where to find it in README.rab

   Notes:

   • If you used a different database besides the Postgres schema assigned in this Piazza post,

     1. Create an SQL dump of your database, i.e., a single file with SQL instructions for recreating that database, including database table definitions, data insertions, etc.

     2. Upload that SQL dump file to Google Drive, and share the resulting drive file with rab@stolaf.edu

     3. Add the URL of that drive file and a description to README.rab

     If multiple non-assigned databases, submit each by this method.

6. If we have data files that are essential to our project but not appropriate for git submission,
   we have submitted any such files as follows:

   1. Create a tarball or zip archive of your files. For example, on a Link machine or Mac terminal window,

      tar cfz mydir.tar.gz mydir
      

      where mydir is your directory of files. On Windows systems that do not have tar, create a .zip archive of your files.

   2. Upload that tarball or zip archive to Google Drive, and share the resulting drive file with rab@stolaf.edu

   3. Add the URL of that drive file and a description to README.rab

Team comments (optional. Include any deliverable information in README.rab)