Skip to content

Latest commit

 

History

History
116 lines (80 loc) · 3.99 KB

judging-protocol.md

File metadata and controls

116 lines (80 loc) · 3.99 KB

Judging Protocol & Schedule

Note: This document is tentative. Times are subject to change

Rules

If you are competing for prizes, you must:

  1. Use the JAMstack. You must not build a monolithic app or run a web server.
  2. Max team size: 6 (Recommended team size: 3-5)
  3. Abide by our code of conduct
  4. To win API prizes, you must use their API. You can review them in apis.md

Judging Criteria

Qualifying Pitches

3:00 - 5:00pm, Main Stage
You should be present by the main stage at least 5 minutes before your presentation is scheduled to start.
This time may be adjusted depending on the number of hackers and teams present.

  • 1 minute, hard stop
  • 40 seconds Q + A
  • We recommend practicing your pitch. Cut out any fluff. Format:
    • Attention-grabbing headliner
    • What the problem is that you're solving
    • Why your product is the solution
    • Demo of your product
    • Remember - you have 1 minute! We will stop you at 60 seconds exactly.
  • Arrive to stand in line at least 5 minutes before your scheduled start time. If you are not at the GitHub stage at your designated time, you will be disqualified.
  • Ensure that your demo is ready & working; you will not get another chance.
  • Got presentation slides but no demo? Sure, that's ok. But it's very likely that only working prototypes will advance you to the next round.

Review your team's place in the queue for presentations here: Posted at 2:00pm Sunday in the Discord

We are using the US Navy Observatory Master Clock for time. If you're on a Mac, you should be synced to this, but it's worth verifying to make sure: https://www.time.gov

If you are not present for your scheduled presentation, you will be disqualified from overall prizes/presentations.

The top 6 teams will move on to present on a judging panel, where we will discuss your project on video for around 10 minutes.

Note that the top 6 teams are contending for the overall hackathon winers. API sponsors may opt to select winners outside of this top 6.

The top 6 teams will be present and take questions on video, which will be streamed to the televisions throughout the GitHub office. If you do not wish to be on video, you can opt to not join your team in your presentation.

Top 6 Teams Panel

5:30 - 6:30

Winners will be announced in the Discord channel #announcements around 5:00pm.

Any commits after 6:00pm will disqualify you from overall prizes and presentations

Dinner, Beer, & Wine

6:00

This is your time to stop coding, chill, eat, and watch the top 6 teams show off their projects on video

Top 3 Teams Presentation

7:20, Main Stage

The top three teams will deliver 7-minute presentations on stage

API Awards

7:45, Main Stage

API Sponsors will announce the winners of their prizes

Overall Awards

8:00, Main Stage

The top 3 teams (presenting top 3) will be awarded their prizes.

Mingling

8:10 - 9:00

Feel free to stick around and mingle for an hour or so

A note on time

Once we get into the swing of things, actual times such as the API Awards and Presentations may vary. Please note that time for your Qualifying Pitch will not vary.

Top 3 Presentations: Presentation Guideline

This is a guideline only, feel free to deviate as you wish

The Setup (1 Min)

Introduce:

  • Yourself
  • The Problem
  • The Solution

The Demo (4.5 min)

Your Product

  • Why it solves the problem
  • How it solves the problem
  • Show off your product
  • How you're using specific API's or services

The Tech (1 minute)

  • What technologies did you use to build this?
  • What challenges did you face while building this?
  • How did you overcome those challenges?

The Sign-off

  • Briefly: The problem
  • Briefly: Why your product solves it
  • Who you are and contact info, if desired