/**********************************************************************
 *  readme template                                                   
 *  Hello World Assignment                       
 **********************************************************************/

Name:

PennKey username (e.g. bjbrown):

Section (e.g. 203):

Do you have a laptop you can bring to office hours/section?

Operating System (e.g. Windows or OS X):

Text editor (e.g. DrJava):

Hours to complete assignment (optional):


/**********************************************************************
 *  List some information (optionally) to help your preceptor get
 *  to know you.
 **********************************************************************/

Nickname:

Year:

(Likely) Major:

Confidence level (0 = very afraid, 5 = very confident):

Do you have any previous programming experience?

Why are you interested in taking computer science?

What other interests do you have?

/**********************************************************************
 *  What are the dates of the midterm and final exams?
 **********************************************************************/


/**********************************************************************
 *  Have you read the CIS 110 style guide?
 **********************************************************************/


/**********************************************************************
 *  Have you created a SEAS account, or did you already have one?
 **********************************************************************/


/**********************************************************************
 *  Have you registered for the Piazza discussion board?
 **********************************************************************/


/**********************************************************************
 *  List whatever help (if any) that you received. You don't need
 *  to include the course materials, but do include the names of
 *  classmates or TAs that assisted you.
 **********************************************************************/



/**********************************************************************
 *  Describe any serious problems you encountered.                    
 **********************************************************************/




/**********************************************************************
 *  List any other comments here.                                     
 **********************************************************************/



/**********************************************************************
 *  After reading the course collaboration policy,
 *  answer the following quiz. This counts for a portion of your grade.
 *  Write down the answers in the space below.
 **********************************************************************/

1.
2.
3.
4.
5.
6.
7.
8.


1. Collaboration on programming assignments.
   (a) Is not permitted.
   (b) Is permitted in the form of discussions of how to approach
       the problem and suggestions for how to debug.
   (c) Is permitted in the form of writing and debugging a program
       together in groups of no more than two.
   (d) Is permitted in the form of letting someone else write a program
       and then changing a few variable names then turning it in.

2. The typical penalty for submitting plagiarized code in a programming
   assignment is.
   (a) Zero for the assignment.
   (b) Failure in the course.
   (c) Hearing before the Office of Student Conduct
       (if convicted, typically suspended and failure in course).
   (d) Expulsion from the University.

3. The penalty for knowingly abetting an act of plagiarism (e.g., by giving
   another student a program to plagiarize) is, in principle,
   (a) No big deal.
   (b) Hearing before the Office of Student Conduct, with typical penalties ranging
       from Probation to Expulsion.

4. The penalty for unknowingly cooperating with someone (e.g., by leaving your
   programs in a publicly readable directory) is
   (a) The same as for knowing cooperation.
   (b) If you can convince the Office of Student Conduct that the program
       was taken without your consent, they might let you off, but it
       would save a lot of trouble if you had protected the directory
       in the first place.

5. The penalty for giving someone hints about how to do a programming
   assignment and helping them interpret error messages is
   (a) No penalty, this is perfectly acceptable.
   (b) Hearing before the Office of Student Conduct, probably get off
       with Letter of Warning.

6. You may show another student the actual code of your solution to a
   programming assignment
   (a) If it's past the due date.
   (b) If they promise to look at it for reference only, then throw it
       away before writing their own solution.
   (c) If that student is a tutor or member of the CIS 110 staff.
   (d) If that student is helping you debug your program and that student
       is not currently taking CIS 110.
   (e) If you are helping that student debug their program.

7. You may e-mail another student the actual code of your solution
   (a) Never.

8. We're dragging you through this exercise because
   (a) Penn students can't be trusted.
   (b) Penn students have great integrity but are often under
       severe time pressure and a clear understanding of the rules
       can never hurt.