We are planning the Project & Community track for the coming IPFS Camp and we want to hear from you what you think should be in it — even if you’re not attending.
We’ve broken it down into three sections:
IPFS: Invidious Presentations and Feuding Session
The goal of this section is to stir things up: we want 3-5 thought-provoking presentations, ~10m each, followed by joint discussion/reflection. Note that when we say provoking, we mean it.
In the “governing the commons” section, I think the public network and utilities is one of the best candidates to truly “exit to community”. As IPFS transitions out of Protocol Labs incubation, there’s a good opportunity to ensure users and community leaders — particularly ones using the public utilities to improve digital human rights and access to information — have seats at the table to set future goals for availability, privacy, and other aspects of the network.
I love the salty presentations idea. There are lots of and I think some strong opinions, loosely held, can be a good way to open up some challenging conversations. I’m interested in preparing or contributing to the “We Need To Talk” topic.
could we consider some call to actions that have varying weights to them (from say I can do this right now in 2 mins to this might take 2 years) and see if we can get some community willing to be the change to whats not working for them…
I have been spelunking around in old threads here and on github thinking about interop and decoupling. If there is appetite, I have been thinking about “internal specs” and “internal interop”, which could from one angle be seen as a productization discussion or from another just a backlog generation/ordering exercise. I wrote up (excessively detailed) notes for anyone curious: