Document triagebot review queue tracking

src/SUMMARY.md

@@ -15,7 +15,7 @@
     - [Agenda Generator](./triagebot/agenda.md)
     - [Issue Assignment](./triagebot/issue-assignment.md)
     - [PR Assignment](./triagebot/pr-assignment.md)
-    - [Tracking PR assignment](./triagebot/pr-assignment-tracking.md)
+      - [Review queue tracking](triagebot/review-queue-tracking.md)
     - [Autolabels](./triagebot/autolabels.md)
     - [Behind Upstream](./triagebot/behind-upstream.md)
     - [Canonicalize Issue Links](./triagebot/canonicalize-issue-links.md)

src/triagebot/pr-assignment.md

@@ -3,7 +3,9 @@
 Triagebot handles automatic and manual assignment of GitHub PRs.
 It also handles welcoming new users when they post a PR.
 
-Rust contributors can track and manage their own work queue using the Zulipchat integration. See [Tracking PR assignment](/triagebot/pr-assignment-tracking.md).
+Contributors to the `rust-lang/rust` repository can track and manage their own work queue using Zulip integration. See [Review queue tracking](review-queue-tracking.md).
+
+You can check which pull requests in the `rust-lang` organization are assigned to you at this [GitHub URL](https://github.com/pulls?q=org%3Arust-lang+is%3Aopen+is%3Apr+assignee%3A%40me+archived%3Afalse).
 
 ## Usage
 
@@ -85,6 +87,8 @@ If a reviewer wants to temporarily prevent themselves from being assigned (autom
 users_on_vacation = ["jyn514", "ChrisDenton"]
 ```
 
+On `rust-lang/rust`, you can also configure vacation using [Zulip integration](review-queue-tracking.md#usage).
+
 ### Additional new PR trigger options
 
 Triagebot will also post a welcome message to the user.

src/triagebot/review-queue-tracking.md

@@ -0,0 +1,61 @@
+# Review queue tracking
+
+Triagebot supports more advanced tracking of reviewers' workload in the `rust-lang/rust` repository. It tracks how many "relevant" pull requests are assigned to each reviewer, and allows reviewers to configure maximum capacity of such PRs, and also if they want to be automatically assigned or not.
+
+This page describes how the review queue works and how you can interact with `triagebot` on Zulip to configure and examine the review queue.
+
+## Configuration
+
+To enable review queue tracking for a repository, include `[pr-tracking]` table in its `triagebot.toml`.
+
+To take the review queue into account when assigning reviewers on PRs, add a `[assign.review_prefs]` table to `triagebot.toml`.
+
+> Note that this functionality currently only works for the `rust-lang/rust` repository (it is hardcoded in `triagebot`). Enabling it for more repositories requires additional design and implementation work.
+
+## Review queue design
+
+The review queue remembers how many "relevant" `rust-lang/rust` PRs are assigned to each reviewer at any given point in time.
+Currently, the heuristic for what makes a PR "relevant" works as follows:
+- The PR must not be blocked (it must not have the `S-blocked` or `S-inactive` labels).
+- The PR must not be a rollup.
+- The PR must be waiting for a reviewer (must have the `S-waiting-on-review` label).
+- The PR must be assigned to someone else than the PR author.
+- The PR must be open and not a draft.
+
+If a PR passes all these checks and it is assigned to reviewer `R`, it will be considered to be in `R`'s review queue.
+
+See the implementation of the [`waits_for_a_review`](https://github.com/rust-lang/triagebot/blob/7044e5449aaf29eea939bc7db81c63b7c872b9b8/src/handlers/pr_tracking.rs#L277-L304) function in triagebot for more details.
+
+## Review preferences
+
+Reviewers can configure *review preferences* that are taken into account when determining who to assign on a PR:
+- Review queue capacity (`C`) --- if the number of PRs in your review queue is at (or above) `C`, `triagebot` will not assign new pull requests to you.
+- Rotation mode (`on` or `off` rotation) --- if you set your rotation mode to be `off`, `triagebot` will not assign new pull requests to you.
+  - This is an alternative to setting yourself as being ["on vacation"](pr-assignment.md#vacation) which does not require sending a pull request to modify the `triagebot.toml` file. `triagebot` takes both `users_on_vacation` in `triagebot.toml` and the rotation mode into account; if you are marked as being on vacation in either of them, it will not assign PRs to you.
+
+Note that the review preferences only affect assignment based on adhoc groups or teams. If someone directly requests your review (`r? <user>`), triagebot will currently always assign you. If you are off rotation or at your maximum review capacity, triagebot will send a comment to the PR where you were directly assigned to let the PR author know that you might not be available for a timely review.
+
+## Usage
+
+You can examine your review queue and configure your review preferences by sending a DM (Direct Message) to the `triagebot` bot account on the [Zulip chat](../platforms/zulip.md). You can open a DM session with the `triagebot` bot by clicking on [this link](https://rust-lang.zulipchat.com/#narrow/dm/261224-triagebot) (requires Zulip login).
+
+You can send a message with one of these commands to `triagebot`:
+
+- `work help` --- Show the available commands.
+- `work show` --- Show the contents of your review queue (in the `rust-lang/rust` repository) and your review preferences.
+- `work set-pr-limit <number>|unlimited` --- Set your review capacity to `<number>` or remove the capacity limit (`unlimited`).
+- `work set-rotation-mode off|on` --- Set your rotation mode to be `on` or `off`.
+
+You can also run the above commands on behalf of other GitHub users with the following message:
+
+```
+as <github-username> <command>
+# e.g.
+as MyFavouriteGitHubUser work show
+```
+
+`triagebot` will notify the user that you have executed a command on their behalf. Note that this functionality is intended for rare occasions or debugging, please do not use it often.
+
+## Implementation
+
+See [`src/handlers/pr_tracking.rs`](https://github.com/rust-lang/triagebot/blob/HEAD/src/handlers/pr_tracking.rs).