In pursuit of fair co-creation === <span style="background:yellow">**[Slides from our DINAcon 2018 session]( now available!**</span> [In pursuit of fair co-creation]( was a workshop facilitated by Gonzalo Casas, Oleg Lavrovsky & Reto Wick on October 19 in Bern. See also: [literature list]( Please contact our interest group for more information, [edit]( this document if you have something to add, visit [this forum thread]( or our community [chat channel]( ([invite link](, or write to *info* @ - to join the discussion. The following people have contributed to this discussion: - Gonzalo Casas / [researchgate]( - Oleg Lavrovsky / [researchgate]( / [blog]( - Reto Wick / [dinacon]( ## Outline *Our plan of questions and topics for the workshop.* - How do you decide what hackathon to join? - Ask every participant to **share an event** they are planning to go to and/or have been at. - Bring a stack of Green and Red Post-Its for people to suggest "attractors" and "detractors", that we'll use in the **Flowchart** later on. - Let's define our scope - "subject" -> **[hackathon](** - (informal, neologism) An event where programmers and others meet for collaborative software development. - "predicate" -> **[exploitation](** - Borrowed from French exploitation, from exploiter (“exploit”), from Latin explicō (“unfold, deploy”). - "object" -> **[precarization](** - (sociology) a condition of existence without predictability or security, affecting material or psychological welfare. - Share relevant projects - **Online platforms** - See [Mechanism for hackathon discoverability]( in [DRIBDAT]( (see [Whitepaper]( and [MakeZurich repo]( (2018) - **Research projects** - [Hackathon as a Method: Social Innovation and Inclusion in the Social Sector]( (2019) - **Reading club** - We will print copies of a card with the link to our [literature list](, in the style of the [Make badge]( - Lens / perspectives - **Role of the challenger** - Alignment of the expectations is critical between the organizing team and the challengers/experts/sponsors who take a initiating or guiding or managing role. - A recurrent source of friction is challengers who miss the point or are underwhelmed with the hackathon. - **Role of the participant** - Finding people you can work with is generally hard, the hackathon is team building on jet fuel. - Matching everyone's [expectations]( is hard, and guidelines can help. - We do not have many established tools and techniques for being effective during a hackathon. - **Role of the infrastructure** - What tools help us to make sure we build confidence in hackathons. - From pomodoro techniques, to build boxes, to data resources, to network and computing infrastructure, to environmental design. - Next steps - **Join the Hacknight, or another hackathon** - - - - ...start your own! - **Help make a Flowchart** - In a playful way our discussion should help to together define the criteria that will enable the discoverability thinking that will be part of Dribdat, etc. - As the "take home" part of the workshop, each participant who leaves us their postal address will get a nicely printed poster first edition, and possibly chocolate `;-)` - **Join the online discussion** -