-
Teams should be no larger than 4 to 5 people.
-
Teams should be only be composed of participants who are not organizers, judges, sponsors, or anybody else in a privileged position at the hackathon.
-
All team members should be present at the event for the awards ceremony. Participants may leave the venue for some time to hack elsewhere.
-
Teams can get support from organizers, volunteers, sponsors, and others.
-
All work on a project should be done at the hackathon. Any ideas that were had before the hackathon may be used.
-
Teams may work on ideas that have already been done. All projects will be judged on the quality of the hack, not on the originality of the hack.
-
Teams may work on an idea they have worked on before, so long as code/assets are not reused.
-
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.
-
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. You must clearly state the new feature.
-
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.
-
Projects that violate the Code of Conduct are 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, breaking the Code of Conduct, or any other unsporting behaviour.