---
# System prepended metadata

title: Meta WG - Check-ins
tags: [' rustc', meta]

---

---
tags: meta, rustc
---

# Meta WG - Check-ins

## Current

## 2020-06-04

- Merged the MCP RFC
- Proposed meeting and elaborated some on the idea of "areas" of the compiler
- Renamed ICE Breaker groups to notify groups
- Working on creating a Windows notification group -- will likely pull the trigger soon

## 2020-04-16

* Created [RFC 2904](https://github.com/rust-lang/rfcs/pull/2904), for the major change process
* Thinking about registering "areas" of the compiler, as an evolution of the "experts map":
    * each would have a registered zulip stream
    * also some list of experts / maintainers you can go to for help, or feedback on MCPs, etc
    * would replace e.g. llvm, mir-opt, and a number of existing wgs
* Also thinking about a "map" that will help steer contributors. So you want to do X...?
    * X = fix a bug, rustbot claim, write a PR
    * X = add a compiler flag, draft a description etc
    * X = big refactoring, create an MCP
    * etc

## 2020-04-02

* Create major_change issue template [#232](https://github.com/rust-lang/compiler-team/pull/232)
* Hoping to move forward shortly with the [Major Change Proposal RFC](https://hackmd.io/VhVSTwgiTcmEslbpC7qCOQ) --
    * process is intentionally quite lightweight
    * to do this right, it'll also be a change for all of us to identify PRs that are making major changes and ensure they go through the process
* After this, thinking about creating a document to help guide people through processes:
    * "So you'd like to do X?"
    * In particular, the process around adding and stabilizing command line flags seems to be coming up a lot

## 2020-03-05

- [Cleanup ICE-breakers group was announced](https://blog.rust-lang.org/inside-rust/2020/02/06/Cleanup-Crew-ICE-breakers.html)

So remember that when we need more information about an issue, like:

> a minimal, standalone example that shows the problem
> links to duplicates or related bugs
> if the bug is a regression (something that used to work, but no longer does), then a bisection to the PR or nightly that caused the regression

we can just do `@rustbot ping icebreakers-cleanup-crew` and have some people helping us.

- [We had a meeting to define a more focused and efficient triaging work](https://rust-lang.zulipchat.com/#narrow/stream/185694-t-compiler.2Fwg-meta/topic/charter.20for.20focused.20and.20efficient.20triage)

This was leadup to the design meeting last week. General conclusion was that we should try to create a working group for triage, and spastorino and pnkfelix started talking about that this week.

- [Major changes template PR is waiting on team](https://github.com/rust-lang/compiler-team/pull/232)

This has stalled out a bit, we need to talk through how to finalize the process and ensure that things are actually moving forward.

- [Diagnostic ICE breakers group PR is waiting on author](https://github.com/rust-lang/rustc-guide/pull/524)

We are starting to have a "Standard checklist" for new ICE-breakers groups! 

- [Draft of Add a "Compile-time Function Evaluation" working group](https://github.com/rust-lang/compiler-team/pull/201)

In general, we probably want to think about the working groups we'll be pushing on this year, and also a bit about different "categories" of working groups:

* task-focused, high priority groups (nll, async-await, maybe traits etc)
* slow progress over time groups (const-eval, const generics?)
* people who own a general code area or are pushing on a endless treadmill (diagnostics, triage)

- [We should document what team membership means, responsibilities, and how to adjust](https://github.com/rust-lang/compiler-team/issues/248)

This is mostly taking details from the compiler contributors RFC and putting them in a central place (forge).