Hackathon Rules


  • General Conditions / Indemnification

  • Eligibility

  • Team Forming

  • Project Development

  • Attendee Code of Conduct

  • Ownership & Promotion

  • Judging Evaluation Criteria


General Conditions / Indemnification

  • By entering, participants warrant and represent that their team is the sole creator of the Submission and that they have obtained permission from all persons or copyright or trademark owners whose likeness, work or mark are depicted in Submission and all permission necessary for THE HACK  to publish or use their Submission in any media worldwide and agree to confirm any of the foregoing in writing. Further, by participating in THE HACK and/or by accepting any prize, contestants agree that THE HACK and the event organizers shall not be liable for any and all actions, claims, including any third party claims, injury, loss or damage arising in any manner, directly or indirectly, arising from or relating to THE HACK, including entry and participation, or the acceptance, possession, use or misuse of any prize. By participating in or accepting any prize, participants agree to fully indemnify event organizers, sponsors and THE HACK from any and all such claims by third parties without limitation.

  • ** Event organizers may prohibit certain contestants or teams from participating in THE HACK or winning a prize if, in its sole discretion, it determines that a contestant or team has attempted to undermine the legitimate operation of THE HACK by cheating, hacking, deception, or any other unfair playing practices of intending to annoy, abuse, threaten or harass any other participants, mentors or the THE HACK team.


Eligibility  

  • Attendees from all backgrounds, genders and geographies are welcome.

  • There is no age restriction to attend the hackathon. In case you are under 18, you need a signed waiver from the parent/legal guardian authorizing you to attend the hackathon. Download the waiver here.    

  • Committee members are not eligible to participate in the hackathon. They may, however,, assist teams  as mentors during the coding/development phase.       

  • There is no country restriction but you must be eligible to receive prizes (in case you win) and you are responsible for paying any taxes on the prize winnings.


Team forming        

  • Teams can consist of one member to a maximum of five members.*

  • All teams should have at least one designer (unless the team only has one member).

  • No team shall have more than one team member employed by the same company.*

  • Participants who participated on the same team during the 2016 or 2017 Reality Virtually Hackathon at the MIT Media Lab are not permitted to be team members on the same team competing in this year's Hackathon.Changes to team members are not permitted after March 13, 2018 at 5:00 PM.*

*Exceptions can be made on a case by case basis. Please contact the hackathon committee if you'd like to discuss a team  exception.


Project Development

  • No development may start before the actual date and time of the event. Any teams that violate this rule will be automatically disqualified. The first line of code should be written on or after March 12th  - 8 pm after the team has registered. However, we encourage you to brainstorm ideas and create wireframes/mockups.

  • Any software development tools, game engine, IDE, a programming language can be used for the event. If a team member uses a purchased tool licensed to him or her and the license is not transferable to other members the team should choose one available to all developer team.

  • To ensure a level field for all contestants, all code must be created only at the hackathon. You are permitted to use publicly developed API’s for your project.

  • You will only be able to use a pre-public release product for use in developing your creation if you bring at least one extra version that can be used by other teams in the Hackathon, and provide any user support needed to teams using the device.

  • Project design/assets can be created prior to the start date of the hackathon. All assets should conform to the Creative Commons License agreement standard, or is freely available and you have permission or license to use it. Proof of permission must be given upon request.  

  • Assets, SDKs, APIs or other tools or components available under a trial licence may be used.

  • A team can submit only one entry for the hackathon. Participation at the hackathon is subjected on a “per-team” basis meaning you are not allowed to be on more than one team at the event.

  • Any intellectual property developed during and within the scope of the hackathon must be open source and licensed under one of the licenses referenced in https://opensource.org/licenses.

  • The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. Also, public code used inside your application should also list the licenses the code is subjected to.  

  • A team may not code applications that violate the code of conduct. For example Racially insensitive ideas for an application will automatically be disqualified.


Project Submission

  • All teams should have a team name, and be registered with Devpost.

  • The Devpost team page listing should have the following:

    • The team lead must list a mobile phone number on the teams DevPost page

    • Their location, floor, and room

    • The platform

    • The development tools used to build the project

    • SDKs used in the project

    • APIs used in the project

    • Any assets used in the project

    • Any libraries used in the project

    • Any components not created at the hackathon

    • A link to a video of a screen capture of the application on Youtube.

  • All projects should be submitted to the hackathon GitHub account (TBA) before judging begins on Wednesday March 14, 2018 at 6:00 PM. Failure to submit will result in disqualification.  

  • All projects submitted will be subject to a code-review.  When the hackathon ends at least one member from each team will meet with the code review team for a brief review of their submission and to confirm that the team’s Devpost page has been correctly updated. Applications will be spot checked by code reviewers. All the projects selected by the judges as finalists will be code reviewed to confirm that the code is original work created at the hackathon.  


Attendee Code of Conduct

Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, previous hackathon attendance or computing experience (or lack of any of the aforementioned). We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery are not appropriate for  any hackathon venue, including hacks, talks, workshops, parties, social media and other online media. Hackathon participants violating these rules may be sanctioned or expelled from the hackathon at the discretion of the hackathon organizers.

Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, or religion, 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. 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).

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 sexualized images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualized clothing/ uniforms/costumes or otherwise, create a sexualized 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 organizers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behavior to local law enforcement.

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


Who will own any IP produced in the Hackathon?

All IP produced during the Hackathon is required to be registered in the public domain with no residual rights to the IP and available for public use. The spirit of the Hackathon is to encourage innovation and collaboration. We want any developments created during the Hackathon to be openly shared with other participants after the event to foster further development for the benefit of the greater good and to be available to the public to spread awareness and appreciation of the creations made during the Hackathon.


What is the judging/evaluation criteria?

  • User experience, Design & Polish: Does the user feel immersed and transported to another reality? How well designed and polished is it?

  • Innovation & Originality of Idea: Does the idea or project show creative thinking? Does it stand out from the crowd? Is your idea unique and original? Are there similar mechanics, methods or experiences already out there?

  • Code & Technical Merit: What is the quality of your code? How often did the team commit? Was there a technical challenge that was overcome?

  • Artwork/Sound Integration: Was the art/sound created at the Hack? Did it add to the overall experience in a novel way?

  • Judges’ Discretion: Was it fun, insightful or impactful on the judges?

  • Relevance to the Prize Category: How does the experience relate to the category it is applied in? Does it capture the essence of that category?

Note: Judges will recuse themselves from judging teams that include a person who works for the same employer as the judge. In such event the scores of the other judges on the panel will be averaged and the average score will be entered as the recused judge’s score.