NOTE: there are a few Apache projects with AI projects listed in the link Tim gave me. They are all listed as having less restrictive AI policies, while some other non-Apache open-source projects have varying degrees of strictness. Here they are for convenience:
- [Apache Airflow](https://airflow.apache.org/): [Gen-AI Assisted contributions](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions), [Add Copilot code review instructions to catch AI-slop PRs#62442](https://github.com/apache/airflow/pull/62442) - [Apache DataFusion](https://datafusion.apache.org): [AI-Assisted contributions](https://datafusion.apache.org/contributor-guide/index.html#ai-assisted-contributions) - [Apache Kvrocks](https://kvrocks.apache.org/): [Guidelines for AI-assisted Contributions](https://kvrocks.apache.org/community/contributing/#guidelines-for-ai-assisted-contributions) - [Apache® Software Foundation (ASF)](https://www.apache.org/): [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) - [Arrow](https://arrow.apache.org): [AI-generated code](https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code) On Tue, Mar 3, 2026 at 10:13 AM Matteo Golin <[email protected]> wrote: > Hi everyone, > > This vote has somewhat turned into a discussion for now it seems. I just > wanted to update everyone that I reached out to Tim Hoffman from Matplotlib > about using their policy in NuttX, and he responded: > > """ > Hi Matteo, you are welcome to take whatever seems useful from our poliy. > It's an ongoing topic and as technology and usage patterns unfold, I'm sure > we will continuously evolve our policy. > Melissa has compiled an overview of AI policies of several projects: > https://github.com/melissawm/open-source-ai-contribution-policies You may > find that helpful as well. > """ > > So there should not be any issues with using/adapting the Matplotlib > policy. > > On Mon, Feb 23, 2026 at 5:08 PM Tomek CEDRO <[email protected]> wrote: > >> Btw I have proposed something more generic and NuttX tailored to be >> added to the Contirbuting Guide in the discussion theead.. this also >> explains our stance and contains all remarks from the Matplotlib's >> version but we can use that one as well :-) >> >> The AGENTS.md is a file to be read and instruct potential AI agents >> not humans. So we can create a dedicated intructions for the AI over >> there just like Linguini suggested it seems official approved and >> widely used approach :-) >> >> >> 1.18. AI and Agents. >> >> 1.18.1. We expect authentic engagement in our community. NuttX comes >> from years of hard work, passion, and personal dedication of >> individuals from around the world. We welcome and respect people with >> similar mindset. But we do not tolerate shortcuts and we have clearly >> defined enemies (see The Inviolable Principles of NuttX). >> >> 1.18.2. AI tools may do some of the work parts for you but it will not >> think for you. Treat them as your helpers but only in tasks which you >> already have experience so you can understand, verify, and explain the >> results details to anyone else on your own. We use tools to save our >> precious time. Without prior experience and perfect understanding the >> outcome is quite opposite - everyone's time is wasted - and we want to >> avoid that. >> >> 1.18.3. Using AI tools for your internal work like brainstorming, >> prototyping, finding information and examples, text correction, >> verification against contributing guidelines and code formatting, is >> fine, but the final submission shared with the project must be result >> of your own work and intellect. This effort makes us grow, develop >> individual skills, and provides experience necessary for top quality >> results. >> >> 1.18.4. Using AI tools to generate a code, git commits, pull requests, >> or any communication channel messages, even with minor edits to >> pretend it's your own work, is unacceptable. This contradicts the >> Apache Software Foundation contribution rules [citation_needed]. This >> also imposes serious copyright and licensing infringement risks >> because very often AI generated content is copyrighted by the AI owner >> even if you created the result. If this is your first or following >> contribution you will be banned. >> >> 1.18.5. We reserve right to ban/block/remove user accounts that are >> considered malicious/spam/bot/ai activity that break any of the >> presented rules. >> >> 1.18.6. The only exception here is for our own internal and approved >> testing or automation tools that may, but usually do not, have some >> sort of reporting autonomy, that we have created ourselves in >> accordance with presented rules. >> >> -- >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> >> On Mon, Feb 23, 2026 at 9:07 PM Sebastien Lorquet <[email protected]> >> wrote: >> > >> > Hello >> > >> > I fully support this policy including the strong restriction in the >> > final paragraph. >> > >> > If you just assert vague advice, it will be considered optional and >> > never applied. >> > >> > Sebastien >> > >> > >> > Le 23/02/2026 à 16:28, Matteo Golin a écrit : >> > > Hello everyone, >> > > >> > > Following the discussion thread on this topic [1], I am starting a >> vote to >> > > adopt the Matplotlib AI use policy [2] in NuttX. >> > > >> > > The proposal is to include the policy verbatim in the contributing >> guide >> > > under the new header "Restrictions on Generative AI usage". I have >> changed >> > > "our discourse server" to "our mailing list/forums" in order to match >> the >> > > methods NuttX uses for communication. >> > > >> > > The policy is copy-pasted below with that change: >> > > >> > > """ >> > > >> > > We expect authentic engagement in our community. >> > > >> > > - >> > > >> > > Do not post output from Large Language Models or similar >> generative AI >> > > as comments on GitHub or our mailing list/forums, as such >> comments tend to >> > > be formulaic and low content. >> > > - >> > > >> > > If you use generative AI tools as an aid in developing code or >> > > documentation changes, ensure that you fully understand the >> proposed >> > > changes and can explain why they are the correct approach. >> > > >> > > Make sure you have added value based on your personal competency to >> your >> > > contributions. Just taking some input, feeding it to an AI and >> posting the >> > > result is not of value to the project. To preserve precious core >> developer >> > > capacity, we reserve the right to rigorously reject seemingly AI >> generated >> > > low-value contributions. >> > > >> > > In particular, it is also strictly forbidden to post AI generated >> content >> > > to issues or PRs via automated tooling such as bots or agents. We may >> ban >> > > such users and/or report them to GitHub. >> > > """ >> > > >> > > Best, >> > > Matteo >> > > >> > > [1]: https://www.mail-archive.com/[email protected]/msg14336.html >> > > [2]: >> > > >> https://matplotlib.org/devdocs/devel/contribute.html#restrictions-on-generative-ai-usage >> > > >> >
