Skip to content

Link the contributing guidelines in CONTRIBUTING.md#158160

Open
apiraino wants to merge 1 commit into
rust-lang:mainfrom
apiraino:mention-forge-in-contributing
Open

Link the contributing guidelines in CONTRIBUTING.md#158160
apiraino wants to merge 1 commit into
rust-lang:mainfrom
apiraino:mention-forge-in-contributing

Conversation

@apiraino

Copy link
Copy Markdown
Contributor

This file is supposed to be the entrypoint for new contributors, so it's helpful if we point them also to our extensive documentation about how to start interacting with the project.

The rest of the document will help with the more technical aspects (and where to ask for help).

Discussed on Zulip.

cc @jyn514

r?

@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 19, 2026
@rustbot

rustbot commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
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:

  • Fallback group: @Mark-Simulacrum, @jieyouxu
  • @Mark-Simulacrum, @jieyouxu expanded to Mark-Simulacrum, jieyouxu

This file is supposed to be the entrypoint for new contributors, so it's helpful if we point them
also to our extensive documentation about how to start interacting with the project.

The rest of the document will help with the more technical aspects (and where to ask for help).
@apiraino apiraino force-pushed the mention-forge-in-contributing branch from 786d73e to cf029ac Compare June 19, 2026 22:22
@rust-lang rust-lang deleted a comment from rustbot Jun 19, 2026
@jyn514

jyn514 commented Jun 20, 2026

Copy link
Copy Markdown
Member

This file is supposed to be the entrypoint for new contributors, so it's helpful if we point them also to our extensive documentation about how to start interacting with the project.

according to who? my impression has always been that https://rustc-dev-guide.rust-lang.org/ is the entrypoint for new contributors; i didn't even know this forge link existed. i note that there's a bunch of docs duplicated between the two.

i also want to note that this is the very first link at the very top of CONTRIBUTING.md, which means that it's going to be the first thing people click. i would really prefer to keep zulip as the first link and only add the reference documentation below it.

@Kobzol

Kobzol commented Jun 20, 2026

Copy link
Copy Markdown
Member

We periodically get new people coming to Zulip, who say something about them and say hi, and then maybe get an emoji response back.

Going to Zulip can be a useful pathway, but we should also have some actual written documentation that tells people some ground rules and how to begin. We have such a page, and so IMO we should link to it in the contributing file (an alternative would be to write all that down in CONTRIBUTING.md, but I think it is more practical to keep that info in the Forge, at least for now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-meta Area: Issues & PRs about the rust-lang/rust repository itself 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.

5 participants