Status

• 2022-10-19: initial draft. It has had verbal buy-in from @Steve (biglep), @Alex Potsides, and @Deleted User~~, but @Steve (biglep) and @Deleted User haven’t reviewed/agreed on the actions~~. @Steve (biglep) and @Deleted User have agreed on the actions. It hasn’t been surfaced to other informants like @lidel or @Daniel Norman (which will happen in #ipfs-nexus).

Purpose

This document is being used to coordinate the efforts (plans, actions) around IPFS-in-JS for Lab Week 2022 and particularly IPFS Camp 2022.

Goal

IPFS Camp 2022 is a great opportunity to message about IPFS-in-JS, particularly about what’s coming and how others can contribute because many community members will be there and there is a “platform” to message from. We want to take advantage and maximize this opportunity.

Success looks like:

1. Increased understanding amongst IPFS stakeholders and users that “IPFS-in-JS” is not dead or in maintenance mode, but rather has tangible items for 2023 to increase impact. There is general excitement about the direction and possibilities for IPFS-in-JS. Tangibly, we should be able to sample people in the community about IPFS-in-JS and get responses like, “Yeah, that project has a plan for moving forward. I’m excited to see what happens in 2023.”
2. Increase in contributors and contributions to IPFS-in-JS. This should show up via PRs/comments in GitHub repos, particularly in “Peach”, “Pomegranate”, docs, and example repos.

Messaging Vehicles

State of IPFS-in-JS Blog Entry

We’ll get a blog entry that captures current thinking in writing. This serves as something durable that the community can point to, and it allows those not at the event to more easily follow along with the direction. This is being drafted in [In Progress] 202210 State of IPFS in JS. There are related actions before this would be published that are being tracked in Actions. This should be completed before IPFS Camp.

State of IPFS-in-JS IPFS Camp Presentation

@Alex Potsides is giving a talk on the “State of IPFS-in-JS” in the IPFS Implementations Track. It will be a verbal form of similar content to State of IPFS-in-JS Blog Entry, but with more visuals and maybe some @Alex Potsides humor 😃. It will also emphasize an invitation to contribute and publicize Community call to arms: propose and vote on names for IPFS-in-JS projects.

Community call to arms: propose and vote on names for IPFS-in-JS projects

We are currently using temporary names in [In Progress] 202210 State of IPFS in JS of “Peach” for js-ipfs and “Pomegranate” for the the new JS IPFS implementation we’re proposing. We want to establish permanent names for these projects that don’t squat on the IPFS namespace (per motivation here). We plan to take a similar tact as go-ipfs/Kubo with soliciting ideas and votes from the community (but with ultimate decision making powers by the maintainers).

The reasons for involving the community here include: