CSCI 101 - Intro to Computer Science

Dear CSCI 101 and/or CSCI 102 Student:

The syllabus for 101/102 provides significant detail on what is (and what is not) allowed in this course. We include the information concerning academic integrity on your syllabus below. Common mistakes that students make (which leads to an academic misconduct charge) include:

• Allowing a friend to see your working code to "help them". The friend might say "I won't copy"", but often copying ends up happening.
• Searching online for "how to write a for loop in Python" is totally fine! Searching online for "how to output the integer that indicates the tax amount due in USD for that given filing status and income in Python" (see CSCI 101 Lab4) is not. In other words, using online resources to help you with a programming concept is totally fine; looking for and using online resources to help you solve a particular CSCI 101 or 102 assignment is not.
• Posting a Python assignment on an open forum (e.g., Chegg).
• Viewing a solution to a Python assignment on an open forum (e.g., Chegg).
• You can work with a friend on CSCI 102 Studio problems. All other Python assignments in 101/102 should be done individually (not with a friend). In other words, you and your friend should not be submitting one solution to a Python assignment.

Programming is a creative process (like art). Every "canvas" should be different!

Signed,
The 101/102 Team

Syllabus Details: All students are advised to be familiar with university policy on Academic Integrity. In addition, CS@Mines faculty have adopted a Collaboration Policy for all courses. This policy is a minimum standard; your instructor may decide to augment this policy. You should read the CS@Mines Collaboration Policy. For CSCI 101&102 lab/homework assignments (not Studio assignments), here are a few items to be aware:

1. You are encouraged to discuss (NOT copy) lab assignments with other students in the class.
2. If you discuss an assignment with anyone (including a 101/102 Team member), you must list their names in your submitted assignment AND provide a brief summary of the discussion.
3. You are not allowed to give code you have developed to another student NOR copy code created by someone else.
4. You are not allowed to show another student your working code.
5. You are ONLY allowed to view another student's code for the purpose of offering debugging assistance.
6. You are NOT allowed to post or view 101 (nor 102) assignments on an open Q&A forum (e.g., Chegg). All 101/102 assignments are copyrighted, so posting an assignment (or a piece of an assignment) is violating copyright law. Also, viewing solutions to the posted copyrighted problems is participating in academic misconduct. All Q&A forums are monitored and any 101/102 post will be investigated.
7. Your discussion is subject to the empty hands policy, which means you leave the discussion without any record [electronic, mechanical or otherwise] of the discussion.
8. Any material from any outside source, such as books, projects, and in particular, from the Web, should be properly referenced in your submitted assignment.
9. If you are aware of students violating this policy, you are encouraged to inform the professor of the course.
10. Violating this policy will be treated as an academic misconduct for all students involved (both the helper and the cheater). See the Student Handbook for details on academic dishonesty.

NOTE: All issues of misconduct are reported to the Dean of Students. Academic misconduct may result in course failure for all students involved (both the helper and the cheater). Cheating on an assignment to get a few points for free is NOT worth the risk!

The complete Academic Integrity Policy can be found in the Mines’ Policy Library.