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!)

Rendered

@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

@rustbot
Copy link
Collaborator

rustbot commented Feb 24, 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.

1 similar comment
@rustbot
Copy link
Collaborator

rustbot commented Feb 24, 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.

@apiraino apiraino force-pushed the suggest-using-mcp-rfc branch 3 times, most recently from 086e7d2 to 19d8667 Compare February 24, 2026 16:03
@apiraino
Copy link
Contributor Author

@Urgau @jieyouxu I've added bootstrap and libs but I'm not t-infra - I am not sure if per se they have a concept of "substancial changes".

Reads better now?

order to have a prior discussion and team buyout:
- Compiler team: a Major Change Proposal (MCP) or a Request For Comment (RFC) (read more [here][mcp-or-rfc-compiler])
- Rustdoc team: open an MCP or an RFC (read more [here][mcp-or-rfc-rustdoc])
- Library team: open an API Change proposal (ACP) on [GitHub][acp-libs] or reach out the team [on Zulip][acp-zulip]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I gathered this info spelunking on Zulip but it's not documented anywhere. I've just learned myself what "ACP" means 😅

@apiraino apiraino force-pushed the suggest-using-mcp-rfc branch 2 times, most recently from 11c3724 to 969979b Compare February 24, 2026 16:24
@apiraino apiraino force-pushed the suggest-using-mcp-rfc branch from 969979b to 2346d99 Compare February 24, 2026 16:30
@jieyouxu jieyouxu self-assigned this Feb 24, 2026
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.

7 participants