--- title: "Jam 00 - Exercise 6 - Honor Code and Final Submission" tags: - 4 🥳 done - jam00 - setup - honor-code - submission --- <!-- markdownlint-disable line-length single-h1 no-inline-html --> <!-- markdownlint-configure-file { "ul-indent": { "indent": 4 }, "link-fragments": {"ignore_case": true} } --> # Exercise 6 - Honor Code and Final Submission {%hackmd dJZ5TulxSDKme-3fSY4Lbw %} ## Overview - Exercise 6 Academic integrity is fundamental to your education and professional development. In this final exercise, you'll: - Review the course honor code - Make a personal commitment to academic integrity - Complete your final submission :::danger 🚨 **Critical Requirement** The honor code is not just a formality - it's a binding agreement about academic integrity. If you have any concerns about these requirements, speak with your professor immediately about withdrawing from the course. ::: ## Required Steps - Honor Code 1. **Review the Honor Code** Add this section to your `README.md`: ```markdown! ## Honor Code for CSCI 205 All of my work in CSCI 205 is completed in Java. It represents my own work, and nobody else. I am committed to upholding the integrity of learning for myself, and for everyone around me. I understand that when I cheat, it misrepresents what I've actually learned. When I cheat, it takes credit for the work that other people have completed. It misrepresents what I actually know to prospective employers. I acknowledge that cheating will have negative consequences on not only my own learning, but it also minimizes the value of the honest work of others who took the same course. **Therefore, I will not cheat.** Work in this course can present complex, challenging problems at times. I am encouraged to research solutions and hold discussions with my classmates. However, all work that culminated from ideas I obtained elsewhere is clearly cited in my code. URLs of web sites that gave me ideas are acceptable citations, but copying code from those sites is strictly forbidden. Conversations with other classmates are acceptable, and even encouraged when presented with challenging problems. However, code exchange is also strictly forbidden. Some jams are designed to be collaborative with another classmate, and are clearly indicated in the instructions for the jam. In these cases, those people on my team are clearly indicated in every source file, but each member of the team commits the collaborative work in their jams. Reiterating, all code I have written is my own, and only my own. I understand that all examples of plagiarism of any kind will be sent to the Board of Review, risking my failure of the course, a permanent mark on my Bucknell record, and possible expulsion from the university. ``` 2. **Commit Your Changes** - Stage and commit your updated README.md - Use the commit message: "jam00, Exercise 6, complete" - Push to GitLab :::info 🔑 **Understanding Collaboration** This course encourages: - Discussing problems with classmates - Researching solutions online - Learning from examples But strictly forbids: - Copying code from any source (without proper citation) - Sharing code between students - Submitting work that isn't your own When in doubt, ask your professor! ::: ## Final Submission Steps 1. **Verify Your Work** Run `git status` to ensure: - All (unhidden) files are committed - Working directory is clean - Nothing left to push (besides maybe your idea config file - we'll talk about that in lab01) - Should look like this: ![clean git](https://hackmd.io/_uploads/BkAtqmiPJe.png) - Or this ![idea only git](https://hackmd.io/_uploads/r15m7Ox_1g.png) - If it doesn't, you need to figure out what you need to do to get it to this state. 2. **Check GitLab** Log into gitlab.bucknell.edu and verify that: - Your `README.md` is complete with honor code - Your answers.txt contains all responses - All files appear in the correct locations - If the files are not in the correct locations, you need to figure out what you need to do to get them there. :::danger 🚨 **Critical Reminder** Once more for good measure: We can only grade what's on GitLab! If you don't see it there, we can't see it either. Double-check that everything is pushed before the deadline. ::: > 🔍 **Final Project Structure** > > Your repository should now contain: > > ```text > csci205_jams/ > ├── README.md # With all sections including honor code > ├── .gitignore # Properly configured > └── src/ > ├── main/ > │ ├── java/ > │ │ └── jam00/ > │ │ └── answers.txt # with all your answers > │ └── resources/ > └── test/ > ├── java/ > └── resources/ > ``` :::info 🔧 **About Empty Folders** Git only tracks files, not folders! This means: - Empty folders won't appear on GitLab - The `resources/`, `test/java/`, and `test/resources/` folders won't show up yet - These folders will appear automatically when you add files to them in future jams - This is normal and expected behavior Don't worry if you don't see all the folders on GitLab - as long as you have your README.md, .gitignore, and answers.txt in the correct locations, you're good to go! ::: Congratulations! You've completed your first jam and set up your development environment for the semester. In the next jam, we'll start writing actual Java code!