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
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Note: This is intended to be an approximation to cross-team MCPs^cross-mcp.
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
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
Start with the linked compiler-team MCP issue 845, then read this proposal and the cross-team MCP reference. Review feedback from the nominated rustdoc, bootstrap, and infra teams; done is a documented, agreed policy and failure protocol for the specified CI jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100