The jury result is on paper
The jury watches each team present live and scores on paper. The application holds no jury score and no jury ranking. The community result is never the jury result, and nothing combines the two.Your team’s three decks
Each team has three links of its own, each a Slideless share link to a deck the team made from the template the organizers published in the organization’s Slideless workspace:- the demo deck (the
hackathon-deck-demoskill): what you built shown working, in one to three episodes of real screenshots of your running app, so the jury can follow it alone; - the jury presentation (the
hackathon-deck-pitchskill): the pitch you give on stage, three to five minutes; - the community presentation (the
hackathon-deck-voteskill): your elevator pitch with the gaps filled, the deck the other participants read on the Vote page and rank. A team is a vote candidate once it is set.
The community vote
The Vote section is off unless the organizers turn it on. When it is on, participants rank the other teams on the Vote page, andhackathon community status prints the same.
Who votes, who is ranked
Before the vote opens, an organizer locks who takes part: the candidate teams, and the voters, every participant on a team. The lock is a snapshot: a later change of the roster does not change who votes or who is ranked.The window
A ballot is accepted from the vote’s opening to its closing, on the server’s clock. A ballot that reaches the server one instant after the close is refused.The ballot
- One ballot per participant. You rank every other candidate, best first. Your own team is listed apart and cannot be ranked.
- Draft and submit. Save draft keeps a ranking in progress, complete or not. Submit ballot needs every other team exactly once. A submission replaces the previous one; only the submitted ranking counts.
- Edits until the close. You can submit again until the vote closes; the last submission is the one that counts.
- Privacy. You see your own ballot and nobody else’s. There is no live leaderboard.
hackathon community ballot show, hackathon community ballot save --ranking <ids> and hackathon community ballot submit --ranking <ids>, the project ids best first.
The scoring rule
For a submitted ballot that ranksm teams, the team at rank r (1 is the best) gets:
A bigger team casts more ballots. Every participant has one ballot, so a team of three casts three
ballots and a solo team one. None of them can rank their own team.