Suggest using MCP and RFC for substancial changes#1013
Suggest using MCP and RFC for substancial changes#1013apiraino wants to merge 1 commit intorust-lang:masterfrom
Conversation
|
r? @lukas-code rustbot has assigned @lukas-code. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Error: Parsing assign command in comment failed: ...' Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip. |
|
Error: Parsing assign command in comment failed: ...' 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
|
Error: Parsing assign command in comment failed: ...' Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip. |
086e7d2 to
19d8667
Compare
src/how-to-start-contributing.md
Outdated
| 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] |
There was a problem hiding this comment.
I gathered this info spelunking on Zulip but it's not documented anywhere. I've just learned myself what "ACP" means 😅
11c3724 to
969979b
Compare
969979b to
2346d99
Compare
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