From Random Hacks of Kindness
Jump to: navigation, searchAt the core of RHoK are the problem defintions: 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 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 do look carefully before you jump into something similar to what already exists and make sure there's real value in a new statement.
- 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.
Find below an index to existing problem definitions. Please tag any problem definition with the following code to automatically add it to this index.
[[Category:Problem Definitions]]Please use a format similar to ProblemDefinitionTemplate.
The Problem Definitions for RHoK 2.0 are also available.
Pages in category "Problem Definitions"
The following 41 pages are in this category, out of 41 total.
Retrieved from "http://wiki.rhok.org/Category:Problem_Definitions"
via wiki.rhok.org
