⚠ The Hackerpack is a living document, and will continue to be updated as we finalize more information about MRUHacks.

The Topic 🥁

Stay tuned! The topic will be released during the opening ceremony.

📜Rules

  1. All participants agree to uphold the Code of Conduct to keep hackathons safe, welcoming spaces for everyone.
  2. All team members should be actively participating in the event.
  3. Teams are encouraged to gain advice and support from organizers, volunteers, sponsors, and each other.
  4. All work on a project should be during the period of the hackathon.
  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 or other project materials).
  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. Participants must be actively engaged in writing and understanding their code. LLM use is welcome, but blindly relying on generated output (“vibe coding”) without learning or adapting it is against the spirit of the competition.
  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, breaking the Code of Conduct, or other unsporting behaviour

🤝 Code of Conduct

Our hackathon is dedicated to a harassment-free experience for everyone, regardless of: