hackathon rules

everything you need to know to compete fairly and have an amazing time.

1. team formation

  • • teams must have 2-4 members maximum
  • • all team members must be high school students
  • • teams can be formed before or during the event
  • • solo participants are welcome and will be helped to find teammates
  • • team changes are allowed only within the first 2 hours of hacking

2. project timeline

  • • coding must begin after the official kickoff ceremony
  • • all development must stop when time is called
  • • late submissions will not be accepted under any circumstances
  • • time extensions are only granted for technical difficulties verified by organizers

3. project requirements

  • • projects must be built from scratch during the hackathon
  • • you may use existing libraries, frameworks, and APIs
  • • pre-written code or templates are not allowed
  • • all code must be publicly accessible (GitHub recommended)
  • • projects must include a demo video (max 3 minutes)
  • • a brief presentation slide deck is required

4. judging criteria

  • innovation: creativity and originality of the idea
  • execution: technical implementation and functionality
  • design: user experience and visual appeal
  • impact: potential to solve real-world problems
  • presentation: clarity and effectiveness of the demo

5. intellectual property

you retain full ownership of your intellectual property. by participating, you grant east bay hackers permission to showcase your project in event materials and future promotional content. we encourage open-source projects but ofc it's entirely your choice.

6. prohibited activities

  • • attempting to hack or disrupt other teams' projects
  • • using work completed before the hackathon starts
  • • creating harmful, offensive, or inappropriate content
  • • violating any laws or platform terms of service
  • • sharing misleading information about your project's development

7. resources and support

mentors will be available throughout the event to provide technical guidance and feedback. hardware, development tools, and API credits will be provided where possible. food, drinks, and a comfortable workspace are included. ask organizers if you need anything!

8. disqualification

teams may be disqualified for violating any of these rules, the code of conduct, or engaging in unsportsmanlike behavior. decisions made by organizers and judges are final. we want everyone to have fun and compete fairly.

questions?

if you're unsure about any rule or need clarification, don't hesitate to ask an organizer. we're here to help you succeed and want to ensure fair competition for everyone.