Yes, that is what I suggested at https://github.com/apache/nuttx/pull/19250
Fortunately (or unfortunately) we don't have the same issues of Godot, we don't have hundreds/thousands of contributors submitting PRs. So, I think more important than totally blocking AI contributions is to make sure that the contributor understands what was created by AI with the help of AI and the contribution is not a slop code. This way I suggest we take a moderated approach, the same way we allow licenses that are not compatible with NuttX: adding a Kconfig option to let the users to decide whether they want AI code or not. BR, Alan On Wed, Jul 1, 2026 at 2:45 PM Lwazi Dube <[email protected]> wrote: > If the project is serious about licensing, copyrights and SBOM, are you > willing to add something like this to Kconfig too, AI-generated of course > :) > > menu "License Setup" > > config ALLOW_AI_COMPONENTS > bool "Allow AI-generated components with unverified provenance" > default n > help > Enabling this allows the use of AI-generated code where the exact > origin, licensing, and authorship cannot be verified. This may > introduce compliance, security, and legal risks. > > endmenu > > > 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/ > > >
