Category:Problem Definitions RHoK2.0

[edit] Problems for RHoK 2.0 events

These problems are either new for RHoK 2.0 events or are problems that people are working on/proposed. For all problem definitions please look at Category:Problem Definitions

Use (and follow) Problem Definition Template to add a new problem definition.
Make a video introduction using your webcam

At the core of RHoK are the problem definitions: these are where teams begin when thinking about the contributions they can make and what kinds of hacks they want to work on.

A few short thoughts:

• Problems MUST be related to Crisis Response, Risk Reduction, Recovery or Development. They might be international in scope, or local to a country, but that's what we're all about. There are lots of great problems that we're all interested in that don't meet this criteria, but there are also some other really good venues to work on these so we'll ask you to take them elsewhere. A warning: problems that don't fall in these categories may be tagged "Out of Scope". Doesn't mean we don't like you or your problem. And feel free to start a discussion on the problems - there's a tool for that on each page.
• Problems can be specific e.g. adding features to an existing project, or framed as a general challenge, where teams can spring from. Both approaches are valuable.
• Ideally (but not always) problems have owners - usually the person who authored the problem statement: someone who can offer guidance, more detail and validate concepts. They should be available during a RHoK hack event.
• Check to see what's here before adding your own.
• Just because someone's already worked on, or is currently working on a problem doesn't mean you can't either create a new variant, or start a new solution. But look carefully before you jump into something similar to what already exists and make sure there's real value in a new statement.
• Collaborations are encouraged.
• Similarly there are often a few existing solutions that try to solve the problem. Understanding why they do/don't work will be very valuable.
• Think about your users when framing problems, and when creating solutions.
• The archive of old problems is an interesting place to start if you've no other inspiration. See if it's worth updating them and making them more relevant.
• Problems (and solutions) will live beyond a single event. Many will go inactive however, and that's fine.
• Also of interest might be the Judging Criteria

[edit] Problem Definitions in Other Languages besides English

• RHoK2.0 problema definiciones en Español
• RHok 2,0 defintions Problem in der Deutschen

What we're doing here is building a community curated set of issues and challenges that can and sometimes should be tackled, at a RHoK or by anyone who's inspired or interested. Have fun.