How to Submit Your Homework

In this course, we will use a local (Enterprise) GitHub as our version control and repository system. That GitHub site is located at github.ccs.neu.edu. You should visit this site as soon as you have a CCIS ID so you can initialize your account there.

We will create a private repository for you at the GitHub site for CS 5010. We expect you to commit and push your work to this repository at the end of every work session. When begin to work in pairs, we will create a repository for each pair, shared between you and your partner.

At the end of each work session, you must do three things:

1. Fill out a work session report and place it within your repository, outside of the directories you created for the problem sets.
2. Commit and push that work session report.
3. Commit and push all of the files in the directory that contains the solution you are developing for the current problem set.

You must also fill out a form describing your preferences for codewalk times the following week, but you only have to do that once a week, before Saturday evening.

If you do not commit and push your files daily, we will assume you are not working on the assignment. If you commit and push only the final version of your assignment, we will suspect you stole the code from somewhere. Even if you wrote all the code yourself, violating course rules by not pushing intermediate versions may lower your grade.

Checking in your partially-completed assignments also serves as a backup in case something happens to the files on your personal machine. (Your dog won't eat the GitHub site.)

Your homework will be collected automatically from your repository at the date and time listed on the problem set (usually 6pm local time on Monday).

Your homework for problem set JJ should be committed and pushed to your repository in a directory named setJJ.

• Problem sets may contain more than one part. Each part should be submitted as a single file within your setJJ directory.
• Some parts of a problem set may specify the name of the file you are to use. If so, use that file name.
• If part K of a problem set does not specify a file name, then your solution for that part should go into a file named qJ.rkt. For example: In Problem Set 01, your solution to part 2 (Exercise 14) goes into a file named set01/q2.rkt.
• If your solution is in a file named set1/q2.rkt, Set01/q2.rkt, set01/question2.rkt, or any other name that is different from the one and only correct name, then our automated testing scripts won't find your file and a variety of bad things will happen.

Be sure to include all of the deliverables.

We have specified coding conventions we expect you to use for this course. Following those conventions will improve your life and ours.

Your problem sets will be graded according to the rubric we have described. Some details and points of emphasis will change from week to week, but those general standards will remain the same throughout the course.