Alex Crichton (Jul 07 2025 at 17:31): Alex Crichton (Jul 07 2025 at 17:31):Currently there's only one listed maintainer for the wasm32-wasip1 Rust target (me) but the target is also considered "Tier 2" in the Rust project. Technically, though, Rust requires 2+ maintainers for a "Tier 2" standing and this target was grandfathered in from the ages of old.
The Rust project is looking to start enforcing the minimum number of maintainers, however. There's no plans to remove Tier 2 targets just yet and the MCP explains how this is the "let's get the ball rolling" part as opposed to "the axe is currently falling". Nevertheless I wanted to raise awareness here.
If anyone else would like to be listed as a target maintainer please feel free to volunteer! Rust's target tier policy is here and AFAIK this more-or-less boils down to "please be available for questions from Rust maintainers and occasionally fixing breakages if things become urgent". I at least personally don't spend too too much time maintaining these targets myself insofar that it's not a large time sink.
If you're interested in becoming a maintainer I believe the process is to add your name here.
Alex Crichton (Jul 07 2025 at 17:32):I'll also note that this is all applicable to the wasm32-unknown-unknown target which I'm also the (currently) sole maintainer of. If anyone would like to volunteer for that it would be much appreciated! I realize though that while overlap between these two targets exists this zulip is more centered around WASI things, but I figured I'd raise the issue here too.
Marcin Kolny (Jul 08 2025 at 08:41):Hi @Alex Crichton , I'm already a maintainer for wasm32-wasip1-threads target, so I can volunteer for maintaining the wasm32-wasip1 target too (especially that we have a business usecase for that too). My github alias is @loganek
Alex Crichton (Jul 08 2025 at 14:27):Great! Can you send a PR to rust-lang/rust to add yourself to the list? You can cc me and I can approve it
Last updated: Dec 06 2025 at 05:03 UTC