A new proposal has been announced #296. It will be brought up at the next meeting.
@Santiago Pastorino @mark-i-m I think discussion is supposed to take place here rather than on GitHub.
I think the first step to do this would be editing the sections in the "Getting Started" section of the dev-guide to make them a bit more linear (e.g., do this, run that, push to Github) while moving the more detailed bits later in the guide. This part doesn't really need compiler-team input. Only the final stage does, where we would replace
It seems like something like this has been on your radar for at least a while, and it seems to be well-received, so what do I need to do to get things started? Are we at the "PRs welcome" stage?
make them a bit more linear (e.g., do this, run that, push to Github) while moving the more detailed bits later in the guide
I think this sounds pretty much like what @Santiago Pastorino and I were thinking. IMHO, a PR would make sense from the rustc-dev-guide side. I think we wanted to do this regardless of what happens to CONTRIBUTING.md
agree with @mark-i-m
I tend to agree that CONTRIBUTING.md just feels like it's duplicating rustc-dev-guide
particularly since we are now managing library impl...
I'd be happy to second the proposal
@T-compiler: Proposal #296 has been seconded, and will be approved in 10 days if no objections are raised.
I am proposing https://github.com/rust-lang/rustc-dev-guide/pull/753. I think it should be orthogonal to this MCP, but just wanted to make a note of it
(btw the zulip stream title here is somehow garbled so I was rather confused until I followed the GH link^^)
We're limited to 60 characters total on Zulip topics so we just truncate
@simulacrum What do you think of adding an ellipsis at the end so that it's clear that it was truncated?