Note spam prevention requirements

Users must join repo-discuss before creating issues or code reviews.

Also note the dev-contributing doc in SUBMITTING_PATCHES and fix the
outdated bugs.chromium.org link.

Release-Notes: skip
Change-Id: I17ee5d5043a8370d33b14103cb3d8ed32d45ec37
diff --git a/README.md b/README.md
index 30c6b3d..41353d1 100644
--- a/README.md
+++ b/README.md
@@ -28,13 +28,25 @@
 
 ## Reporting bugs
 
-Please report bugs on the [issue tracker](https://bugs.chromium.org/p/gerrit/issues/list).
+Please report bugs on the
+[issue tracker](https://issues.gerritcodereview.com/issues?q=status:open%20componentid:1370072).
+
+Due to spam abuse, membership in the
+[repo-discuss](http://groups.google.com/group/repo-discuss) Google Group is
+required in order to create issues. See the
+[announcement](https://www.gerritcodereview.com/2025-06-05-community-managers-minutes.html#reducing-spam-on-both-issue-tracker-and-gerritgooglesource)
+for more info.
 
 ## Contribute
 
 Gerrit is the work of hundreds of contributors. We appreciate your help!
 
-Please read the [contribution guidelines](https://gerrit.googlesource.com/gerrit/+/master/SUBMITTING_PATCHES).
+Please read the [contribution guidelines](SUBMITTING_PATCHES).
+
+Due to spam abuse, membership in the
+[repo-discuss](http://groups.google.com/group/repo-discuss) Google Group is
+required in order to create Gerrit changes on the
+[gerrit-review](https://gerrit-review.googlesource.com) Gerrit server.
 
 Note that we do not accept Pull Requests via the GitHub mirror.
 
diff --git a/SUBMITTING_PATCHES b/SUBMITTING_PATCHES
index 8a5b785..6e22345 100644
--- a/SUBMITTING_PATCHES
+++ b/SUBMITTING_PATCHES
@@ -8,6 +8,8 @@
 
    git push https://gerrit.googlesource.com/gerrit HEAD:refs/for/master
 
+See https://gerrit-review.googlesource.com/Documentation/dev-contributing.html
+for full details.
 
 Long Version:
 
@@ -62,6 +64,11 @@
 
 (3) Sending your patches.
 
+Due to spam abuse, membership in the http://groups.google.com/group/repo-discuss
+Google Group is required in order to create Gerrit changes on the
+https://gerrit-review.googlesource.com Gerrit server. Ensure you've done that
+before attempting git push.
+
 Do not email your patches to anyone.
 
 Instead, login to the Gerrit Code Review tool at: