Repository: rust-lang/rust-forge
Pull request #846: Add initial onboarding notes
Author: login: Mark-Simulacrum
Labels: name: S-waiting-on-review
description: Status: Awaiting review from the assignee but also interested parties.
Created: 2025-05-16T15:37:10Z | Merged: 2025-05-22T01:55:07Z

The lack of this came up in discussion during an all-hands session as a missing artifact. I'm not sure whether this should be in the Forge (but where else?) but seems like an OK starting point. Also probably much more than just this would be helpful.

cc @rust-lang/leadership-council @carols10cents @JakobDegen @rylev @scottmcm @spastorino

[Rendered](https://github.com/rust-lang/rust-forge/blob/master/src/SUMMARY.md)


Diff:
diff --git a/src/SUMMARY.md b/src/SUMMARY.md
index 625206b20..3a75def13 100644
--- a/src/SUMMARY.md
+++ b/src/SUMMARY.md
@@ -1,6 +1,7 @@
 # Rust Forge
 
 [Overview](./README.md)
+- [Onboarding to the project](./onboarding.md)
 - [Platforms](./platforms/README.md)
   - [Twitter](./platforms/twitter.md)
   - [Discord](./platforms/discord.md)
diff --git a/src/onboarding.md b/src/onboarding.md
new file mode 100644
index 000000000..bc63011d9
--- /dev/null
+++ b/src/onboarding.md
@@ -0,0 +1,54 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- GitHub, via a [new issue](https://github.com/rust-lang/leadership-council/issues/new/choose). This will get discussed at the regular council meeting (to which all project members are [invited](https://github.com/rust-lang/leadership-council/blob/main/procedures/meeting-observers.md)).
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council).
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar; see [Council term limits] for more details.
+
+[Council term limits]: governance/council.md#term-limits
+
+## Relationship to Foundation
+
+The Foundation works to support the Project, and the Project has direct
+representation on the Foundation's board (the 5 Project directors). Those
+directors are selected by the Leadership Council per the [bylaws].
+
+Those directors have 50% of the vote on any Board vote in the Foundation,
+regardless of the number of non-Project directors.
+
+The website has the [current Project directors].
+
+Please reach out whether you're just interested, have questions, or have concerns in:
+
+- Zulip, on [#foundation](https://rust-lang.zulipchat.com/#narrow/channel/335408-foundation).
+- To the Council (see above).
+- To one of the Project Directors (see member list above), recommending Zulip
+  DM as an initial point.
+
+[current Project directors]: https://www.rust-lang.org/governance/teams/launching-pad#team-foundation-board-project-directors
+[bylaws]: https://rustfoundation.org/policy/bylaws/#section-2.4-privileges-of-individual-membership


Reviews:
user: login: traviscross
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-16T16:17:43Z
user: login: Mark-Simulacrum
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-16T16:24:59Z
user: login: ehuss
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-17T22:24:36Z
user: login: Mark-Simulacrum
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-22T01:54:47Z

Review comments:
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council).
```
created_at: 2025-05-16T16:09:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar, see [Council term limits] for more details.
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
calendar; see [Council term limits] for more details.
```
created_at: 2025-05-16T16:10:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar, see [Council term limits] for more details.
+
+[Council term limits]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#term-limits
+
+## Relationship to Foundation
+
+The Foundation works to support the project, and the project has direct
+representation on the Foundation's board (the 5 project directors). Those
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
The Foundation works to support the Project, and the Project has direct
representation on the Foundation's board (the 5 Project directors). Those
```

We go both ways, of course, but's capitalized elsewhere here.
created_at: 2025-05-16T16:12:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar, see [Council term limits] for more details.
+
+[Council term limits]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#term-limits
+
+## Relationship to Foundation
+
+The Foundation works to support the project, and the project has direct
+representation on the Foundation's board (the 5 project directors). Those
+directors are selected by the Leadership Council per the [bylaws].
+
+Those directors have 50% of the vote on any Board vote in the Foundation,
+regardless of the number of non-Project directors.
+
+The website has the [current project directors].
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
The website has the [current Project directors].
```
created_at: 2025-05-16T16:12:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar, see [Council term limits] for more details.
+
+[Council term limits]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#term-limits
+
+## Relationship to Foundation
+
+The Foundation works to support the project, and the project has direct
+representation on the Foundation's board (the 5 project directors). Those
+directors are selected by the Leadership Council per the [bylaws].
+
+Those directors have 50% of the vote on any Board vote in the Foundation,
+regardless of the number of non-Project directors.
+
+The website has the [current project directors].
+
+Please reach out whether you're just interested, have questions, or have concerns in:
+
+- Zulip, on [#foundation](https://rust-lang.zulipchat.com/#narrow/channel/335408-foundation)
+- To the Council (see above)
+- To one of the Project Directors (see member list above), recommending Zulip
+  DM as an initial point
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
- Zulip, on [#foundation](https://rust-lang.zulipchat.com/#narrow/channel/335408-foundation).
- To the Council (see above).
- To one of the Project Directors (see member list above), recommending Zulip
  DM as an initial point.
```
created_at: 2025-05-16T16:13:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar, see [Council term limits] for more details.
+
+[Council term limits]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#term-limits
+
+## Relationship to Foundation
+
+The Foundation works to support the project, and the project has direct
+representation on the Foundation's board (the 5 project directors). Those
+directors are selected by the Leadership Council per the [bylaws].
+
+Those directors have 50% of the vote on any Board vote in the Foundation,
+regardless of the number of non-Project directors.
+
+The website has the [current project directors].
+
+Please reach out whether you're just interested, have questions, or have concerns in:
+
+- Zulip, on [#foundation](https://rust-lang.zulipchat.com/#narrow/channel/335408-foundation)
+- To the Council (see above)
+- To one of the Project Directors (see member list above), recommending Zulip
+  DM as an initial point
+
+[current project directors]: https://www.rust-lang.org/governance/teams/launching-pad#team-foundation-board-project-directors
path: src/onboarding.md
user: login: traviscross
body: ```suggestion
[current Project directors]: https://www.rust-lang.org/governance/teams/launching-pad#team-foundation-board-project-directors
```
created_at: 2025-05-16T16:13:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
path: src/onboarding.md
user: login: traviscross
body: I wonder whether we should mention filing an issue on the `leadership-council` repository and nominating it.  While raising the matter on Zulip may generate some discussion, a nominated issue is how something formally makes its way into our inbox.

created_at: 2025-05-16T16:17:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council)
path: src/onboarding.md
user: login: Mark-Simulacrum
body: I think that's a great idea - can you suggest it?
created_at: 2025-05-16T16:24:59Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council).
+- Zulip DM, to your council representative (see
+  [council](https://www.rust-lang.org/governance/teams/leadership-council) for
+  which team each representative represents).
+
+Either can be a reasonable starting point, please select what you feel more
+comfortable with, though bias towards being public.
+
+Leadership Council positions are elected by the Project teams on a rotating
+calendar; see [Council term limits] for more details.
+
+[Council term limits]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#term-limits
path: src/onboarding.md
user: login: ehuss
body: When possible, I'd like to keep links to the "official" policy pages, instead of RFCs which are more of a historical snapshot of a decision.

```suggestion
[Council term limits]: governance/council.md#term-limits
```
created_at: 2025-05-17T22:22:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+# Onboarding to the Project
+
+This document is a starting point for a new team member (or a refresh for
+existing team members) on things that are useful to know as a member of the
+project, in particular in terms of where to raise concerns or get help.
+
+## Relationship to Council
+
+The Leadership Council formally takes positions on behalf of the Project when
+needed. All Rust project members are officially represented by approximately
+one member of the council (some teams parent up to two or more members).
+
+Generally speaking, any concerns you have that are either more widely
+applicable (i.e., not just your team) or you feel aren't being fully handled
+within your team can be escalated to the Council. Note that interpersonal
+concerns and/or code of conduct violations should always be directed to the
+Moderation team.
+
+Escalating to the Council can be done via:
+
+- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council).
path: src/onboarding.md
user: login: Mark-Simulacrum
body: ```suggestion
- GitHub, via a [new issue](https://github.com/rust-lang/leadership-council/issues/new/choose). This will get discussed at the regular council meeting (to which all project members are [invited](https://github.com/rust-lang/leadership-council/blob/main/procedures/meeting-observers.md)).
- Zulip, on [#council](https://rust-lang.zulipchat.com/#narrow/channel/392734-council).
```
created_at: 2025-05-22T01:54:46Z
author_association: MEMBER

PR comments:
user: login: rustbot
created_at: 2025-05-16T15:37:15Z
body: r? @ehuss

rustbot has assigned @ehuss.
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
author_association: COLLABORATOR
user: login: spastorino
created_at: 2025-05-17T14:47:21Z
body: What's the idea or plan here? what was the all hands session about? can we link the discussion?.
I guess the idea would be that we would provide more onboarding docs for the different parts of the project later?.
author_association: MEMBER
user: login: rylev
created_at: 2025-05-18T11:17:15Z
body: I personally know of two places where improving onboarding was actively was discussed:
* [Session on burnout](https://hackmd.io/@jyn514/SJXs9arZxe)
* [Session on Project and Foundation relations](https://hackmd.io/xGLUBwyARDez--36661Pxg)
author_association: MEMBER
user: login: Mark-Simulacrum
created_at: 2025-05-22T01:52:16Z
body: Thanks Ryan! Yes, this is coming out of the Foundation discussion for me (I didn't get a chance to attend the other session).

My primary goal is to get _something_ landed here, and it can be extended over time. I'm not sure whether this is the best form for it, but it seems like a reasonable-ish starting point and is net-new content as far as I know.


author_association: MEMBER