1. You must be signed in via Discord before sign-ins close on Saturday, April 9th at 12 pm EST to be eligible. (No exceptions will be made!)

  2. Your project must be submitted to Devpost and must have a Github repository where judges can view your project's code and other project assets.

  3. The maximum team size is 4. This ensures that we have enough prizes for everyone on your team.

  4. Teams should be made up exclusively of students (or recent graduates within one year of having graduated). Professionals are allowed to participate, but will not be eligible for prizes.

  5. All team members should be present at the event.

  6. Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.

  7. All work on a project should be done at the hackathon.

  8. Projects completed during this CatHacks may be submitted to other hackathons. However, no work may be completed before the start of CatHacks. (Ex. Hacking begins on Friday, April 8th at 7:00 pm EST. Other hackathons start on Saturday. You may use your work started at CatHacks on those hackathons that start after CatHacks, assuming the other hackathons allow it.)

  9. Teams can use an idea they had before the event.

  10. 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. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.

  11. Teams can work on an idea that they have worked on before (as long as they do not re-use code). Prior work on a project must be identified and described during judging. Failure to do so will result in disqualification.

  12. 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.

  13. 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.

  14. 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.

  15. Projects that violate the Code of Conduct(http://static.mlh.io/docs/mlh-code-of-conduct.pdf) are not allowed.

  16. 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(http://static.mlh.io/docs/mlh-code-of-conduct.pdf), or other unsporting behavior