From 20017a249c696080f7344e45ae680e1d1cd44c4e Mon Sep 17 00:00:00 2001
From: Eric Huss <eric@huss.org>
Date: Wed, 23 Mar 2022 13:53:40 -0700
Subject: [PATCH] Add a notice about review capacity.

---
 .github/PULL_REQUEST_TEMPLATE.md     |  5 +++++
 CONTRIBUTING.md                      |  5 +++++
 src/doc/contrib/src/process/index.md | 12 ++++++++----
 3 files changed, 18 insertions(+), 4 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 25faebe75..141ac5ed4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,5 +1,10 @@
 <!-- homu-ignore:start -->
 <!--
+NOTICE: Due to limited review capacity, the Cargo team is not accepting new
+features or major changes at this time. Please consult with the team before
+opening a new PR. Only issues that have been explicitly marked as accepted
+will be reviewed.
+
 Thanks for submitting a pull request 🎉! Here are some tips for you:
 
 * If this is your first contribution, read "Cargo Contribution Guide":
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3233e481c..88ffbd3d0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -11,6 +11,11 @@ you [file an issue] or start a thread on the [internals forum] before submitting
 a pull request. Please read [the process] of how features and bugs are managed
 in Cargo.
 
+**NOTICE: Due to limited review capacity, the Cargo team is not accepting new
+features or major changes at this time. Please consult with the team before
+opening a new PR. Only issues that have been explicitly marked as accepted
+will be reviewed.**
+
 [internals forum]: https://internals.rust-lang.org/c/tools-and-infrastructure/cargo
 [file an issue]: https://github.com/rust-lang/cargo/issues
 [the process]: https://doc.crates.io/contrib/process/index.html
diff --git a/src/doc/contrib/src/process/index.md b/src/doc/contrib/src/process/index.md
index bb40bf872..7fac60592 100644
--- a/src/doc/contrib/src/process/index.md
+++ b/src/doc/contrib/src/process/index.md
@@ -6,6 +6,13 @@ a part of that process.
 See the [Working on Cargo] chapter for an overview of the contribution
 process.
 
+Please read the guidelines below before working on an issue or new feature.
+
+**Due to limited review capacity, the Cargo team is not accepting new features
+or major changes at this time. Please consult with the team before opening a
+new PR. Only issues that have been explicitly marked as accepted will be
+reviewed.**
+
 [Working on Cargo]: working-on-cargo.md
 
 ## Cargo team
@@ -18,10 +25,6 @@ participating, feel free to contact us on [Zulip].
 
 ## Roadmap
 
-The Cargo team typically establishes a roadmap each year that sets which areas
-they will be focusing on. This is usually posted on the Inside Rust Blog (such
-as [the 2020 roadmap]).
-
 The [Roadmap Project Board] is used for tracking major initiatives. This gives
 an overview of the things the team is interested in and thinking about.
 
@@ -76,6 +79,7 @@ Most of them require some design work, which can be difficult. Check out the
 Cargo follows the Rust model of evolution. Major features usually go through
 an [RFC process]. Therefore, before opening a feature request issue create a
 Pre-RFC thread on the [internals][irlo] forum to get preliminary feedback.
+
 Implementing a feature as a [custom subcommand][subcommands] is encouraged as
 it helps demonstrate the demand for the functionality and is a great way to
 deliver a working solution faster as it can iterate outside of Cargo's release