Hackathon Rules

These rules are subject to change. The final rules will be given out on the day of the event.

  • All design elements, code, hardware builds, etc. for your project must be created during the event. Third party tools and frameworks are allowed as well as your normal tooling (Gulp, Yeoman, Composer, NPM, Bower, etc.). While you may not begin coding in advance, you can plan and discuss with your team in advance. Written documents and design sketches are allowed.  You may also incorporate pre-existing material that is freely available to the public into your project, such as public domain images, Creative Commons music, open-source libraries, existing APIs and platforms, and the like.
  • Projects must involve writing significant software, though hardware may be incorporated.  Note: projects that incorporate peripheral hardware that may need additional space (such as large robotic devices, drones, etc.) must be pre-approved by the Troy Hack Organizing Committee. For questions or approval, contact info.troyhack@gmail.com.
  • Teams must be comprised of 1-4 people.
  • Only 5 of the competing teams will present their projects in the final round of judging at the end of the event. Note: we recommend that, prior to the beginning of preliminary judging, teams prepare a short (~2 minute) project pitch to be given to a subset of the judges.
  • Teams that make it to the final round will be given up to three minutes to present their finished project to a panel of judges.
  • The prizes not specified otherwise will be awarded solely based on the decision of the judging panel.  
  • At least one team member must be physically present during sign-in, and one must be conscious and present to present the project to the judges during their assigned presentation time. A team of three or four may have one remote member who never works from the hackathon location. The other members must spend the majority of their design/coding time at the hackathon location.
  • Any intellectual property developed during the hackathon will belong to the team that developed it. We expect that each team will have an agreement between themselves regarding the IP, but this is not required.

Hackathon Code of Conduct

Harassment and abuse are never tolerated. If you are in a situation that makes you uncomfortable at Troyhack, if the event itself is creating an unsafe or inappropriate environment, or if interacting with an event volunteer or organizer makes you uncomfortable, please report it using the procedures included in this document.

We stands for inclusivity. We believe that every single person has the right to hack in a safe and welcoming environment.

Harassment includes but is not limited to offensive verbal or written comments related to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, social class, economic status, veteran status, sexual images, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. If what you’re doing is making someone feel

uncomfortable, that counts as harassment and is enough reason to stop doing it.

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

Sponsors, judges, mentors, volunteers, organizers, and anyone else at the event are also subject to the anti-harassment policy. In particular, attendees should not use sexualised images, activities, or other material both in their hacks and during the event. Booth organizers (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment.

If a participant engages in harassing behavior, Troyhack may take any action it deems appropriate, including warning the offender or expulsion from the event with no eligibility for reimbursement or

refund of any type.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the organizers using the reporting procedures defined below.

We will be happy to help participants contact campus security or local law enforcement, provide

escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event. We value your attendance.


We expect participants to follow these rules at all hackathon venues, online interactions in relation to the event, and at hackathon-related social events.

Reporting Procedures

If you feel uncomfortable or think there may be a potential violation of the code of conduct, please report it immediately using one of the following methods. All reporters have the right to remain anonymous.

By sending information to the general reporting line, your report will go to any or all of the

representatives listed below.

• David Ajao - +1 (334) 722-0616, dajao@troy.edu

• Alex Vakhno - +1 (334) 372-3230, ovakno@troy.edu

• Christina Atencio – +1 (205) 706-1666, catencio@troy.edu

Troyhack reserves the right to revise, make exceptions to, or otherwise amend these policies in whole or in part. If you have any questions regarding these policies, please contact csclub@troy.edu.

This guide was last updated on: January 9, 2020