Riccardo/David, I emailed Richard Stallman about our discussion and forwarded the current policy, as we had discussed it on the other list, to him.
My previous emails made my position very clear: - GNUstep should evaluate contributions based on their licensing, quality, correctness, review, provenance, and maintainability—not on the development tools used to create them. - There is no reliable, objective way to distinguish AI-assisted code from human-written code, making a blanket "No-AI" policy difficult to define, enforce, and apply fairly. - The existing AI policy strikes the right balance by requiring responsible disclosure while allowing maintainers to continue judging submissions on their technical merits. Additionally, the case I cited ( https://www.scotusblog.com/cases/thaler-v-perlmutter/) makes it clear that we should not accept code that is composed in its entirety by AI because, given the ruling in that case, provenance is dubious. I believe it's okay to use in a limited sense for fixing bugs, writing boilerplate code (e.g. anything that is repetitive), but that entire classes, etc. should not be allowed and, if they are, then the author must be able to fully understand and explain the code. Yours, GC On Wed, Jul 15, 2026 at 10:57 AM Riccardo Mottola < [email protected]> wrote: > Hi David, > > > David Chisnall wrote: > > This week, EMACS paused ‘AI’ contributions because the GNU project is > expected to provide an explicit policy soon. I presume that policy will > apply to GNUstep as well. > > Didn't know that... there is so much influx about this topic and mostly > I need to be "work biased". > > I'm curious to read what it will be for GNU. It makes sense, as I > pointed out myself. > > I hope it will be strict but not unreasonable. Many aspects need to be > covered, not just different types of "contribution" to the project > itself, but I guess also connection to external providers, etc etc. Way > beyond the original intent of code contribution to GNUstep I started > this topic for. > > Riccardo > -- Gregory Casamento GNUstep Lead Developer / Black Lotus, Principal Consultant http://www.gnustep.org - http://heronsperch.blogspot.com https://www.openhub.net/languages/objective_c
