Create Problem statements

[9rb]

Use the template + repository created in item 16
potential sources for problem statements are rchat, rvote, liquid democracy, spv needs, rcat / rsong, rchips (rholang extensions), rholang v1.1, Decentralized id,

[dckc]

Do we have any problem statements yet? Pointer, please?

This "problem statement" terminology is new to me. I haven't seen it used at other hackathons. Point me at precedents?

[9rb]

template:
https://www.hackerearth.com/blog/developers/how-to-create-effective-problem-statements-for-idea-challenges-and-hackathons/

1. Describe the problem to be solved and why it's important
2. Point to existing resources for more information- for e.g. in case of decentralized id, point them to the w3c spec, identity.foundation etc.
3. Success criteria for this hackathon deliverable

[dckc]

FWIW, I have been putting ideas in https://github.com/orgs/rchain-community/projects/1 when they occur to me.

I was thinking of making a handful of slides for each idea that I might want to present at the hackathon in hopes that a team would form around it.

I don't see a session for presenting ideas / team formation in the schedule sketch in #12 (comment) , though.

I'm still struggling to see how "problem statements" fit into the typical hackathon structure

Hackathons typically start with one or more presentations about the event, as well as about the specific subject, if any. Then participants suggest ideas and form teams, based on individual interests and skills.

The example article above talks about problems to be solved over 5 years, not 2 days.

Is a problem statement intended to be used to recruit team members? Do you plan to allow time for problem statements to be presented?

[dckc]

@9rb recently suggested "If it [ranked choice] s not ready, it's perhaps a prime candidate to become a problem statement ?"

The issue is rchain-community/rvote#59

I think issues are a pretty good way to represent problem statements.

In this case,

1. the issue says why it's important
2. it's surrounded by the natural context for more information
   • if what's there isn't clear, someone can straightforwardly request more info by leaving a comment
3. the success criterion comes for free: the issue is fixed to the satisfaction of at least one person with merge rights in the rv2020 repo

[9rb]

Rao to continue to use this issue to track the list of problem statements to be created. Actual problem statements would be individual issues. Use priority or labels on problem statements to indicate this hackathon or future hackathons.