• Attendees from all backgrounds, genders, and nationalities are welcome. There is no age restriction to attend MIT Reality Hack.

• Hackers who are 17 years old and younger must have their parents/legal guardian fill out a consent form in order to attend.

• Prize winners are responsible for paying any taxes on their prize winnings, if applicable.

Interacting with other hackers before the Hackathon

Do:

• Familiarize yourself with tools, packages, SDKs

• Identify like-minded people in the Discord Server

• Share ideas and discuss hardware and software you’d like to check out in the Discord Server

Don't:

• Create specific project plans, especially in collaboration with potential teammates, or write any code in advance - this is grounds for immediate disqualification.

• Form teams prior to Team Formation on the evening of January 25.

Examples:

• "I'd love to create an AR tool that puts duct tape on all real-world bananas." This is great! (YES)

• "Hey potential teammate, that's a cool idea! I had a similar one with masking tape and oranges! Can't wait to brainstorm with you at the Hack!" (YES)

• "Hey potential teammate, you might be interested to know there's a cool thing out there called Open AR Tool." (YES)

• "Hey potential teammate, I like that idea too. Let's have a call to discuss the project details." (NO)

Team Formation at the Event

• Rules TBD. Stay tuned.

General Rules

• No development may start before the actual date and time of the event’s hacking period, which begins on Day 2 on Friday, January 26. Any teams that violate this rule will be automatically disqualified. Do not begin working on your project before Friday, January 26 at 8 AM.

• Any software development tools, game engine, IDE, and/or programming language can be used for the event.

• Paid Software Assets - You are NOT allowed to purchase paid art/audio assets. Low cost paid developer plug-ins are okay. Assets, SDKs, APIs or other tools or components available under a trial license may be used. If you are not sure if an asset is allowed, go to the information desk to make a rules inquiry or ask on Discord in the #questions-to-organizers channel.

• Paid Design Tools - For paid creation tools such as Adobe Creative and Solid Works, you are allowed to use any platform available to you. We want to enable designers to continue to work in the platform they are most familiar with.

• Use of Unique Hardware - TBD

• Use of Personal Property - You are responsible for the safety and security of your own personal property, including laptops, tablets, mobile phones, and any XR gear you bring. We cannot store or secure personal equipment at the hackathon.

• Any ideas created or discussed at the hackathon are considered to be in the public domain. This means if you have ideas that you might want to patent or copyright, you should not talk about those ideas during the hackathon.

• Source code 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 project adheres to. The public code used inside the project should also list the licenses the code is subjected to.

• A team can use multiple licenses in their project. For example, the public code used could be licensed under the Apache license agreement whereas the code written by the team for their project could be licensed under the MIT license agreement.

• A team may not build projects that violate the Code of Conduct. For example, racially insensitive ideas for a project will automatically be disqualified.