Skip to content

chore: add LLM policy to contributing and (new) PR template#9182

Open
janl wants to merge 1 commit intomasterfrom
nollm
Open

chore: add LLM policy to contributing and (new) PR template#9182
janl wants to merge 1 commit intomasterfrom
nollm

Conversation

@janl
Copy link
Member

@janl janl commented Feb 25, 2026


## Checklist

- [ ] This is my own work, I did not use AI, LLM's or similar technology
Copy link
Contributor

Choose a reason for hiding this comment

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

This wording is too restrictive. Most developers "use AI" in some sense, and asserting "this is my own work" should cover it.

Copy link
Member Author

Choose a reason for hiding this comment

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

what usage do you think is acceptable?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think either we need to follow what Apache says (easy mode!), or discuss what we consider "using AI". If I get an error message while working and ask claude / gemini / google with the automated AI box at the top what it means, is that "using" AI? If I have never really noticed that VSCode autocomplete is copilot now, is that using AI?

My view on this right now is that if we are not confident in licencing, we should constrain this to clearly be about the PR as output, as opposed to the PR as process. "I am a human, and this code, documentation and other associated works in the PR are written by me, not an LLM or similar technology". Something along those lines.

I'd also suggest in the comments on the template making it clear we don't support bot submissions (eg from openclaw or whatever) or LLM work in general due to licencing issues.

Copy link
Member Author

Choose a reason for hiding this comment

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

@SCdF that’s a useful view that I am happy with. I’ll make adjustments accordingly.

@garethbowen I take your +1 as support :)

Copy link
Member Author

Choose a reason for hiding this comment

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

new push is more explicit

Thus, it is expressly forbidden to contribute material generated by AI, LLMs,
and similar technologies, to the PouchDB project. This includes, but is not
limited to, source code, documentation, commit messages, or any other areas of
the project.
Copy link
Contributor

Choose a reason for hiding this comment

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

I like @pjfanning 's suggestion to lean on Apache's docs here: https://www.apache.org/legal/generative-tooling.html

Copy link
Member Author

Choose a reason for hiding this comment

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

I don’t agree with the ASF’s take tho :)

Copy link
Contributor

@garethbowen garethbowen left a comment

Choose a reason for hiding this comment

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

I'm ok with this compromise. Approving.

This feels significant enough that it would be good to get more than one review from the community before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants