To ensure fair competition among all Hackathon participants, each challenge has one or two special criteria (ie. special ingredients) that will not be released until the actual date and time of the event. Therefore, we recommend not attempting to build anything tangible until the start of the event.

Once registered, you and/or your team will have access to our exclusive online Zulip forum where you can recruit other team members and discuss the hackathon with fellow students and participants. Here we encourage you to begin brainstorming ideas and creating wireframes/mockups.

The three main event challenges are posted below. Additional Sponsor challenges will be posted no later than March 1st, 2019.

Any software programming language can be used for the event.

You are permitted to use publicly developed and openly licensed API’s and SDKs for your project.

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 be freely available.

Any software development tools, game engine, or IDE 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 teams, the team should choose an alternate tool which is available to all developer teams.

You will only be able to use a pre-publicly released 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, 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 license may be used.

A team can submit only one entry for the hackathon, and be considered for one prize. 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 can use multiple licenses in the application. For example, The public code used is subjected to the Apache license agreement whereas the code written by the team for the application is subjected to the MIT license agreement.

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