Adopting an AI policy for sphinx-doc #14463
Closed
jdillard
started this conversation in
Feature requests and ideas
Replies: 3 comments 8 replies
|
I think, just taking over numpy's policy is fine. |
1 reply
|
Not sure where to bring up misbehaving bots, but this bot closed it's own PR, then re-opened the same PR. I closed that PR, but if it re-opens it again, than the DDoS type behavior should be banned. |
7 replies
|
Closing this since we have a policy in place and a violation label. Thanks everyone! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Given that there is more and more AI usage in terms of issues and PRs, it has been suggested by @timhoffm that it would be a good idea to adopt an official AI policy. So I figured I would start a discussion to get others input.
This isn't my wheel house, but I put together a list of examples below for inspiration to help get the discussion started.
Python ecosystem examples
Some example of what other Python projects have done regarding AI policies.
CPython
https://devguide.python.org/getting-started/ai-tools/
Quick Summary:
NumPy
A fairly comprehensive policy that covers more ground and worth looking at.
https://numpy.org/devdocs/dev/ai_policy.html
SymPy
Similar to NumPy, just kind of showcasing that there is somewhat of a convergance.
https://docs.sympy.org/dev/contributing/ai-generated-code-policy.html
Other examples
@melissawm put together this awesome repo https://github.com/melissawm/open-source-ai-contribution-policies
All reactions