adding an AI Tool Policy (#1063)

* adding an AI Tool Policy

* erasing word

* Update AIToolPolicy.md

Co-authored-by: Yagiz Nizipli <yagiz@nizipli.com>

* Update .github/ISSUE_TEMPLATE/1-bug-report.yml

Co-authored-by: Yagiz Nizipli <yagiz@nizipli.com>

* Update README.md

Co-authored-by: Yagiz Nizipli <yagiz@nizipli.com>

* rename

---------

Co-authored-by: Yagiz Nizipli <yagiz@nizipli.com>

Author: lemire

.github/ISSUE_TEMPLATE/1-bug-report.yml

@@ -7,6 +7,8 @@ body:
         Thank you for reporting an issue.
 
         Please fill in as much of the following form as you're able.
+
+        Contributors are encouraged to read our AI Usage Policy, see AI_USAGE_POLICY.md.
   - type: input
     attributes:
       label: Version

.github/ISSUE_TEMPLATE/2-feature-request.yml

@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thank you for suggesting an idea to make Node.js better.
+        Thank you for suggesting an idea to make ada better.
 
         Please fill in as much of the following form as you're able.
   - type: textarea

AI_USAGE_POLICY.md

@@ -0,0 +1,50 @@
+# AI Usage Policy
+
+Contributors can use whatever tools they would like to
+craft their contributions, but there must be a **human in the loop**.
+**Contributors must read and review all LLM-generated code or text before they
+ask other project members to review it.** The contributor is always the author
+and is fully accountable for their contributions. Contributors should be
+sufficiently confident that the contribution is high enough quality that asking
+for a review is a good use of scarce maintainer time, and they should be **able
+to answer questions about their work** during review.
+
+We expect that new contributors will be less confident in their contributions,
+and our guidance to them is to **start with small contributions** that they can
+fully understand to build confidence. We aspire to be a welcoming community
+that helps new contributors grow their expertise, but learning involves taking
+small steps, getting feedback, and iterating. Passing maintainer feedback to an
+LLM doesn't help anyone grow, and does not sustain our community.
+
+This policy includes, but is not limited to, the following kinds of
+contributions:
+
+- Code, usually in the form of a pull request
+- Issues or security vulnerabilities
+- Comments and feedback on pull requests
+
+## Extractive Contributions
+
+The reason for our "human-in-the-loop" contribution policy is that processing
+patches, PRs, RFCs, and comments is not free -- it takes a lot of
+maintainer time and energy to review those contributions! Sending the
+unreviewed output of an LLM to open source project maintainers *extracts* work
+from them in the form of design and code review, so we call this kind of
+contribution an "extractive contribution".
+
+
+## Copyright
+
+Artificial intelligence systems raise many questions around copyright that have
+yet to be answered. Our policy on AI tools is similar to our copyright policy:
+Contributors are responsible for ensuring that they have the right to
+contribute code under the terms of our license, typically meaning that either
+they, their employer, or their collaborators hold the copyright. Using AI tools
+to regenerate copyrighted material does not remove the copyright, and
+contributors are responsible for ensuring that such material does not appear in
+their contributions. Contributions found to violate this policy will be removed
+just like any other offending contribution.
+
+## Reference
+
+- [LLVM AI Tool Use Policy](https://discourse.llvm.org/t/rfc-llvm-ai-tool-policy-human-in-the-loop/89159)

README.md

@@ -301,6 +301,9 @@ CMake project, after having installed ada on your system.
 
 ## Contributing
 
+Contributors are encouraged to read our [AI Tool Policy](AI_USAGE_POLICY.md).
+
+
 ### Building
 
 Ada uses cmake as a build system, but also supports Bazel. It's recommended you to run the following