[Tracking Issue] js-ipfs deprecation - signposting over to Helia about js-ipfs HOT 9 CLOSED

related: ipfs/ipfs-gui#107 & ipfs/ipld-explorer-components#359

from js-ipfs.

I talked to @RangerMauve about migration to helia and it sounds like libp2p/js-libp2p#1461 is a blocker

from js-ipfs.

Chatting with @achingbrain about rough requirements/plan for migration

1. Notes in all the readmes.
2. deprecation notes on NPM, (all packages inside js-ipfs repo)
   • deprecate ipfs-utils
3. migration guide
   • "I used to use these APIs with js-ipfs, but now i use these with helia like this" - for all happypath
     • We would add sections for specific non-happypath cases, or "case-studies" where we've migrated old tooling (like ipld-explorer-components and ipfs-share, etc.)
   • @SgtPooki - Use notion doc for documenting specific usecases while working on js-ipfs deprecation for ipfs/ipld-explorer-components#359 & ipfs-share
4. Closing/migrating all js-ipfs issues with pointer to migration guide & helia

something I thought of during our talk:

4. boilerplate messages for js-ipfs issue closing/cleanup
   • One message for issues that should check if helia solves their problems
   • Message for issues that definitely have solutions in helia
   • Message for unsupported things where users may be better suited to use js-kubo-rpc-client instead of helia

from js-ipfs.

Some updates on preparing for the deprecation:

1. The issue has been updated with more thorough task lists.
2. A project board has been created (https://github.com/orgs/ipfs/projects/26 ) to track the handling of the open issues in js-ipfs.
3. The deprecation process and messaging is all being drafted in https://pl-strflt.notion.site/2023Q2-js-ipfs-Deprecation-c84d5d4f661044198ba6e63bf0a34790 (to allow for easier commenting)

from js-ipfs.

2023-05-23 update: we're getting close to doing the disruption phase. Some updates:

1. This issue itself had some updates with more text filled in, tasks rearranged, and expected completion dates added.
2. The issue handling process and messaging has had various updates: https://pl-strflt.notion.site/2023Q2-js-ipfs-Deprecation-c84d5d4f661044198ba6e63bf0a34790

from js-ipfs.

2023-05-24 update: we have completed all the "preparation tasks" and will start in on the "disruption tasks". The team has the goal of making it through the 300+ js-ipfs issues and PRs by end of week (2023-05-26).

from js-ipfs.

Per https://github.com/orgs/ipfs/projects/26/views/2, 372 issues and/PRs have been closed. There is one open item :). We'll sweep back through on 2023-06-08 to see if any issues have reopened. If there aren't any, we'll move forward with repo archiving.

from js-ipfs.

Given no issues have been reopened over a week per #4336 , I'm going to archive this issue. That will prevent this issue from being mutated. We have tracking items for the relevant documentation items. When those are all done, we'll come back, unarchive the repo, and close this last issue.

Thanks all for your work and support in making this effort happen. Well done.

from js-ipfs.

I'm closing this issue now that the docs issues were completed. The only thing that wasn't done was around proto.school, but dealing with messaging about the outdated nature of that overall site is a separate endeavor.

from js-ipfs.