1. You must treat all team members, competitors, judges, coaches, volunteers, etc, with respect and courtesy, abiding by the UQ code of conduct.
  2. Hackathon teams will be a maximum of 4 people
  3. All prizes are to be shared between all team members
  4. Teams should be made up exclusively of students or EMCRs who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
  5. All team members should be present at the event. Leaving the venue for some time to hack elsewhere is fine.
  6. Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
  7. All work on a project should be done during the hackathon.
  8. Teams can use an idea they had before the event.
  9. 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.
  10. 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.
  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. Teams can be disqualified from the competition at the organizers’ discretion. Reasons might include but are not limited to breaking the Competition Rules, behaving in a way that violates the UQ code of conduct or other unsporting behaviour.