MUST be registered and accepted to attend based on the TOHacks application portal. Any registrations done on DevPost and not on our portal will be ineligible to participate and win prizes. The following have been modified from Standard Hackathon Rules, provided by MLH:

  1. There is a maximum team size of 4. 
  2. Teams should be made up exclusively of students (or recent graduates within one year of having graduated) who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
  3. All team members should be e-present at the event.
  4. Teams can, of course, gain advice and support from organizers, volunteers, sponsors, and others.
  5. All work on a project should be done at the hackathon.
  6. Teams can use an idea they had before the event.
  7. 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 should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
  8. Teams can work on an idea that they have worked on before (as long as they do not re-use code or other project materials).
  9. 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.
  10. Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
  11. 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.
  12. Projects that violate the Code of Conduct are not allowed.
  13. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour
  14. You are strongly encouraged to record a 3-minute demo of what you have built. Pitches or presentations are discouraged.
  15. You may submit your project to other hackathons during the same weekend as this event is virtual. 
  16. Any cheating or violations can be reported by messaging Andy Tran, or Shwetha Sivakumar (Co-Founders, TOHacks), and will be dealt with in accordance with the MLH Cheating Response Procedure.
  17. As part of the MLH's Disciplinary Action Policy:
    1. To ensure that Major League Hacking (MLH) sanctioned events are a safe and welcoming environment, MLH and the local event organizers reserve the right to refuse admittance to any individual to an event. This document outlines common reasons that an individual could be refused entrance to an event, procedure for notifying the individuals and organizers of bans or suspensions, and outlines the appeals process.

    2. In the event of a violation of sanctioning guidelines, Code of Conduct, or other official Major League Hacking regulation or policy, actions will be taken to rectify the issue. These actions will typically include, in order of severity, the following:

    3. Written or Verbal Warning outlining the violation and how the participant can take action to resolve the issue. Temporary Suspension from the current or future MLH season(s). Permanent Ban from all MLH activities.

  18. Remember: The competition is just a part of the hackathon. To make the most out of the event, try something new, teach other people, and make new friends!