glibc AI policy

[DJ Delorie]

Florian Weimer <fweimer@redhat.com> writes:
> I don't think how this could be useful.  For example, one vendor seems
> to claw back copyright assignment on generated content to the user after
> they violate service terms, but only for free accounts.  How would we
> model that in analysis tooling?

If it were me, and that happened, I'd strip that vendor out completely
for being too risky and/or tainted.  However, I think your situation has
a bug in that I don't think copyright status depends on who is doing the
copying, only that copying was done.  If they claw back copyright, it's
clawed for everyone.

> I also don't understand why we are suddnely worried so much about risks.
> May be let the FSF do the worrying on our behalf?

The FSF has a long track record of taking a long time to decide
important issues.  We need to know how to deal with AI submittals now.
As I've said before, even if our policy is "wait for the FSF" we still
need *a* policy.  At the moment, that policy inclues the assisted-by
tag.