Skip to content

Add AI development policy #2379

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

Merged
erikvansebille merged 3 commits into from
Nov 14, 2025
Merged

Add AI development policy #2379

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d41419
Add a text on AI development policy
erikvansebille Nov 14, 2025
c6bc115
Update docs/development/policies.md
erikvansebille Nov 14, 2025
c4fee28
Update docs/development/policies.md
erikvansebille Nov 14, 2025
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
12 changes: 12 additions & 0 deletions docs/development/policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
# Policies

## Use of AI in development

Many developers use AI Large Language Models to help them in their work. These LLMs have received both praise and criticism when it comes to software development.

We accept that Parcels developers have their own motivation for using (or not using) AI. However, we have one policy that we expect all Parcels developers to follow:

> It is ultimately your responsibility to understand the code that you commit.

Remember that reviews are done by human maintainers - asking us to review code that an AI wrote but you don't understand isn't kind to these maintainers.

The [CLAUDE.md](/CLAUDE.md) file in the repository has additional instructions for AI agents to follow when contributing to Parcels.

## Versioning

Parcels follows [Intended Effort Versioning (EffVer)](https://jacobtomlinson.dev/effver/), where the version number (e.g., v2.1.0) is thought of as `MACRO.MESO.MICRO`.
Expand Down