OCCHACKS CODE OF CONDUCT
At the end of the day, OCCHacks hopes to encourage collaborative and creative spirits. In the hopes to maintain a safe and positive space, your participation at OCCHacks includes your acknowledgement and acceptance of the following.
1. Elligibility Only college-level students aged 18 and above are allowed to participate. We want to keep a more level playing field and run within the legal limits.
2. Inclusivity Any form of hatred (e.g. bigotry, racism, sexism, transphobia, etc.) is intolerable and punitive action will be taken without exception. OCCHacks strives to provide a safe and comfortable environment to all students. All forms of harassment and discrimination will be handled with the same gravity. If you feel unsafe or notice that someone else is uncomfortable, contact a staff member or hackathon organizer immediately.
3. Behavior Treat everyone with respect, courtesy, and professionalism. Any breaking of respectful conduct, including, but not limited to, sabotage, explicit content, verbal insults, and invasion of personal space, will be handled at the discretion of hackathon staff.
4. Plagiarism Projects that are not credited properly and/or wrongfully used and presented will be disqualified. All work can only be done by team members and tools involved.
5. Punitive Action Punitive actions may include, but is not limited to, disqualification, ejection, and permanent ban from future OCC hackathons. These will be used at the discretion of hackathon staff.
IMPORTANT RULES TO NOTE
Please be aware that this list is tentative and not exhaustive as it contains subtle intracacies that are crucial in understanding the bounds and logistics of the competition. Infractures may lead to disqualification.
1. Projects may be made in teams of up to four.
2. Projects must be strictly created and finished during the alloted time exceptions (Oct. 10, 9:15 AM to Oct. 11, 3:30 PM).
3. Projects can compete in only one track. Be sure to decide which early.
4. OCCHacks is an in-person event, so attendees are required to be physically present to check into the event at the start of the hackathon. Attendees are allowed to leave after the event has officially started but must be physically present during judgment.
5. This event cannot be hosted on location overnight, so attendees will be asked to leave when the building closes. Projects may continue to be worked on overnight at home within the time.
6. AI usage and vibe-coding is permitted, but be aware that creativity and originality is still a critical factor in the success of your project.
