Application and Acceptance                                                             

  • All applicants should submit their application through the hackathon website. No exceptions will be made.
  • Upon applying, an auto-generated email will be sent letting you know that you have applied for the hackathon
  • The hackathon committee will review applications as they are submitted before making a decision to accept/deny applications
  • Upon acceptance an email will be sent to you stating your application has been accepted.
  • Only accepted applicants that have registered on Eventbrite will be able to participate in the hackathon.
  • Showing up on the day of the hackathon will not guarantee you a spot! If slots open up due to cancellations, a waiting list will be initiated and spots will be given in preference to people in the waiting list
 

Eligibility  

  • Attendees from all backgrounds, genders and geographies are welcome.
  • There is no age restriction to attend the hackathon. Please note that alcohol may be served during the event. In case you are under 21, you may have to sign a waiver form to make sure you feel comfortable in the environment.
  • In case you are under 18, you need a signed waiver from the parent/legal guardian authorizing you to attend the hackathon. The waiver form is available to download from the hackathon website.   
  • Committee members are not eligible to participate in the hackathon. They may however assist teams in the coding/development phase.      
  • There is no country restriction but you must be eligible to receive prizes (in case you win) and be legal to pay taxes on prize winnings.     
  • Employees of prize sponsors are not eligible to participate in the hackathon.
 

Team forming                                                 

  • Teams can consist of one member to a maximum of five members. Exceptions can be made for teams to have more than five members on a case by case basis. Contact the hackathon committee in case you need to have a team more than 5 members.
  • All teams should have at least one designer (unless the team only has one member).
  • Changes to team members are not permitted after 5pm on the 2nd day of the hackathon (Saturday). Exceptions can be made on a case by case basis as decided by the rules committee.
  • All teams should have a team name, and be registered with DEVPOST here.
 

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 October 7th - 10pm. However, we encourage you to brainstorm ideas and create wireframes/mockups.
  • Any software development tools, game engine, IDE, programming language can be used for the event. However if in a team certain members have purchased tools and they cannot be transferred to other team members then the team should decide on one that can be used by all team members who do development.
  • 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. During final submission, mention of any publicly used API’s is mandatory with a “percentage” usage for your application. For example: Team “A” used the Facebook API for 85% of their application.
  • You will only be able to use a pre-public release product for use in developing your creation if you bring at least 1 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. 
  • 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 in more than one team at the event.
  • All projects submitted may be subject to a code-review and if selected in the short-list of applications then a mandatory code/asset review to determine whether the work was originated at the hackathon or before.
  • Any intellectual property developed during and within the scope of the hackathon must be registered in the public domain, meaning that the investors will retain no residual rights to the intellectual property and the intellectual property will be available for public use.
 

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 is not appropriate at 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.

By participating in this hackathon,

You acknowledge that we may share your information with our top level sponsors so that they may contact you about exciting recruitment and product announcements. If you do not wish to receive these messages, you can unsubscribe from the sponsor contact emails at any time.