multiformats / multiformats/rust-multiaddr
`/webrtc` `/webrtc-direct` rename proceeding
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 101
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Tracking next steps to do the /webrtc -> /webrtc-direct rename (https://github.com/multiformats/multiaddr/pull/150#issuecomment-1468791586) with potential for collision with the introduction of /webrtc (browser-to-browser) https://github.com/multiformats/rust-multiaddr/pull/79.
- Release https://github.com/multiformats/rust-multiaddr/pull/84 as non-breaking change
- Release breaking change from
Protocol::WebRTCtoProtocol::WebRTCDirecthttps://github.com/multiformats/rust-multiaddr/pull/78. - Release https://github.com/multiformats/rust-multiaddr/pull/79 as a non-breaking change.
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 checklist and the referenced rust-multiaddr pull requests #78, #79, and #84, along with the linked multiaddr discussion. Confirm the breaking rename from Protocol::WebRTC to Protocol::WebRTCDirect and the subsequent non-breaking release. Done means both unchecked release steps are completed and the protocol naming collision is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100