Tracking issue: mplex deprecation
Open
Nobody has claimed this yet.
in progress
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Things left to do:
- https://github.com/ipfs/kubo/issues/9958
- https://github.com/libp2p/test-plans/issues/196
- archive https://github.com/libp2p/go-mplex
- remove it from go-libp2p transport suite: https://github.com/libp2p/go-libp2p/pull/2402
- mark it as deprecated in the specs
- blog post https://github.com/libp2p/blog/issues/106
- remove from docs.libp2p
- deprecate from js-libp2p
@achingbrain Anything left to do on the JS side?
@mxinden @thomaseizinger Anything left to do on the Rust side? Feel free to add to above list.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the unchecked items and linked issues for the test plan, go-mplex archive, specs, blog post, and docs.libp2p removal. Confirm the remaining JS and Rust work in the linked project discussions; this tracking issue is done when each checklist item is completed and the mplex deprecation is reflected across the named projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript, rust
- Domain
- documentation, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100