In addition, the following rules must be abided by at all times:

  1. Each team can have a max of 4 people. All of the members of a team must have applied to NewHacks through and received an acceptance. Registering through Devpost alone does not qualify as an acceptance.   
  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 present at the event, for the opening and closing ceremony. Leaving the venue for some time to hack elsewhere is fine.
  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. We will verify it by your git repository
  6. Teams can use an idea (but can not use materials-code from previous hackathons) 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).
  7. Teams may not submit code that they submit at another hackathon or for a project. 
  8. 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.
  9. 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.
  10. Teams must stop hacking once the time is up. Projects will be spun up from the submitted git repositories during the presentation.
  11. Projects that violate the Code of Conduct are not allowed.
  12. 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.