Breaking API changes and other feedback requests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
I am opening this issue to provide a central place that users of rust-libp2p can subscribe to for potential breaking changes and other feedback requests that the rust-libp2p maintainers might have. The idea is that we (@libp2p/rust-libp2p-maintainers) post a link to a discussion, comment, pull request or issue with a short description as a comment under this issue. This will trigger a notification to every subscribed person and allow them to weigh in on the discussion if it concerns them.
Please refrain from discussing within this issue itself but use emoji reactions instead to indicate your thoughts (if you want to):
- 🚀 I've read the discussion and I support the idea.
- 👀 I've read the discussion and I am ambivalent about it.
- 👎 I've read the discussion and I disagree: Please weigh in on the linked discussion itself so we can iterate on the idea.
Contributor guide
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
The issue does not name any source files, tests, or implementation entry points. Read the issue's comment thread and any discussions it references first; completion is not defined beyond maintaining a central place for feedback and breaking-change notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100