Add a bit more detail about AI usage in general

Author: thisisnic

CONTRIBUTING.md

@@ -64,6 +64,11 @@ publicly on the [arrow-dev mailing-list](https://mail-archives.apache.org/mod_mb
 
 You can also ask on the mailing-list, see above.
 
+## Are you using AI coding tools?
+
+Please review our [AI-generated code guidance](https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code)
+before submitting AI-assisted contributions.
+
 ## Further information
 
 Please read our [development documentation](https://arrow.apache.org/docs/developers/index.html)

README.md

@@ -91,6 +91,9 @@ on git main.
 
 Please read our latest [project contribution guide][4].
 
+If you are using AI coding tools, please review our
+[AI-generated code guidance][7].
+
 ## Getting involved
 
 Even if you do not plan to contribute to Apache Arrow itself or Arrow
@@ -114,3 +117,4 @@ We use [AWS][6] for some of the required infrastructure for the project.
 [4]: https://arrow.apache.org/docs/dev/developers/index.html
 [5]: https://runs-on.com/
 [6]: https://aws.amazon.com/
+[7]: https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code

docs/source/developers/overview.rst

@@ -179,6 +179,9 @@ the following:
 * Watch for AI's tendency to generate overly verbose comments, unnecessary
   test cases, and incorrect fixes
 * Break down large PRs into smaller ones to make review easier
+* Avoid pinging maintainers to request reviews; most maintainers have
+  limited time, and we will review PRs as bandwidth allows. AI agents
+  should never tag or ping maintainers.
 
 PR authors are also responsible for disclosing any copyrighted materials in
 submitted contributions. See the `ASF's guidance on AI-generated code