Was there an option presented for those of us who want to keep our
open-source projects 100% free of AI-generated code? That discussion
absolutely should have happened. If there’s a link to it, please
share—imposing these tools on people who didn't ask for them is not
acceptable.

On Wed, 1 Jul 2026 at 11:47, Matteo Golin <[email protected]> wrote:

> Hello everyone,
>
> NuttX still has not adopted an AI policy, and the number of substantially
> AI-generated contributions is continuing to grow. Recently, the Godot
> project adopted a new AI policy which I think is quite reasonable. [1]
>
> I would like to suggest that NuttX adopt the AI policy from Godot [1]
> (slightly modified for more clarity), as follows, and include it in our
> contribution guide:
>
> - *No autonomous AI agent use or vibe coding*
>
>    - A human must be involved in the coding process if patches are
> submitted
>
> - *No use of AI to generate substantial pieces of code*
>
>    - We require all code to be human authored. AI assistance should be
>    limited to menial things (like code completion, regex, formatting, or
> find
>    and replace).
>    - If you do use AI in some capacity to author code, you must disclose it
>    in the PR discussion.
>
> - *No AI-generated text in human-to-human communication*
>
>    - When our maintainers volunteer their time to review your issue, PR, or
>    proposal, they do not want to talk to a machine. This is a basic
> principle
>    of respect.
>    - Machine translations are still acceptable as long as the original
>    content was written by a human.
>    - This includes PR descriptions and comments.
>
> - *All PRs must be reviewed and approved by a human before merging*
> Please let me know your thoughts, I really think it is time to adopt this
> change as I am seeing more and more frequently that substantially
> AI-generated PRs are submitted (what is really most frustrating is its use
> in human-to-human communication).
>
> Best,
> Matteo
>
> [1]: https://godotengine.org/article/contribution-policy-2026/
>

Reply via email to