MRUHacks Schedule

October 13th, Friday

8:30 AM: Doors Open

  • Begin your MRUHacks experience! Check in at the front desk upon arrival.

10:00 AM: Opening Ceremony

  • A warm welcome and insightful words from Showpass Founder & CEO, Lucas McCarthy. Discover the event’s prompt and get inspired!

12:00 PM: Lunch!

  • Come to the Ideas Lounge and grab some Pizza!

1:30 PM: Workshop

  • “How to Ace Your Demo” presented by Ray DePaul from the Institute of Innovation and Entrepreneurship. Gain invaluable insights to enhance your presentation skills.

7:15 PM: Dinner!

  • Come to the Ideas Lounge to grab some food!

8:30 PM: Games!

  • Time to unwind in the Ideas Lounge! Engage in some fun with games like Mario Kart, Jackbox, and more. A great way to relax and rejuvenate!

 

October 14th, Saturday

8:30 AM: Breakfast!

  • Find us in the Ideas Lounge for a Light Breakfast.

11:00 AM: Submission Deadline

  •  It’s time to wrap up your projects and submit them for judgment. May the best team win!

12:00 PM: Lunch!

  • Join us in the Ideas Lounge for the last meal of the hackathon!

1:00 PM: Judging Expo

  •  Showcase your innovation and hard work in front of the esteemed judges. Good luck!

3:00 PM: Closing Ceremonies

  • Join us as we conclude MRUHacks with the announcement of winners and closing remarks.

Eligibility

- Participants must be Mount Royal University Students. 

- Participants must be physically present during the judging expo and closing ceremony to recieve prizes.

- There is no degree requirement. 

Project and Submission Requirements

- Projects should be submitted through Devpost.

- Projects should have code publicly available on GitHub.

- Submissions must be created during the 24 hours of the competition.

- Participants should not make large changes or add new features after the submission deadline has passed.

- Participants are expected to present a demo of what they have built.

Demos

After hacking finishes, teams will show their projects to the judges through a live demo.

Judges will go from table to table evaluating each project science fair style. You will not be asked to demo your project to everyone in attendence.

You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It's okay if you didn't finish your hack—that happens all the time! Completion is only one part of the judging criteria, so you might still do well. Also, demoing is not just about the competition. It's a chance to share with others what you learned and what you tried to build—that's what hacking's all about! In the case that you don't have anything to demo, you can give a presentation about what you tried and what you learned. Hearing what other people learned is interesting and inspiring for other attendees.

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

 

Code of Conduct

Our hackathon is dedicated to providing a safe and comfortable environment and harassment-free experience for everyone, regardless of the following:  
  • gender
  • gender identity and expression
  • age
  • sexual orientation
  • disability
  • physical appearance
  • body size
  • race
  • ethnicity
  • nationality
  • religion
  • political views
  • previous hackathon attendance or lack of
  • computing experience or lack of
  • chosen programming language or tech stack

Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion or political views, sexual images in public spaces, deliberate intimidation, stalking, following, photography or audio/video recording against reasonable consent, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

Participants asked to stop any harassing behavior are expected to comply immediately.

As this is a hackathon, we like to explicitly note that the hacks created at our hackathon are equally subject to the anti-harassment policy.

Sponsors and partners are also subject to the anti-harassment policy. In particular, sponsors should not use sexualised images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of hackathon staff immediately.

Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon. We value your attendance.

If a participant engages in harassing behavior, the hackathon organisers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon, or reporting their behaviour to local law enforcement.

Photography

Photography is encouraged, but other participants must be given a reasonable chance to opt out from being photographed. If they object to the taking of their photograph, comply with their request. It is inappropriate to take photographs in contexts where people have a reasonable expectation of privacy (in bathrooms or where participants are sleeping).

 

We expect participants to follow these rules at hackathon and workshop venues and hackathon-related social events.