1- minimum team size is 2 and maximum is 5
2-All team members should be present at the event.
3-Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
4-Teams can work on an idea that they have worked on before (as long as they do not re-use code).
5-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.
6-Teams must stop hacking once the time is up.
7-If during demoing your hack you find a bug that breaks your application , you are allowed to fix it only it's a few lines of code. Making large changes or adding new features is not allowed.
8-Projects that violate the Code of Conduct are not allowed.
9-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.Demos Rules:
1-After hacking finishes, teams will show their projects each other and to the judges.
2-You are strongly encouraged to present a demo of what you have built. Pitches or presentations are discouraged.
3-You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. 10 - The responsibility of the components and the materials required for developing the prototype during the Hackathon lies solely on the participating teams. Anything that are required to be provided from RevHack must be conveyed in prior.