Re: Claude AI code audit of GNUstep core stack — 1 50 fixes, 12 perf optimizations, all available for upstream

--0000000000002c2afe0656e5199e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Lars,

I don't know how the GNU Project is arriving at its policy or whether
individual GNU projects have an opportunity to provide input. I have
written to RMS about our policy and given him a link to it.  I hope it can
inform any decision they make.

I don't think the discussion should become a witch hunt either. AI is a
tool, and like any tool, it can be used well or poorly. Regardless of how
code is produced, I believe our responsibility as maintainers remains the
same: to ensure that contributions meet our standards for licensing,
provenance, quality, correctness, maintainability, and review.

Ultimately, those standards are what determine whether code belongs in
GNUstep, not the particular tools used during its development.

I'm hoping the GNU Project reaches a thoughtful and balanced conclusion.

Yours, Greg

On Sat, Jul 18, 2026 at 5:00=E2=80=AFAM [email protected] =
<
[email protected]> wrote:

> Hi Greg,
>
> just one question in this regard: Do we have a voice in GNU=E2=80=99s dis=
cussion
> on that topic (I hope, there is a discussion an not just a decision by on=
e
> person, namely RMS)? If so, I hope, we make our standpoint clear and don=
=E2=80=99t
> go onto a witch-hunt against AI (which would be like a witch hunt against
> compilers and linkers in the times when UNIX was still written in
> assembler). In my opinion AI is just a (very sophisticated) tool which yo=
u
> need to know, how to use it and its limitations. Then we can use it sanel=
y
> and to our advantage.
>
> Hoping for the best outcome,
>
> Lars
>
> Am 18.07.2026 um 10:23 schrieb Gregory Casamento <[email protected]=
m
> >:
>
> David,
>
> Sorry for the late reply; work has been very demanding lately.  Of course=
,
> any policy they issue will apply to us.  I think this is a reasonable
> approach for EMACS if they are waiting for guidance from the GNU Project.
>
> Until that policy is published, however, I don't think it gives us any
> basis for changing GNUstep's existing approach. Once the GNU Project has
> issued its guidance, we can evaluate it on its merits, determine whether
> and how it applies to GNUstep, and discuss whether any changes are
> warranted.
>
> I believe our current policy provides a practical balance as it focuses o=
n
> licensing, provenance, code quality, review, and maintainability rather
> than the specific tools contributors use.
>
> As mentioned in previous emails, I have set a clear line on what is
> acceptable, and this was reflected in the discussion a few weeks ago.
>
> Yours, GC
>
> On Wed, Jul 15, 2026 at 4:31=E2=80=AFAM David Chisnall <gnustep@theravens=
nest.org>
> wrote:
>
>> On 14 Jul 2026, at 22:48, Gregory Casamento <[email protected]>
>> wrote:
>> >
>> > Based on the discussion, I do not see sufficient consensus or
>> justification to replace our existing AI policy with a "No-AI" policy fo=
r
>> the GNUstep core libraries. Accordingly, the existing policy will remain=
 in
>> effect.
>>
>> Most of the arguments have been covered in other places and it=E2=80=99s=
 quite
>> surprising that most of the folks in this thread seem unfamiliar with th=
em,
>> but I would add one thing:
>>
>> This week, EMACS paused =E2=80=98AI=E2=80=99 contributions because the G=
NU project is
>> expected to provide an explicit policy soon. I presume that policy will
>> apply to GNUstep as well.
>>
>> David
>>
>>
>
> --
> Gregory Casamento
> GNUstep Lead Developer / Black Lotus, Principal Consultant
> http://www.gnustep.org - http://heronsperch.blogspot.com
> https://www.openhub.net/languages/objective_c
>
>
>

--=20
Gregory Casamento
GNUstep Lead Developer / Black Lotus, Principal Consultant
http://www.gnustep.org - http://heronsperch.blogspot.com
https://www.openhub.net/languages/objective_c

--0000000000002c2afe0656e5199e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e,monospace"><p class=3D"gmail-isSelectedEnd">Lars,</p><p class=3D"gmail-is=
SelectedEnd">I don&#39;t know how the GNU Project is arriving at its policy=
 or whether individual GNU projects have an opportunity to provide input. I=
 have written to RMS about our policy and given him a link to it.=C2=A0 I h=
ope it can inform any decision they make.</p><p class=3D"gmail-isSelectedEn=
d">I don&#39;t think the discussion should become a witch hunt either. AI i=
s a tool, and like any tool, it can be used well or poorly. Regardless of h=
ow code is produced, I believe our responsibility as maintainers remains th=
e same: to ensure that contributions meet our standards for licensing, prov=
enance, quality, correctness, maintainability, and review.</p><p class=3D"g=
mail-isSelectedEnd">Ultimately, those standards are what determine whether =
code belongs in GNUstep, not the particular tools used during its developme=
nt.</p><p class=3D"gmail-isSelectedEnd">I&#39;m hoping the GNU Project reac=
hes a thoughtful and balanced conclusion.</p><p>Yours, Greg</p></div></div>=
<br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">On Sat, Jul 18, 2026 at 5:00=E2=80=AFAM <a href=3D"mailto:l=
[email protected]">[email protected]</a> &=
lt;<a href=3D"mailto:[email protected]">lars.sonchocky-hel=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div>Hi Greg,<div><br></div><div>just one question in this =
regard: Do we have a voice in GNU=E2=80=99s discussion on that topic (I hop=
e, there is a discussion an not just a decision by one person, namely RMS)?=
 If so, I hope, we make our standpoint clear and don=E2=80=99t go onto a wi=
tch-hunt against AI (which would be like a witch hunt against compilers and=
 linkers in the times when UNIX was still written in assembler). In my opin=
ion AI is just a (very sophisticated) tool which you need to know, how to u=
se it and its limitations. Then we can use it sanely and to our advantage.<=
/div><div><br></div><div>Hoping for the best outcome,</div><div><br></div><=
div><span style=3D"white-space:pre-wrap">	</span>Lars<br id=3D"m_-258826753=
7875648687lineBreakAtBeginningOfMessage"><div><br><blockquote type=3D"cite"=
><div>Am 18.07.2026 um 10:23 schrieb Gregory Casamento &lt;<a href=3D"mailt=
o:[email protected]" target=3D"_blank">[email protected]</a>&=
gt;:</div><br><div><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"f=
ont-family:monospace,monospace"><p>David,</p><p>Sorry for the late reply; w=
ork has been very demanding lately.=C2=A0 Of course, any policy they issue =
will apply to us.=C2=A0 I think this is a reasonable approach for EMACS if =
they are waiting for guidance from the GNU Project.</p><p>Until that policy=
 is published, however, I don&#39;t think it gives us any basis for changin=
g GNUstep&#39;s existing approach. Once the GNU Project has issued its guid=
ance, we can evaluate it on its merits, determine whether and how it applie=
s to GNUstep, and discuss whether any changes are warranted.</p><p>I believ=
e our current policy provides a practical balance as it focuses on licensin=
g, provenance, code quality, review, and maintainability rather than the sp=
ecific tools contributors use.</p><p>As mentioned in previous emails, I hav=
e set a clear line on what is acceptable, and this=C2=A0was reflected in th=
e discussion a few=C2=A0weeks ago.</p><p>Yours, GC</p></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 15,=
 2026 at 4:31=E2=80=AFAM David Chisnall &lt;<a href=3D"mailto:gnustep@thera=
vensnest.org" target=3D"_blank">[email protected]</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">On 14 Jul 2026, at=
 22:48, Gregory Casamento &lt;<a href=3D"mailto:[email protected]" t=
arget=3D"_blank">[email protected]</a>&gt; wrote:<br>
&gt; <br>
&gt; Based on the discussion, I do not see sufficient consensus or justific=
ation to replace our existing AI policy with a &quot;No-AI&quot; policy for=
 the GNUstep core libraries. Accordingly, the existing policy will remain i=
n effect.<br>
<br>
Most of the arguments have been covered in other places and it=E2=80=99s qu=
ite surprising that most of the folks in this thread seem unfamiliar with t=
hem, but I would add one thing:<br>
<br>
This week, EMACS paused =E2=80=98AI=E2=80=99 contributions because the GNU =
project is expected to provide an explicit policy soon. I presume that poli=
cy will apply to GNUstep as well.<br>
<br>
David<br>
<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D"ltr"><font fac=
e=3D"monospace">Gregory Casamento<br>GNUstep Lead Developer / Black Lotus, =
Principal Consultant<br><a href=3D"http://www.gnustep.org/" target=3D"_blan=
k">http://www.gnustep.org</a> - <a href=3D"http://heronsperch.blogspot.com/=
" target=3D"_blank">http://heronsperch.blogspot.com</a><br></font></div></d=
iv><div dir=3D"ltr"><font color=3D"#888888" face=3D"monospace"><a href=3D"h=
ttps://www.openhub.net/languages/objective_c" style=3D"color:rgb(17,85,204)=
" target=3D"_blank">https://www.openhub.net/languages/objective_c</a></font=
></div></div></div></div>
</div></blockquote></div><br></div></div></blockquote></div><div><br clear=
=3D"all"></div><div><br></div><span class=3D"gmail_signature_prefix">-- </s=
pan><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div di=
r=3D"ltr"><div><div dir=3D"ltr"><font face=3D"monospace">Gregory Casamento<=
br>GNUstep Lead Developer / Black Lotus, Principal Consultant<br><a href=3D=
"http://www.gnustep.org" target=3D"_blank">http://www.gnustep.org</a> - <a =
href=3D"http://heronsperch.blogspot.com" target=3D"_blank">http://heronsper=
ch.blogspot.com</a><br></font></div></div><div dir=3D"ltr"><font color=3D"#=
888888" face=3D"monospace"><a href=3D"https://www.openhub.net/languages/obj=
ective_c" style=3D"color:rgb(17,85,204)" target=3D"_blank">https://www.open=
hub.net/languages/objective_c</a></font></div></div></div></div>

--0000000000002c2afe0656e5199e--