Yup, this became common problem in all sorts of projects, not only Open-Source ones.. which results in distraction and waste of human and technical resources.. thus I am also against this kind of shortcuts.
Considering overload of the CI these PRs also impose danger to our project with limited resources - valuable contributions may not get in and other projects that share Apache resources will suffer too, in worst case scenario we will loose the CI. I saw several of these "well described" PRs that for instance only added header file in the code. Description did not even match the change. I guess we could work out some sort of blocking policy for the AI generated code and amend the Contributing Guide? Also AI stuff is a huge problem in the Google Summer of Code (GSoC) where people show up out of nowhere with brilliant ideas that then never happen. Other projects like FreeBSD, NetBSD, Gentoo are also against AI generated code and content because it implies copyrights and legal issues. https://www.heise.de/en/news/FreeBSD-policy-AI-generated-source-code-No-thanks-10634141.html https://www.freebsd.org/status/report-2025-07-2025-09/ https://www.freebsd.org/status/report-2025-04-2025-06/ Have a good day folks :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Tue, Feb 3, 2026 at 4:04 PM Matteo Golin <[email protected]> wrote: > > Hello, > > This week in particular there has been a large number of AI-generated pull > requests submitted to NuttX and NuttX apps. Most of these used AI to > completely generate PR descriptions and/or commit messages. In some cases, > AI was used to generate documentation and possibly code. > > The quality of these PRs are low, containing unnecessary information that > summarized the diffs (i.e. files changed, lines inserted, etc) and > repetitive summaries. The dangerous aspect of these PRs is that the vast > majority of them contained completely generated test claims with no logs > (and in some cases, generated logs) to back them. When asked about the test > claims, the authors stated that the PR was AI-generated and removed all > claims. > > This is starting to become a trend, with a lot of recent PRs containing the > same "files changed" section. They are difficult to review because they > don't communicate the changes clearly, have unnecessary information and > often contain fabricated information. Some of them contain multiple commits > which should be reviewed split across multiple PRs and change summaries > which omit information about commits. PR authors are also refusing to > provide logs or adequate explanations in some cases. > > I think it's time for the community to discuss a stance on AI generated > submissions. I don't think it's enforceable to prevent contributors from > using AI in their PRs, and some contributors may be using it to assist them > in a moderate way (I personally do not think any AI use is good, but I know > this is not realistic for many people). I think that PRs which contain AI > generated descriptions or code should be blocked by a change request until > they are modified to improve the code quality or description quality. This > isn't really a change, that's what we do with poor code submissions. > However, I think contributors should be warned to stop using AI output if > they are not verifying it, and there should be a stance from NuttX in the > contributing guidelines regarding AI usage/guidelines. If it becomes a > pattern for certain contributors I think their PRs should start getting > closed. > > What does the community think? > > Matteo > > Here are some of these AI PRs: > > https://github.com/apache/nuttx-apps/pull/3381 > https://github.com/apache/nuttx-apps/pull/3397 > https://github.com/apache/ <https://github.com/apache/nuttx/pull/18223>nuttx > <https://github.com/apache/nuttx/pull/18223>/pull/18223 > <https://github.com/apache/nuttx/pull/18223> > https://github.com/apache/nuttx/pull/18266 > https://github.com/apache/nuttx/pull/18221 > https://github.com/apache/nuttx/pull/18219 > https://github.com/apache/nuttx/pull/18217 > https://github.com/apache/nuttx/pull/18216 > https://github.com/apache/nuttx/pull/18205 > https://github.com/apache/nuttx/pull/18207
