DATES:
June 23-25
ELIGIBILITY:
Who Can Participate:
- Eligible Individuals: Participants: Individuals at least 18 years or older.
- Teams: Groups of 1-5 Eligible Individuals can participate together.
- Entrants: Both individuals and teams can participate in the Hackathon.
Participation Rules:
- Teams must have a Representative authorized to submit the team's entry.
- An Eligible Individual can participate in multiple teams or enter as an individual.
Who Cannot Participate:
- Organizations are not allowed to participate, nor are any individuals involved with organizing or promoting the Hackathon.
- People or organizations located in countries or territories where US law prohibits participation or receiving prizes are not eligible.
- Judges, their employers, and any individuals or organizations with a conflict of interest cannot participate.
- Immediate family and household members of ineligible individuals or organizations are also not eligible to participate.
Note: Immediate family members include spouses, children, parents, and siblings.
SUBMISSION REQUIREMENTS
1. All submissions must be made by 3:00pm, June 25th, or the alternative deadline published on the day.
2. All submissions must make use of at least one of the partner APIs.
3. All submissions must fit into one of the challenge categories.
4. All submissions and demos must include a working (coded) prototype (mobile or software application, website, etc.). No slideware permitted.
5. All submissions must be demoed live to the judge panel between 4pm and 5pm on June 11th.
6. All submissions must keep to the 3-minute time parameters outlined for demos.
7. Submissions may not contain any copyrighted elements other than elements owned by the entrant.
JUDGING CRITERIA
User Experience / User Interface
Assessing the ease of use and aesthetics of your project. Does it effectively accomplish its intended purpose in a user-friendly and approachable manner?
Originality / Uniqueness
Determining whether your project is a novel idea or if similar ones have been executed before.
Technicality
Evaluating the complexity of the problem you are solving, including the number of components involved. Did you develop it in an efficient manner, or did you add too many unnecessary components? Is your code well-structured and clean?
Practicality
Assessing the practicality and potential appeal of your project to its intended audience. Does it have business value and potential for growth and mass adoption?
Moonshot Potential
Beyond practical considerations, we also welcome radical and visionary projects that have the potential to revolutionize industries or create entirely new ones. Is your project a "moonshot" idea that could lead to a billion-dollar business or a breakthrough in your field? We encourage you to think big and propose bold, daring solutions.
Wow Factor
Additional points will be given for any exceptional aspects of your project not covered by the above criteria.
Judging: 1/10 (10 being highest)
CODE OF CONDUCT:
The purpose of this code of conduct is to create a safe and welcoming environment for all participants attending the in-person hackathon event. All participants are expected to abide by this code of conduct.
Respectful Behavior
All participants must treat each other with respect and consideration. Harassment, discrimination, or any form of abusive behavior towards another participant will not be tolerated. This includes verbal, physical, or written attacks, or any behavior that makes another participant feel unsafe or uncomfortable.
Inclusive Language
All participants must use inclusive language and avoid any language that is offensive or exclusionary. This includes, but is not limited to, language that is discriminatory towards race, gender, sexuality, or disability.
No Alcohol or Drug Use
No alcohol or drugs are allowed on the premises of the in-person hackathon. Participants who are under the influence of drugs or alcohol will not be allowed to participate.
Privacy and Security
Participants are expected to respect each other’s privacy and security. This includes not sharing personal information without the consent of the individual and not hacking or accessing data that is not intended for public consumption.
Safety
Participants are expected to abide by all safety rules and regulations outlined by the in-person hackathon organizers. Any behavior that puts oneself or others in danger will not be tolerated.
Reporting
If any participant witnesses or experiences any behavior that violates this code of conduct, they should report it immediately to the in-person hackathon organizers. The organizers will take appropriate action to address the issue and ensure the safety of all participants.
Consequences for Violations
Any participant who violates this code of conduct will be subject to immediate removal from the in-person hackathon event. The organizers reserve the right to determine the appropriate consequences for any violations.
Acknowledgment and Agreement
All participants attending the in-person hackathon event are expected to read and abide by this code of conduct. By attending the event, participants acknowledge and agree to follow this code of conduct.