With the backdrop of current geo-politics and a recent article (in norwegian, sorry) on using Solid as a basis for a new and better foundation for common applications a group of us are planning a hackaton to see what cool applications of Solid participants can dream up.
The hackaton will be a live event in small-ish town in Norway. We still expect a reasonable attendance as we are supported by significant parts of the IT community here.
Does you have any hints or tips to how we should organize or conduct this hackaton? Any experiences you would like to share and pitfalls we might want to avoid?
Hi @kentis we (ODI) might be able to support to an extent in our position stewarding Solid. We are looking to get some re-usable materials hackathon materials in place; including easy “getting started materials” - both short explainer documents, and some opinionated codebases that have things like authentication already set-up (also with some help from @jacksonmorgan).
Suggestions:
Avoid participants making too many decisions - there are lots of libraries, to choose form; for a hackathon with first timers with Solid, it is good to have a clear set of decisions around tooling made for them
Make sure you know your participants and structure goals accordingly. If you have front-end dev’s as your target; you probably don’t want them to need to dig to deeply into RDF and data modelling - so the templates you have set up in advance should come with appropriate
Easy wins - if you want to have some things that people can publish after 1-2 days; you could consider a hackathon (or a track of) that is “building solid plugins for existing ecosystems” to help get Solid into Discourse, Slack, on your file system, in your code editor … this means you are more likely to get a complete product that really helps support the adoption of Solid done within the scope of a hackathon!
Feel free to flick an email to solid@theodi.org if you’d like to set up a call.
