thisisnic commented on code in PR #48952:
URL: https://github.com/apache/arrow/pull/48952#discussion_r2721211635


##########
docs/source/developers/overview.rst:
##########
@@ -146,6 +146,43 @@ will merge the pull request. This is done with a
   description, a link back to the pull request, and attribution to the 
contributor
   and any co-authors.
 
+.. _ai-generated-code:
+
+AI-generated code
++++++++++++++++++
+
+We recognise that AI coding assistants are now a regular part of many
+developers' workflows and can improve productivity. Thoughtful use of these
+tools can be beneficial, but AI-generated PRs can sometimes lead to
+undesirable additional maintainer burden. PRs that appear to be fully
+generated by AI with little to no engagement from the author may be closed
+without further review.
+
+Human-generated mistakes tend to be easier to spot and reason about, and
+code review often feels like a collaborative learning experience that
+benefits both submitter and reviewer. When a PR appears to have been
+generated without much engagement from the submitter, reviewers with access
+to AI tools could more efficiently generate the code directly.
+
+We are not opposed to the use of AI tools in generating PRs, but recommend
+the following:
+
+* Only take on a PR if you are able to debug and own the changes yourself -
+  review all generated code to understand every detail
+* Match the style and conventions used in the rest of the codebase, including
+  PR titles and descriptions
+* Be upfront about AI usage and summarise what was AI-generated
+* If there are parts you don't fully understand, leave comments on your own PR
+  explaining what steps you took to verify correctness
+* 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
+
+PR authors are also responsible for disclosing any copyrighted materials in
+submitted contributions. See the `ASF's guidance on AI-generated code

Review Comment:
   I *think* we're good, as we already have a link to this page in the template 
already, and it covers quite a few other topics too.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to