• Teams must have a maximum of four members.
    • Participants may work alone, but they will be judged on the same guidelines as a team will be.
  • All members of a team must be registered participants.
    • All team members must currently be enrolled in an university, college, high school or recently graduated (within 1 year).
  • All team members must sign in and be present at the event.
    • Working off-site is discouraged, but allowed.
  • Code for a team’s project should only be written by team members.
    • Getting advice from other teams, volunteers, sponsors, or mentors is not only allowed, but encouraged!
    • However, your project must ultimately be built by your efforts. In other words, do not let others make your project.
  • All code written for this project MUST be written at hackKU.
    • It is entirely against the spirit of this competition to work on a project already in progress. If any project is found to have been started before the hackathon, that project would be disqualified. (But still judged)
    • You may choose to expand or add features to an existing product. If you choose to do so, be very clear about what parts you created, and what was already there.
    • If you do so, properly utilize said open-source items by following the terms of their licenses.
    • Submissions will be done through Devpost. Once your code is submitted and the hackathon ends, you cannot make any changes.
  • You may use open-source frameworks, libraries, and code.
  • Hacking must stop when the hackathon is over. 
    • Submissions will be done through Devpost. Once your code is submitted and the hackathon ends, you cannot make any changes.
  • For judging purposes, your code must be publically available on Github.
    • We will use it to verify all the rules and deadlines of the competition were followed. All winning teams may be subject to a code review.
  • Follow the MLH Code of Conduct.
  • All submissions remain the intellectual property of the individuals or teams that made them.