The Spirit

Remember that hackathons are like marathons. Some people go to compete but most people take part to better themselves and have fun. Whatever the reason is you're at a hackathon, make sure you're upholding the by collaborating with other teams, helping beginners, and having fun.

The Rules

  1. Team of 5 or individuals can apply. For individuals you can form your team in the premise or we can help you to form a team.
  2. All team members should be present at the event.
  3. Teams can gain advice and support from our clinics staff during hacking
  4. All work on a project should be done at the hackathon venue.
  5. Teams can use an idea they had before the event.
  6. Teams can work on an idea that they have worked on before (as long as they do not re-use code).
  7. 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.
  8. 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.
  9. 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.
  10. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, or other unsporting behaviour.

The Presentation

After hacking finishes, teams will have one hour to prepare on their presentation and then show their projects to each other and to the judges for 15 mins.

You are strongly encouraged to present a demo of what you have built during the presentation. Your team will be judged on both the quality of your pitch and the quality of your idea.

You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It's okay if you didn't finish your hack—that happens all the time! Completion is only one part of the judging criteria, so you might still do well. Also, demoing is not just about the competition. It's a chance to share with others what you learned and what you tried to build—that's what hacking's all about.