dealing with PR review latency

[pnkfelix]

Meeting proposal info

• Title: Dealing with PR review latency
• Type: it's complicated

Summary

Contributors get frustrated when their PR's don't get reviewed.

Our current handling of reviews doesn't necessarily distribute the review labor in a manner that makes the most sense

We should have a meeting to talk about what our overall goals are here, and what mechanisms we might put in place to improve the over experience for our contributors.

About this issue

This issue corresponds to a meeting proposal for the compiler team
steering meeting. It corresponds to a possible topic of
discussion. You can read more about the steering meeting procedure
here.

Comment policy

These issues are meant to be used as an "announcements channel"
regarding the proposal, and not as a place to discuss the technical
details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision.
In the meantime, if you have questions or ideas, ping the proposers
on Zulip (or elsewhere).

[pnkfelix]

As announced on https://blog.rust-lang.org/inside-rust/2023/02/10/compiler-team-feb-steering-cycle.html, we'll be having this meeting on 2023-02-17

@rustbot label: +meeting-scheduled

[pnkfelix]

We met about this on 2023-02-17

This doc drove the meeting: https://hackmd.io/1xr2fB7VS22F_IqlbR_Zrw

The public zulip archive serves as the official meeting record: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bsteering.5D.202023-02-17.20review.20latency.20compiler-team.23589/near/328486305