Closed
Description
Proposal
The contributor survey showed that
- CONTRIBUTING.md is frequently used by contributors.
- A lot of contributors have a hard time finding out how to get started.
Thus, we are interested in making CONTRIBUTING.md a better starting point by moving it's current contents to rustc-dev-guide and instead having CONTRIBUTING.md point to the new Getting Started Guide.
Specifically, we want to merge these two PRs:
- Move contributing.md to rustc-dev-guide and point at getting started rust#73454
- Move CONTRIBUTING.md to rustc-dev-guide rustc-dev-guide#753
This is orthogonal to #296.
Mentors or Reviewers
Process
The main points of the Major Change Process is as follows:
- File an issue describing the proposal.
- A compiler team member or contributor who is knowledgeable in the area can second by writing
@rustbot second.- Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a
-C flag, then full team check-off is required. - Compiler team members can initiate a check-off via
@rfcbot fcp mergeon either the MCP or the PR.
- Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a
- Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.
You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.