#ipofcc summary
During the workshop In pursuit of fair co-creation at #DINAcon18, we discussed time-bounded collaborative events, like …
(turn to next page)
… Hackathons!
Every weekend, masses of people take part in hackathons around the world. From corporate innovation labs to chaotic co-creation jams, from competitive coding to cooperative making, from nondisclosure to open license, there are hackathons for everyone's taste.
Yet, despite common labels, such as 'hackathon' or ‘hackday’, their goals vary greatly. This creates ambiguity that is exploited for work precarization.
These types of events are common to many technical communities. We are part of the following networks which organize events around the year:
To set up the grounds for a discussion, we put together a reading list together with researchers from the Bern University of Applied Science:
hackmd.io/s/S1_nyDIff
You'll find this and more in our workshop outline:
bit.ly/ipofcc
We also proposed an ‚open data driven model‘ for time-bounded events:
- Events are data sources themselves.
- Events are self-describing using a metadata scheme.
- Event meta-data contains classifiers to describe different event typologies.
- Event meta-data describes and links to event data (i.e. projects).
- Event data becomes an integral part of the data source.
hackathon.json
You can read more about this on GitHub: dribdat issue #112 .. or just look at how it is implemented on these sites:
At the DINAcon workshop, we covered fundamentals:
- Defining the scope (hackathons, exploitation, precarization)
- Who are the actors involved (organizers, challengers/sponsors, participants)
- What projects we can support (hackathon platform, research project, conferences)
And together with participants, we built (in a collaborative manner, of course!) a list of attractors and detractors for participation in hackathons.
This inspired us to, during the #hacknight later that day, to start putting the list into a flowchart.
The flowchart is a playful* way to describe the metadata that we believe should be exposed by every hackathon in order to provide fair conditions to decide attendance. It may help to:
- guide potential participants to join (or not) a specific event
- let organizers consider some of the issues at hand
- just amuse or confuse (some) people