Meta: Require MCP and relevant team nominations for adding (ecosystem, custom codegen backend) testing jobs that would block PR/Merge CI and require documenting failure protocol

[jieyouxu]

Note: This is intended to be an approximation to cross-team MCPs¹.

I'm proposing a new rust-lang/rust policy (it's drafted as a compiler MCP but with multiple team nominations) that we require MCP and relevant team nominations for adding (ecosystem, custom codegen backend) testing jobs that would block PR/Merge CI and require documenting failure protocol.

Please let me know if nominated relevant teams have suggestions, concerns or other feedback.

There's no I-{team}-nominated labels for some teams, so I'll have to do it manually (sorry):

• cc @rust-lang/rustdoc
• cc @rust-lang/bootstrap
• cc @rust-lang/infra

Footnotes

1. https://rust-lang.zulipchat.com/#narrow/channel/486433-all-hands-2025/topic/Project-scope.20MCP ↩