Skip to content

Comments

Suggest using MCP and RFC for substancial changes#1013

Open
apiraino wants to merge 1 commit intorust-lang:masterfrom
apiraino:suggest-using-mcp-rfc
Open

Suggest using MCP and RFC for substancial changes#1013
apiraino wants to merge 1 commit intorust-lang:masterfrom
apiraino:suggest-using-mcp-rfc

Conversation

@apiraino
Copy link
Contributor

@apiraino apiraino commented Feb 21, 2026

As per discussion on Zulip, our documentation is probably not clarifying immediately the paths to contribute substancial changes (MCP/RFC).

Added a little bit of wording and links to hopefully help new contributors.

r?

thanks!

(suggestions on wording are welcome!)

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 21, 2026
@rustbot
Copy link
Collaborator

rustbot commented Feb 21, 2026

r? @lukas-code

rustbot has assigned @lukas-code.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: compiler
  • compiler expanded to 68 candidates
  • Random selection from 67 candidates

@rustbot

This comment was marked as off-topic.

@rustbot

This comment was marked as off-topic.

@rustbot
Copy link
Collaborator

rustbot commented Feb 21, 2026

Error: Parsing assign command in comment failed: ...'
' | error: specify user to assign to at >| '
thanks!
'...

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip.

Copy link
Member

@Urgau Urgau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably also worth linking T-libs-api ACP and T-lang experiments.

View changes since this review

Comment on lines +28 to +36
If you want to contribute substancial changes, please follow the recommended path of a Major
Change Proposal (MCP) or a Request For Comment (RFC) in order to have a prior discussion and
team buyout. You can learn more about what constitutes as "substancial" by reading the relevant
sections of the documentation for the [compiler][mcp-or-rcp-compiler] and for
[rustdoc][mcp-or-rcp-rustdoc].

[mcp-or-rcp-compiler]: compiler/proposals-and-stabilization.html
[mcp-or-rcp-rustdoc]: rustdoc/proposals-and-stabilization.html

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section assumes that you want to contribute to the compiler, T-libs-api use ACP not MCPs, T-lang use experiments, ...

Copy link
Member

@jieyouxu jieyouxu Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ATM as well (not really for this PR but yeah):

  • T-rustdoc uses sth else (maybe just Zulip)?
  • T-bootstrap is just Zulip
  • T-infra is just Zulip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants