- All members of a team should be present at the event. Leaving the venue for some time to hack elsewhere is fine (One team member should be present at the event at all times).
- All work on a project should be done at the hackathon.
- The teams must provide their Username and the GitHub/BitBucket repository name to the Hackathon staff.
- It is mandatory to add ‘InfoUnifynd (info@unifynd.com)’ as a collaborator along with the Username and Repo name.
- Teams can use ideas conceived before the event.
- Teams can work on ideas that have already been done. If somebody works on a common idea they will be allowed to do so and will be judged on the quality of their hack.
- 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 not allowed.
- Teams are welcome to approach organizers, volunteers, sponsors for advice.
- Adding new features to existing projects is allowed. Judges will only consider new functionality added during the hackathon in determining the winners.
- Teams must stop hacking once the time is up after which they will not be allowed to debug and make any changes to their programs.
- 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 behavior.
- Projects that violate the Code of Conduct are not allowed.