glibc AI policy

Florian Weimer fweimer@redhat.com
Thu Apr 2 17:55:14 GMT 2026


* DJ Delorie:

> Florian Weimer <fweimer@redhat.com> writes:
>> So I don't think this is an urgent issue for the project.  I expect
>> that the FSF, as the ultimate legal guardian of the code base, will
>> provide us with legal guidance at some point in the future.
>
> IMHO we should have a public policy, and as soon as practical, even if
> that policy is "we're waiting for the FSF".  We can update the policy if
> the FSF provides guidance, but until then, I think it's better to
> anticipate the obvious questions and have answers ready for them.

I would be fine with waiting for guidance from the FSF.

> Waiting until after the flood of AI patches comes in is too late.

Why?  In some ways, the worst-case scenario for us as the community
would be a flood of high-quality contributions (whether AI-generated or
not).  How would we block that, and could we justify it?  The
low-quality flood largely hasn't happened, and I doubt that it ever will
at this point.  Not being on Github probably has helped a lot.

I think we can deal with problems as they arise, rather than planning
for scenarios that might never materialize.

Thanks,
Florian



More information about the Libc-alpha mailing list