JOIN EVENT
Event has ended
  • --
  • --
  • --
Organizers
Dominik Kundel

Event checklist

 
 
 
 

About this event

Description is not updated

Prizes

Prizes are not published
More

Schedule

  • Saturday
  • 15:00 : Reception

    Come and pick up your shirts, find a good spot for hacking, find a team.

    15:30 : Introduction

    Short introductory words about how the hackathon is going to procede, what steps are necessary to participate in the actual competition and which prizes you can win.

    16:00 : HACK!

    Start writing your code! Don't forget to commit regularly to your repository! :)

    18:00 - 20:00 : Servery is open for dinner

    We won't be able to serve you food for dinner so use this slot to rush down and grab a bite in the servery :)

  • Sunday
  • 00:00 : PIZZA Time

    Time to get energy through some fresh pizza!

    01:00 - 04:00 : Games, Games, Games

    In order to keep you guys awake we will provide some games with some cool prizes you will definitely enjoy :)

    07:00 : Breakfast

    4 more hours left you better want to have enough energy! What is better than some fresh sandwiches?

    11:00 : STOP Hacking

    After 19 hours of coding it's time to close your code editors and get ramped up for the demos. NO MORE COMMITS from this point on.

    11:00 - 13:00 : Brunch and Demo preparation

    Use this time wisely to prepare your demos and grab a bite in the servery.

    13:00 : DEMO Time

    It's time to show off what you did in the last hours in front of a jury and everyone who is interested. Remember: No PPT slides! Check the rules for the length of the demos.

    14:30 : Judging Time

    The judges will gather up to make a decision on who won.

    15:00 : Award Ceremony

    Time to give out the prizes for the first jacobsHack!

    15:30 : YOU DID IT!

    Now it's time to finally rest :)

More

Rules

The basic rule set is taken from AngelHack and adjusted to jacobsHack! 1. Fresh Code We all start coding at the same time. This is done to keep things fair. Please don’t come in and build on to...

The basic rule set is taken from AngelHack and adjusted to jacobsHack!

1. Fresh Code

We all start coding at the same time. This is done to keep things fair. Please don’t come in and build on top of previous projects if you want to win. It’s cool to work on designs beforehand, digital mockups, open source frameworks, and anything else available to everyone, but try to keep things within just limits

2. Code Review

Winning teams will be subject to a code-review at some point following the event or immediately before winning

3. Ownership and IP

Teams have full ownership of everything they build at our events and are free to do with it as they wish

4. Team Size

Teams of up to 4 humans are allowed. You can also add 1 cyborg, Furby, drone, or Sphero

5. T-Shirts

As we will hack in the College 3 QSA we can not block the venue for outsiders. In fact people are more than welcome to pass by and watch. However as we provide all food and drinks for free we want to make sure that all participants benefit from it. To make sure that only parcticipants consume the drinks and food we ask everyone to wear the T-Shirt you'll receive at the beginning. If you don't wear the T-Shirt you are not eligable for any of these benefits. Also please don't give food or drinks to your friends who are non-participants.

6. Submissions

Every project/team needs to be registered at hackathon.io and additionally provide the link to an accessible git repository. This should be preferably GitHub but can be a private git repository as long as the organizers and judges are granted access to check the code and commits

7. Disqualification

We want a fair competition and are not planning to disqualify anyone however if any of the following things is violated we sadly have to disqualify you (and in cases your team):

  • There are commits done after Sunday 11:00.
  • We see you working on your code after the deadline in order to fix your Demo.
  • You give the drinks/food provided at the hackathon to non-participants.

8. DEMO your Hack

You must demo your hack in order to present. No slide-decks or power-points will be allowed. Don’t be scared if you didn’t finish… it’s okay long as you tried your best. The presentation shouldn't be longer than 3 minutes followed by a 2 minute Q&A.

9. HAVE FUN!

It’s a hackathon! Use whatever languages or hacks you have in your arsenal. Show us hardware. Show us new concepts. Show us anything you’d like