scikit-learn · betatim · Aug 5, 2025 · Jul 23, 2025 · Jul 25, 2025 · Jul 28, 2025
diff --git a/doc/developers/contributing.rst b/doc/developers/contributing.rst
@@ -102,6 +102,8 @@ and follows the decision-making process outlined in :ref:`governance`.
   Look for issues marked "help wanted" or similar. Helping these projects may help
   scikit-learn too. See also :ref:`related_projects`.
 
+.. _automated_contributions_policy:
+
 Automated Contributions Policy
 ==============================
 
@@ -110,7 +112,17 @@ fully-automated tools. Maintainers reserve the right, at their sole discretion,
 to close such submissions and to block any account responsible for them.
 
 Ideally, contributions should follow from a human-to-human discussion in the
-form of an issue.
+form of an issue. In particular, please do not paste AI generated text in the
+description of issues, PRs or in comments as it makes it significantly harder for
+reviewers to assess the relevance of your contribution and the potential value it
+brings to future end-users of the library. Note that it's fine to use AI tools
+to proofread or improve your draft text if you are not a native English speaker,
+but reviewers are not interested in unknowingly interacting back and forth with
+automated chatbots that fundamentally do not care about the value of our open
+source project.
+
+Please self review all code or documentation changes made by AI tools before
+submitting them under your name.
 
 Submitting a bug report or a feature request
 ============================================

diff --git a/doc/faq.rst b/doc/faq.rst
@@ -300,6 +300,33 @@ reviewers are busy. We ask for your understanding and request that you
 not close your pull request or discontinue your work solely because of
 this reason.
 
+What does the "spam" label for issues or pull requests mean?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The "spam" label is an indication for reviewers that the issue or
+pull request may not have received sufficient effort or preparation
+from the author for a productive review. The maintainers are using this label
+as a way to deal with the increase of low value PRs and issues.
+
+If an issue or PR was labeled as spam and simultaneously closed, the decision
+is final. A common reason for this happening is when people open a PR for an
+issue that is still under discussion. Please wait for the discussion to
+converge before opening a PR.
+
+If your issue or PR was labeled as spam and not closed the following steps
+can increase the chances of the label being removed:
+
+- follow the :ref:`contribution guidelines <contributing>` and use the provided
+  issue and pull request templates
+- improve the formatting and grammar of the text of the title and description of the issue/PR
+- improve the diff to remove noise and unrelated changes
+- improve the issue or pull request title to be more descriptive
+- self review your code, especially if :ref:`you used AI tools to generate it <automated_contributions_policy>`
+- refrain from opening PRs that paraphrase existing code or documentation
+  without actually improving the correctness, clarity or educational
+  value of the existing code or documentation.
+
+
 .. _new_algorithms_inclusion_criteria:
 
 What are the inclusion criteria for new algorithms?