Hack for the Sea is a "blue" hackathon: Blue tech, blue economy, blue sky. We gather professionals from all fields, of all ages in one place for a weekend in Cape Ann, Massachusetts to put our heads together and attempt to make traction on the difficult, intractable, and impossible challenges that face the ocean and our relationship with it.
If you're reading this, the question is:
If you had dozens of talented people for a weekend to help you help the ocean, what would you ask for?
If you have an answer, leave a comment below.
Guidelines
The best challenges are outcome based and well framed.
Requirements
All challenges must have:
- A beneficiary - Usually an organization that is officially posing the challenge. Open to individuals as well.
- Your main question - This should be a one-sentence question that is well framed, and will serve as the title for your challenge. See below for guidance.
- A description - Two or three paragraphs that sufficiently describe the outcome that you're looking for. Don't focus on how it happens, focus on what you want.
- Some sort of provision in the form of a data set, hardware, or something commensurate that the participants have access to, uniquely provided by the beneficiary to help them face the challenge. This is optional but HIGHLY recommended.
- This sentence at the end: "We agree to release all work contributed to the hackathon as public domain, either via a free and open source software license, or via a Creative Commons Attribution-ShareAlike license"
Finally, the beneficiary will be responsible for the prize associated with the challenge. The prize will not touch the organizer's hands and will instead be delivered directly from the beneficiary to the participants. Keep this in mind as you craft your challenge. Prizes can be monetary or non-monetary, but in most cases, non-monetary is preferred as to not corrupt the spirit of the event.
Framing the Challenge
A good challenge can be expressed in the form of a yes or no question, where the answer is currently unknown or "no." Some of the recent challenges have been:
- Can you fingerprint a whale based on its blowhole?
- Can you predict when cod spawning can occur?
- Is it possible to build a sustainable, but also usable mooring?
Bad challenges are either:
- A veiled ask for a specific project, e.g. "Build me a better X."
- Questions with answers. For example, one of the challenges from last year was "How does a changing coastal watershed affect coastal waters?" has an answer: "Negatively."
Hack for the Sea is a "blue" hackathon: Blue tech, blue economy, blue sky. We gather professionals from all fields, of all ages in one place for a weekend in Cape Ann, Massachusetts to put our heads together and attempt to make traction on the difficult, intractable, and impossible challenges that face the ocean and our relationship with it.
If you're reading this, the question is:
If you had dozens of talented people for a weekend to help you help the ocean, what would you ask for?
If you have an answer, leave a comment below.
Guidelines
The best challenges are outcome based and well framed.
Requirements
All challenges must have:
Finally, the beneficiary will be responsible for the prize associated with the challenge. The prize will not touch the organizer's hands and will instead be delivered directly from the beneficiary to the participants. Keep this in mind as you craft your challenge. Prizes can be monetary or non-monetary, but in most cases, non-monetary is preferred as to not corrupt the spirit of the event.
Framing the Challenge
A good challenge can be expressed in the form of a yes or no question, where the answer is currently unknown or "no." Some of the recent challenges have been:
Bad challenges are either: