# Welcoming new members in a Rust team

### What is this?

When a new member joins a team a number of things happen. The new member might not be aware of all of them. It could be useful for them to receive a sort of "welcome email" explaining what's going to change.

Here's a proposal of an email template to be used by the person actualizing the membership (after the PR on `rust-lang/team` has been merged) to be sent to the new member to their github public email.

Each team can use and tailor the template according to their needs.

[Zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/244344-t-compiler.2Fcontrib-private/topic/Welcoming.20new.20members.20in.20t-compiler-contributors/near/404409050) (private thread).

### Open TODOs

- I am not sure who would want to use this (is the team membership an automated process or has someone a checklist of things to do?)
- A review of the wording and content is very welcome
- Perhaps worth being integrated with this [compiler-team#398](https://github.com/rust-lang/compiler-team/pull/398)

### The email template

<details>
<summary>For members of t-compiler-contributors</summary>

Hello $USERNAME,

welcome to the compiler-contributor team! Here's a brief summary of what will change for you. Take your time to look around and get familiar with these changes.

### Your public profile

Your Github profile will now appear on the governance page of the Rust website ([here](https://www.rust-lang.org/governance/teams/compiler#Compiler%20team%20contributors)).

### Your permissions

You will gain access to:
- [A private Zulip stream](https://rust-lang.zulipchat.com/#streams/244344/t-compiler.2Fcontrib-private/personal), where internal discussions happen or ideas in very draft state are shared.

You will gain permissions on the Github repository [rust-lang/rust](https://github.com/rust-lang/rust):
- You can now edit issues and pull requests (title and comments)
- You can now close issues and pull requests
- $ANYTHING_ELSE ?

### Your Github repositories

You will be subscribed and gain write access to the following Github repositories:
- [rust-lang/rustc_apfloat](https://github.com/rust-lang/rustc_apfloat)
- [rust-lang/ar_archive_writer](https://github.com/rust-lang/ar_archive_writer)
- [rust-lang/project-thir-unsafeck](https://github.com/rust-lang/project-thir-unsafeck)
- [rust-lang/odht](https://github.com/rust-lang/odht)
- [rust-lang/wg-incr-comp](https://github.com/rust-lang/wg-incr-comp)
- [rust-lang/project-rfc-2229](https://github.com/rust-lang/project-rfc-2229)
- [rust-lang/rustc-demangle](https://github.com/rust-lang/rustc-demangle)
- [rust-lang/surveys-private](https://github.com/rust-lang/surveys-private)
- [rust-lang/rfcs](https://github.com/rust-lang/rfcs)

Some of them are pretty quiet or obsolete, so don't worry about all of them.

Tip: Github automatically adds you as subscriber to every repo you get write permission too. You can disable this in the settings ([here](https://github.com/settings/notifications)).

As a compiler contributor you can now use `bors` on the repository [rust-lang/rust](https://github.com/rust-lang/rust). Both `try` builds and `r+`. See the documentation [here](https://rustc-dev-guide.rust-lang.org/compiler-team.html#team-membership).

Tip: some baseline rules around bors permissions are: don't do a `try` build unless you have done a check for malicious code first and don't `r+` unless you are reasonably confident that you can effectively review the code in question.

### Communication

If this is your first team membership, you will also be subscribed to the `[e-mail]` mailing list. See [this file](https://github.com/rust-lang/team/blob/HEAD/teams/all.toml) to check how subscriptions work.

It's a very low-volume mailing list (maybe a few emails per year), it's a way to communicate things to all contributors. You will not receive spam from this address.

Please let us know if you're not interested and we will unsubscribe you.

</details>

---

<details>
<summary>other team?</summary>

Feel free to copy&paste and adapt!
</details>