Create linker subteam/Working Group #964
Description
Proposal
Background
Last Autumn, I opened the proposal to integrate the Wild linker with nightly Rust: #917. During the discussions, it was proposed to instead create a subteam or Working Group that drive it, without needing to involve the broad T-compiler. The exact form is not yet decided, but I'm hoping to reach the consensus in discussions.
This proposal addresses that (totally not a proposal in response to a proposal regarding the original proposal).
The Goals
The main motivation and one of the goals for this proposal is to gather a group of people knowledgeable about linkers, linking process and how it relates to Rust project. Even if just as different sides for the discussions to make them more meaningful. This will allow driving the integrating of Wild linker with Rust, without bothering people unfamiliar with the topic.
As the second goal, T-compiler members indicated they could use a point of contact for handling questions and issues regarding linkers. To meet that, this group needs to gather familiar with linkers used by tier 1 targets and the linking process (you can consider this as an invitation). I believe the questions towards lower tier targets would be better addressed by their respective maintainers. This also means you don't even need to care about the Wild linker to help.
Joining
I don't want to persuade anybody, so I decided to make this fully open. You can even add yourself (if you have edit rights here) and/or leave a comment in Zulip's stream for this MCP.
Mentors or Reviewers
If you have a reviewer or mentor in mind for this work, mention them here. You can put your own name here if you are planning to mentor the work.
Process
The main points of the Major Change Process are as follows:
- File an issue describing the proposal.
- A compiler team member who is knowledgeable in the area can second by writing
@rustbot secondor kickoff a team FCP with@rfcbot fcp $RESOLUTION.- Refer to Proposals, Approvals and Stabilization docs for when a second is sufficient, or when a full team FCP is required.
- Once an MCP is seconded, the Final Comment Period begins.
- Final Comment Period lasts for 10 days after all outstanding concerns are solved.
- Outstanding concerns will block the Final Comment Period from finishing. Once all concerns are resolved, the 10 day countdown is restarted.
- If no concerns are raised after 10 days since the resolution of the last outstanding concern, the MCP is considered approved.
You can read more about Major Change Proposals on forge.