-
Notifications
You must be signed in to change notification settings - Fork 1
Getting started
This is the content of the eventstart.md template for new Dribdat events:
Planning your next event? Here are tips for hackathon guru meditation. Skip this page
The starting point of awesome hackathons: a short description of a problem, some initial ideas of solutions which can be realistically attempted during the time constraints of the event. Once you create your event page, you can attach challenges that the teams should respond to.
Create a series of Challenges, which you may want to organize in Categories
Use the Quickstart guide to share tips with challenge owners
Create a Template event if you would like to speed this part up
Some people like to hack on their own - for others, hackathons are all about collaboration and meeting new people. A team generally consists of 3 to 8 people. You can encourage your participants to set up a profile with roles that you can define in the Presets menu to create a smooth team-building process.
Decide what Roles are appropriate to your event
Encourage participants to create an online Profile
Facilitate team-building by having everyone try to Join a challenge
When participants bring their own material (e.g. software or hardware), sharing is encouraged as long as the entire team can use them easily and legally. This is why we encourage the use of free, open source/open data, web-accessible. Try to help participants from a wide range experience levels to get started.
Provide links in your event Instructions, such as to collections of open datasets
Set up a Resources area with tools and datasets recommended for each stage
Customize the event Stages with your own hints and progression rules
In the interest of creating a safe and inclusive environment, we strongly encourage applying clear terms and licenses to your event. We have provided an example at the bottom of every page, which you may modify, and also include a reference to in your opening presentation or e-mailed instructions.
Check the Community section in your event settings, by default this is the Hack Code of Conduct + Creative Commons
Make sure that your organising team is ready to enforce the Code of Conduct, discuss your conditions with participants
Verify compliance during evaluation rounds, when issuing certificates, or other post-event analysis
Disagree with something? Please raise an issue or Edit this page.