Skip to content

[META] AI policy #7914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ShaharNaveh wants to merge 6 commits into
base: main
Choose a base branch
from
Open

[META] AI policy #7914

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b4e66d1
Add `CONTRIBUTING.md` and link it in the readme
ShaharNaveh May 18, 2026
1ab9206
Add TBD PR template
ShaharNaveh May 18, 2026
96a895c
Merge remote-tracking branch 'upstream/main' into ai-policy
ShaharNaveh May 19, 2026
0daf0f7
Merge `DEVELOPMENT.md` -> `CONTRIBUTING.md`
ShaharNaveh May 19, 2026
5c51bfd
Revise `PULL_REQUEST_TEMPLATE.md`
ShaharNaveh May 19, 2026
df31b9d
Have checkboxes
ShaharNaveh May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
<!--
Thanks for your contribution!
-->

- [ ] Closes #xxxx <!-- Replace xxxx with the GitHub issue number -->
- [ ] This PR follows our [AI policy](https://github.com/RustPython/.github/blob/main/AI_POLICY.md)
Comment thread
fanninpm marked this conversation as resolved.

## Summary
<!-- What's the purpose of the change? What does it do, and why? -->

26 changes: 25 additions & 1 deletion DEVELOPMENT.md → CONTRIBUTING.md
View file
Open in desktop
Copy link
Copy Markdown
Contributor Author

@ShaharNaveh ShaharNaveh May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added CONTRIBUTING.md as it's standardized https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors#adding-a-contributingmd-file

Should we merge DEVELOPMENT. md into it?

feels redundant two have two separate files for the same thing, no?

Copy link
Copy Markdown
Member

@youknowone youknowone May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having both CONTRIBUTING and DEVELOPMENT doesn't make sense. yeah, mv DEVELOPMENT and patch it please.

Copy link
Copy Markdown
Contributor Author

@ShaharNaveh ShaharNaveh May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The DEVELOPMENT. md is pretty outdated, I'll refresh it in a follow PR. I'd rather keep this PR small

Original file line number Diff line number Diff line change
@@ -1,4 +1,28 @@
# RustPython Development Guide and Tips
# Contributing to RustPython

Contributions are more than welcome, and in many cases we are happy to guide
contributors through PRs or on [**Discord**](https://discord.gg/vru8NypEhv).

## Finding ways to help

We label issues that would be good for a first time contributor as [`good first issue`](https://github.com/RustPython/RustPython/issues?q=label%3A%22good+first+issue%22+is%3Aissue+is%3Aopen+).
Also checkout the [issue tracker](https://github.com/RustPython/RustPython/issues) for all open issues.

You can enhance CPython compatibility by increasing our unittest coverage, you can see [This pinned issue](https://github.com/RustPython/RustPython/issues/6839) to see which libs and tests need be updated to our current supported python version.

Another approach is to checkout the source code: builtin functions and object
methods are often the simplest and easiest way to contribute.

You can also simply run `python -I scripts/whats_left.py` to assist in finding any unimplemented method.

## Use of AI

We **require all use of AI in contributions to follow our
[AI Policy](https://github.com/RustPython/.github/blob/main/AI_POLICY.md)**.
Comment on lines +20 to +21
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the AI policy document exists and is accessible

# Check if the AI policy file exists in the .github repository
gh api repos/RustPython/.github/contents/AI_POLICY.md --jq '.name' 2>/dev/null || echo "AI_POLICY.md not found in RustPython/.github repository"

# Also check the raw content availability
curl -s -o /dev/null -w "%{http_code}" https://raw.githubusercontent.com/RustPython/.github/main/AI_POLICY.md

Repository: RustPython/RustPython

Length of output: 251

The referenced AI policy document does not exist and must be created before merging.

The contribution guidelines require contributors to follow an AI policy at https://github.com/RustPython/.github/blob/main/AI_POLICY.md, but this document is not currently available in the RustPython/.github repository. The policy cannot be enforced or followed by contributors without this document. Either create the AI_POLICY.md file in the RustPython/.github repository or update the reference to point to an existing document.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 20 - 21, CONTRIBUTING.md references a
non-existent AI policy at
https://github.com/RustPython/.github/blob/main/AI_POLICY.md; add the missing
AI_POLICY.md to the RustPython/.github repository (or update the link in
CONTRIBUTING.md) so the referenced policy exists. Create a clear AI_POLICY.md
file containing the project's AI usage rules and place it in the .github
repository root, then verify CONTRIBUTING.md's link points to that new file (or
change the link to an existing policy file) to ensure the guideline resolves
correctly.


If your contribution does not follow the policy, it will be closed.

## RustPython Development Guide and Tips

RustPython attracts developers with interest and experience in Rust, Python,
or WebAssembly. Whether you are familiar with Rust, Python, or
Expand Down
20 changes: 3 additions & 17 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,24 +229,10 @@ For a high level overview of the components, see the [architecture](architecture

## Contributing

Contributions are more than welcome, and in many cases we are happy to guide
contributors through PRs or on Discord. Please refer to the
[development guide](DEVELOPMENT.md) as well for tips on developments.
Contributions are welcome and highly appreciated. To get started, check out the
[**contributing guidelines**](CONTRIBUTING.md).

With that in mind, please note this project is maintained by volunteers, some of
the best ways to get started are below:

Most tasks are listed in the
[issue tracker](https://github.com/RustPython/RustPython/issues). Check issues
labeled with [good first issue](https://github.com/RustPython/RustPython/issues?q=label%3A%22good+first+issue%22+is%3Aissue+is%3Aopen+) if you wish to start coding.

To enhance CPython compatibility, try to increase unittest coverage by checking this article: [How to contribute to RustPython by CPython unittest](https://rustpython.github.io/guideline/2020/04/04/how-to-contribute-by-cpython-unittest.html)

Another approach is to checkout the source code: builtin functions and object
methods are often the simplest and easiest way to contribute.

You can also simply run `python -I scripts/whats_left.py` to assist in finding any unimplemented
method.
You can also join us on [**Discord**](https://discord.gg/vru8NypEhv).

## Compiling to WebAssembly

Expand Down