1. You can have up to 4 members on the team.
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. 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.
6. Teams can use an idea they had before the event.
7. Teams can work on an idea that they have worked on before (as long as they do not re-use code).
8. Teams can use libraries, frameworks, or open-source code in their projects. You must clearly distinquish your contributions in the submission and during live judging.
9. Adding new features to existing projects is not allowed.
10. 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.
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.