We now note that that we do not waive our attribution requirements for Spritely Goblins, which are present in Apache v2 (and for that matter, CC BY, CC BY-SA, and most FOSS licenses) https://codeberg.org/spritely/goblins/pulls/998/files

(1/2) IMO @cwebber has made a strawperson argument, because I don't know anyone (at least, anyone who is serious about #FOSS policy & how its impacted by LLM-gen-AI) who says “nobody cares about attribution requirements”.

I can only speak for my own position, but my position (based on 30 years of community observation) is that (a) attribution is not particularly important to most *who choose* **non**-copyleft, & (b) attribution *alone* never had a particularly good enforcement hook.…

#AI #LLM

@bkuhn @cwebber

Maybe ive been reading too much into some words; or maybe Ive misunderstood.

BUT some of your conversations and comments on LLMs to me and others have had a distinct "attribution is going to be fucked in a post-LLM world, the best we can hope for is to preserve copyleft" vibe to it.

I would be hard pressed to find an example in our own comment history; as my toots self destruct after a few months. BUT it's definitely come up.

Anyway; am I wrong in that sentiment? Do you think there is a way forward with some of these LLM concerns preserving attribution?

@trashheap

If a statement I made seemed like I said that, I either misspoke or it was misquoted. (Also, I wouldn't have 🤬'd making a point like this in any event.)

My position is instead that enforcement of attribution requirements **by themselves** (without other copyleft provisions to provide scaffolding) has always been extremely difficult to nearly impossible in real world contexts. #LLMGenAI may make the problem more acute, but the problem has always been there.

Cc: @cwebber

#LLM #AI

Btw I have heard at least one prominent FOSS person (I'm choosing to not fill their notifications here by identifying them) that nobody cares about attribution requirements (and particularly not enforcing them). But to me, attribution is what I care about MORE than any other licensing requirements, more than copyleft "share-alike" style provisions, etc.

If you feel similarly, it would be good to hear on this thread. Perhaps even copying a similar notice into your project is a good idea.

@bkuhn @cwebber Sorry I did not mean to indicate that was a direct quote (thus the word vibe, following it.) BUT that was the impression ive been getting from following much of your and cwebber's conversations on the subject; and from some comments youve sent my way.

We now note that that we do not waive our attribution requirements for Spritely Goblins, which are present in Apache v2 (and for that matter, CC BY, CC BY-SA, and most FOSS licenses) https://codeberg.org/spritely/goblins/pulls/998/files

So if you train on our codebase, you have to retain attribution, which we consider the most important requirement to motivate development of technology in the commons.

If, somehow, you are using a statistical soup which has no way to preserve attribution, well, we don't permit or approve of dropping such a requirement, and actually, the licenses we use never have.

@cwebber that's very interesting!

I'm not sure your licenses apply to training LLMs; it's not clear to me that copyright governs the training process.

I know you think differently; that a license attaches like a spell to the bits and bytes, no matter how small the excerpt or how varied the rearrangement.

@cwebber

The mechanism is not the issue. I think the expression of author intent is really important!

For Web resources, we have the AI preferences from IETF:

https://datatracker.ietf.org/doc/html/draft-ietf-aipref-attach-05

But, of course, Free Software doesn't just come from one website. It's made to be spread around. It would be good to have some sort of AI prefs expressed in the package itself, no matter where it is.

Btw I have heard at least one prominent FOSS person (I'm choosing to not fill their notifications here by identifying them) that nobody cares about attribution requirements (and particularly not enforcing them). But to me, attribution is what I care about MORE than any other licensing requirements, more than copyleft "share-alike" style provisions, etc.

If you feel similarly, it would be good to hear on this thread. Perhaps even copying a similar notice into your project is a good idea.

@trashheap

Hopefully it is clear now that it was a misunderstanding.

Cc: @cwebber

@evan

@cwebber it is for these reasons we need something better than open source. An ethical open license.

@bkuhn @trashheap I appreciate the clarification on your position here.

I still do hold the positions that attribution are the glue that hold the commons together, and it's important that we fight to preserve it, and not give the impression that it is being voluntarily waived in the face of LLMs.

@cwebber @bkuhn @trashheap@tech.lgbt If bkuhn's right that permissive licenses make attribution hard to enforce, then the best way to accomplish that would be to use copyleft.

Anyway, if you keep Apache v2, it would certainly make sense to include a NOTICE file, since currently an Object derived from goblins does not need to attribute you at all. And as Apache v2 defines "Object", that seems to include AI models.

@joeyh @bkuhn Hm, interesting point re: NOTICE

@joeyh @bkuhn I have always found NOTICE to be pretty weird

@bkuhn @trashheap I appreciate the clarification on your position here.

I still do hold the positions that attribution are the glue that hold the commons together, and it's important that we fight to preserve it, and not give the impression that it is being voluntarily waived in the face of LLMs.

@cwebber @bkuhn @trashheap IMO the real challenge to FOSS enforcement against LLM producers is the same one everyone else has: if the training is fair use because the resulting model is transformative, the producer doesn’t need a license (and doesn’t have to respect the terms of any existing license). It’s still early early days in terms of court decisions, but this looks like the direction we’re headed in the US (though the outcome will likely vary depending on how much memorization a model can be shown to do).

@copiesofcopies @bkuhn @trashheap My main concern is that the resulting legislative environment is as equitable for FOSS as it is for the proprietary world, whatever the outcome is. In many ways this is why I'm happy to see the vibe-laundered versions of Adobe's suite etc, I think that will push the issue.

@joeyh @bkuhn However in the case of code, I think attribution is more important to me on source than on object form anyway, since that's where the cultural history of the collaborative work is kept

@cwebber @bkuhn @trashheap unfortunately, we’re falling behind quickly, just in terms of the regulatory impact on who can afford to build competitive models. The CLAIM Act (just introduced) is basically designed to compel anyone who trains a model to either: (1) make it impossible for that model to accidentally cause harm, or (2) buy expensive insurance to cover the damage from inevitable harm.