Agenda and --verbose

Registration
All participants need to register both online (which you have already done), and in person on Saturday morning, where you can pick up Wifi access info and a name badge.

What you should bring

• Your laptop
• Power supply for your laptop :)
• Fun and a smile

We will provide food, coffee and cold drinks throughout the event.

Agenda
Saturday
9:30            doors open
10:00-11:00  Intro, problems presentation. The group "self-organizes" into project teams. You may also work alone if preferred.
11:00-         The coding marathon begins
13:00-14:30  lunch (we will have snacks, coffee and drinks throughout the whole event)
19:30-20:30  dinner
23:30           night shutdown

Sunday
9:30            doors open
10:00-16:00  coding
13:00-14:30  lunch
16:00           deadline for project submission for judging & prizes
16:00-17:00  projects presentation
17:00-17:30  break  
17:30-18:00  Prizes

Problems and Teams
At the core of RHoK are the problem definitions. These are challenges that pose humanitarian, disaster response, risk reduction and recovery problems where technology can make a difference. The problems are provided by “problem owners”: experts from the field those with existing tools who want help, and those with broad ideas who want to work with others on refining them and/or innovating. We have more than 30 global problems, to be found at http://www.rhok.org/problems. You should have a look through them before the event and see if there are any that excite you.

See http://www.rhok.org/FeaturedProblems for a list of featured problems. Some of them will be presented in detail before the event.

RHoK hacks are owned by their developers but must be made available through an OSI approved open source license, preferably a BSD license (http://www.opensource.org/licenses/bsd-license.html) and posted on GitHub or another open code repository. There will be a github sponsored repository for every project.

Teams
After the pitch/presentations we’ll have posters with the problem definitions laid out around the room. Have a look around, talk to people. Express your interest in a problem by putting your name on the sheet (use a sticky note). Make sure to mention your skills and/or experience.

This is your weekend, so you can work on whatever problem you want, alone or in a group, but we strongly suggest that you join a team of 2-5 other people working on a problem. You can work with remote teams too, so we’re sure you can find a team of others who are working on a problem you’re interested in as working on your own is something you can do at home next week: the problems will still be there. RHoK is about working together, making new friends and contacts, and adding your skills in a unique way.

Have a look at the project pages on the wiki to see what teams have started elsewhere, and if you’re interested in joining forces, or if you’re committed to starting your own. You can either start a new project page on the wiki (using the template), or add your team/names to an existing project somewhere else. Make sure you do the following:

• List your names and location
• List what communications channels you’ll be using. IRC room, skype, phone, email, etc.
• Edit the Problem definition page to link to your team/project page.

Presentation
Teams/individuals will get a chance to present their work at 16:00 on Sunday, with each team allocated 5 minutes to demo/show their project and convince us all how they’ve met the challenge and problem.

We mean it about the 5 minutes, so be ready to get gonged off stage if you go over. This is your (long) elevator pitch.

Sponsors
We are so thankful to RHoK Global and all of the sponsors who helped to bring about this event:

• Bigpoint
• Digital Pioneers N.V.
• Mindmatters
• Betahaus Hamburg
• github.com

We look forward to seeing you all – and if you like to bring a hacking friend, just do it.