This track aims to create space for advancing the IPFS project and community. New session proposals are welcome, especially those that focus on a specific, actionable subtopic rather than attempting to grapple with the entire universe of project and community stewardship at once.
@mosh is track lead
A walkthrough of the new IPIP (RFC-like) process and its motivations, updated specs repository, and when and why you should submit an IPIP. Q&A at the end.
@dietrich - Slides - Video (to come)
Discuss evolving web-wide standards & specs that might benefit from participation from our community. Examples include upcoming deadline at IETF for multi* stuff started long ago, and W3C activity around extensions APIs and webviews and wallet APIs.
IPFS has ‘won’. Content addressing is a sustaining innovation that can make its way into many more places. Discuss creating a cross-organization Content Addressable Alliance that advocates and promotes the usage of content addressing.
Brief session on history of funding IPFS implementations, and exciting updates going forward.
Learn what happens in a given month in IPFS development for projects like Kubo, js-ipfs, and supporting the wider community. You should walk away with better insight into venues you can engage the maintainers and ideas/input will be welcome as well.
This session will be a walk through how PL manages IPFS GitHub organization configuration as code using a tool called GitHub Management. It’ll provide practical information on how to request changes to the configuration (for example, if you contribute frequently to a repository within IPFS and you’d want to become a collaborator) and how to set up a similar solution in any other GitHub organization.