Seeking new or expanded maintainership of the smallvec crate

[mbrubeck]

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?

[nicoburns]

It might be worth bringing this to the attention of the rust libs team. smallvec is extremely widely used (34th most downloaded crate overall), and it also used by rustc itself.

[TDecking]

I actually started contributing because I wanted to drag v2 over the finish line. That said, I do not have a lot of maintainer experience.

[FelixSelter]

I also have zero maintainer experience but I am willing to help. Any suggestions on what I should work on?

[mbrubeck]

For getting the v2 release ready, here are some things that I think anyone interested could help with:

• Look through the changes that landed on the v1 branch after it diverged from v2; make a list of which ones are missing from v2; and file issues or PRs for any that should be forward-ported to v2.
• Benchmark v1 versus v2, and file issues or PRs for any performance regressions.
• Draft release notes for smallvec 2.0.0, especially a summary of the most significant breaking changes (e.g. removed or renamed methods).
• Figure out what work is needed for Add a RawSmallVec type #245 and/or if we should merge Make RawSmallVec private (v2). #348 for now.