---
# System prepended metadata

title: Volunteers for `lang-interest`

---

---
title: "Volunteers for `lang-interest`"
date: 2025-06-20
url: https://hackmd.io/AL9eYfpHSISE21VAYCdLrw
---

# Volunteers for `lang-interest`

## Background

Sometimes, particularly on stabilizations, the lang team would like to have more eyes on certain PRs.  While we do try to ping those we can think of that have knowledge and interest in the item, often that still leaves only a handful of people that have been specifically notified about what might be a consequential stabilization or other matter.

To help with this, we're creating a marker team -- a ping group -- called `lang-interest`.  We're inviting people to join this group if those people want to be notified about matters where the lang team would like more eyes on something and are willing to help us look for errors.

## Rules

The rules for membership in this group are as follows:

- You promise to not complain about getting pinged.  You've asked for it.
- You help us look for errors.

While we're currently intending to add anyone that asks who is already in `team/people` (and of the people that aren't, anyone whose contributions we recognize), we may adjust our requirements over time as we learn things, and we may do some periodic housekeeping, so note that membership on this marker team is at the continued discretion of the lang team.

## Looking for errors

On a stabilization, we want people to have a look and to confirm for us that what's proposed:

- Works in the way described in the stabilization report.
- Aligns with prior lang FCPs.
- Matches the behavior specified in the accompanying Reference PR.
- Fully specifies all aspects of the stabilized behavior.
- Does not stabilize something unstated or unconsidered.
- Has adequate test coverage of all behaviors being stabilized.
- Has a mature and robust implementation in the compiler.
- Has pinged every person that has worked on this and might have important context.
- Does not have unforeseen effects on our tools such as rustfmt and rust-analyzer.

If you find where one of those things isn't true, you may have found a bug in the stabilization, and we want to hear about it so we can investigate.  Similarly, if you have a close look and everything looks in order to you, we appreciate hearing your confirmation of that also.

On something that's not a stabilization, we may also ping this group to seek broader input on some question.

## How to join -- already in `team/people`

If you're already in [team/people](https://github.com/rust-lang/team/tree/master/people), simply list yourself below.  For our context, and as we may later add more specialized ping groups, please list in parentheses any areas of special interest or special expertise that you have (e.g. "opsem", "LLVM", "lints", "macros", etc.).

- `yoshuawuyts` ("async", "concurrency", "effects", "wasm")
- `veykril` ("rust-analyzer support", "macros")
- `obi1kenobi` ("semver")
- `jieyouxu` ("lints", "parser", "attributes", "cli", "test coverage", "test infra")
- `fee1-dead` ("effects", "syntax", "lints", "test coverage", "opsem")
- `lcnr` ("types")
- `BoxyUwU` ("types", "const-generics")
- `Darksonn` ("async", "opsem", "ABI", "rfl related")
- `spastorino` ("types")
- `your-github-username` ("interest1", "interest2")

## How to join -- not in `team/people`

If you're not yet in `team/people`, we'll need a bit more information.  Add a section for yourself following the template below (see the [team repo](https://github.com/rust-lang/team/) for questions about this format).

To start with, we're likely to first add people whose names we recognize from earlier ongoing contributions.  This is just so that we don't burden the `team` repo too much.  If we don't add you right away, don't worry.  Just keep contributing, and we'll try to add you later when we're more familiar with your contributions.

### `mejrs`

- `mejrs` ("attributes", "diagnostics", "diagnostic_namespace")

```
name = "Bruno Kolenbrander"
github = "mejrs"
github-id = 59372212
zulip-id = 433532
email = "brunokolenbrander@hotmail.com"
```

### `dianne`

- `dianne` ("diagnostics", "effects", "patterns", "types")

```
name = "Dianne Wagner"
github = "dianne"
github-id = 29509279
zulip-id = 759061
email = "diannes.gm@gmail.com"
```

### `your-github-username`

- `your-github-username` ("interest1", "interest2")

```
name = "Your Name"
github = "your-github-username"
github-id = 1234
zulip-id = 1234
email = "your.email@example.com"
```
