Seeking new or expanded maintainership of the smallvec crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 216
- Avg merge
- 17h 50m
- Merged PRs (30d)
- 95
Description
I am currently the main active maintainer of the smallvec crate, and I will continue to maintain it until I am able to hand it off to someone else. However, I have not been able to give it the time it deserves, leading to some long-delayed pull requests. Also, a stable 2.0.0 release is long overdue. I'd like to improve progress on these things by bringing in at least one more active maintainer.
The Servo project owns this repo and are the de-facto backup maintainers. @jdm, is there someone on the Servo team who can take a more active role in this crate? And @TDecking, you have done most of the recent work the v2 branch; would you be interested in taking a larger role in getting it released?
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
This issue is about finding additional maintainers for the smallvec crate, resolving delayed pull requests, and progressing the v2 branch toward a stable 2.0.0 release. It names no source files, tests, or concrete implementation task, and provides no newcomer-checkable definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100