2024 Rules
Add Headings and they will appear in your table of contents.
Below are the rules that *every hacker* must follow while participating in HenHacks.
*Many of these rules pertain to hacking and hack submissions- failure to abide by any of these rules will disqualify you from the hackathon. If you have any questions, please reach out to us at henhacksud@gmail.com.
Please be sure to read and make sure you understand all of these rules to ensure everyone has a great time throughout the weekend!
Happy Hacking,
-- The HenHacks Team
HenHacks has a strict zero tolerance policy on racism, sexism, homophobia, abuse, or anything inappropriate. If you would like to report any misconduct, please do so here:
Hackers must follow the MLH Code of Conduct.
There is a maximum team size of 4, but no minimum team size.
Teams should be made up exclusively of students who are not organizers, during-event volunteers, judges, sponsors, or in any other privileged position at the event.
All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine, though.
Teams can, of course, gain advice and support from organizers, volunteers, sponsors, and others.
All work on a project should be done at the hackathon **(do not start hacking before 12pm on Saturday, 3/2 or after 12pm on Sunday, 3/3)**
Teams can use an idea they had before the event.
Teams can work on an idea that they have worked on before (as long as they do not re-use code).
Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they are allowed to do so and will be judged on the quality of their hack.
Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.
Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, or other unsporting behavior.