# IPFS Stewards <> Advocates sync 9.12.2022

## Participants

- Daniel
- Lidel
- Mosh
- Discordian
- Jamz
- TMo
- Elliot

## Discussion topics

- Name chosen for the new JavaScript implementation (Elliot)
- Part of the broader effort for more implementations. Avoiding name squatting js-ipfs
- [**Helia**](https://github.com/ipfs/helia) is the new name!
- Q: What's the right word to communicate the status of js-ipfs -> Helia?
- js-ipfs is in maintenance mode until Helia is released at which point js-ipfs will deprecate.
- Both are a wrapper over the same libs (libp2p, ipld, js-ipfs etc).
- Aiming for a first release by end of Q1 2023
- We are looking to grow the team! If you know of anyone let Steve, Alex, or Elliot know!
- IPFS Community calendar
- Migrating from Gcal to Luma
- https://lu.ma/ipfs
- @discordian Added the open office hours to the : https://lu.ma/IP-Office-Hours
- Stewards IPFS Roadmap
- Stewards and broader IPFS efforts
- Metawork on the [starmaps roadmapping tool](https://www.starmaps.app/)
- We have an example from the [bedrock team](https://www.starmaps.app/roadmap/github.com/protocol/bedrock/issues/15?crumbs=%5B%5B%22protocol%2Fbedrock%231%22%2C%22Bedrock+Roadmap+Root%22%5D%5D#simple)
- Helia roadmap: https://github.com/ipfs/helia/blob/main/ROADMAP.md
- Ignite (IPFS GUI & Tools) roadmap: https://www.starmaps.app/roadmap/github.com/ipfs/ipfs-gui/issues/106
- IPDX roadmap: https://www.starmaps.app/roadmap/github.com/pl-strflt/ipdx/issues/67
- Testground roadmap: https://www.starmaps.app/roadmap/github.com/testground/testground/issues/1491
- IPFS Docs migration and reorg
- [James' proposal](https://www.notion.so/pl-strflt/IPFS-Docs-Migration-and-Reorg-Discussion-Planning-Tracking-aa9516ab1cbb48968993ce3fb2059282)
- Involves a new implementation with more flexibility that is already used for the Filecoin docs
- Timeline: beginning of 23Q1 to share architectures with a concrete pitch and example websites.
- Implementation specific docs:
- Either have a dedicated subsection in the docs or a separate site.
- James' perspective : It wouldn't be best to leave the docs in GitHub.
- Mosh: in the long term it might make sense to have guides
- Next steps:
- Engaging with the community to review the proposals
- Come up with 1 or 2 more information architectures (in addition to the two already in the proposal) and open to community to vote on GitHub
- Announce it (on multiple channels)
- Besides that, the the docs team hs
- Public IPFS metrics
- Some numbers to show on the website
- What's a node?
- Distinction beween DHT servers and total peers
- Content resolution time
- Engres Metrics
- https://docs.google.com/spreadsheets/d/1OITjakfkvT62IPCSSw0qUWLWod6sTgC8O542_C4V9eM/edit#gid=1309528099
- Nebula metrics: http://162.55.187.75:3000/d/CSQsORs7k/nebula
- IPNS with crypto wallets
- https://github.com/ipfs/js-ipns/pull/192
- [libp2p key types](https://github.com/libp2p/specs/blob/master/peer-ids/peer-ids.md#key-types) & [IPNS key types](https://github.com/ipfs/specs/blob/main/ipns/IPNS.md#key-types)
- Secp256k1 is actually