Most rules are from previous hackathons hosted at UVic and the MLH hackathon base rules

OK THE RULES:

  1. Team sizes can range from 1-5 if the teams hack is to be entered into prize pools.

    1. Possibility of change depending on sponsor related prize pools.

  2. All team members should check in during the event.

    1. checking in would require a commit, push, review, slack message... ect.

  3. Teams can gain advice and support from organizers, volunteers, sponsors, others, online material, and physical material.

    1. Please be sure to cite in some capacity.

      1. 1. example: Readme or code comments.

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

    1. For certain types of projects some prep is necessary, though do project work during hours of hackathon.
      1. example: Hardware ordering

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

  6. Teams can work on idea that have already been done

    1. Hacks don't 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.

  7. Teams can work on an idea that they have worked on before (as long as they do not re-use code).

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

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

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

    1. This time is limited to approximately 10 minutes

  11. Any behaviour that is deemed detrimental or not in the spirit of the hackathon will result in a disqualification at the discretion of organizers'.

  12. Projects that violate the MLH Code of Conduct are not allowed.

    1. https://static.mlh.io/docs/mlh-code-of-conduct.pdf

  13. Teams and or projects 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.