Live data from Hacker News

Relicensing with AI-Assisted Rewrite

tuananh.net

11–20 of 408 posts

Re: Relicensing with AI-Assisted Rewrite

#11
post #6

I like the idea of AI-generated ~code~ anything being public domain. Public data in, public domain out.

This could be read as a reformulation of the old adage - "what's mine is mine, and what is yours, is mine too".

So, you can pilfer the commons ("public") but not stuff unavailable in source form.

If we expand your thought experiment to other forms of expression, say videos on YT or Netflix, then yes.

Re: Relicensing with AI-Assisted Rewrite

#12
I think the more interesting question here would be if someone could fine tune an open weight model to remove knowledge of a particular library (not sure how you'd do that, but maybe possible?) and then try to get it to produce a clean room implementation.

Re: Relicensing with AI-Assisted Rewrite

#13
post #6

I like the idea of AI-generated ~code~ anything being public domain. Public data in, public domain out.

I don't think you can classify "public data in" as public domain. Public data could also include commercial licenses which forbid using it in any way other than what the license states. Just because the source is open for viewing does not necessarily mean it is OSL.

That's the core issue here. All models are trained on ALL source code that is publicly available irrespective of how it was licensed. It is illegal but every company training LLMs is doing it anyways.

Re: Relicensing with AI-Assisted Rewrite

#15
post #13
post #6

I like the idea of AI-generated ~code~ anything being public domain. Public data in, public domain out.

I don't think you can classify "public data in" as public domain. Public data could also include commercial licenses which forbid using it in any way other than what the license states. Just because the source is open for viewing does not necessarily mean it is OSL. That's the core issue here. All models are trained on ALL source code that is publicly available irrespective of how it was licensed. It is illegal but e…

Copyright is not a blacklist but an allowlist of things kept aside for the holder. Everything else is free game. LLM ingestion comes under fair use so no worries. If someone can get their hand on it, nothing in law stops it from training ingestion.

We can debate if this law is moral. Like the GP I took agree public data in -> public domain out is what's right for society. Copyright as an artificial concept has gone on for long enough.

Re: Relicensing with AI-Assisted Rewrite

#16

This is precedent setting. In this case the rewrite was in same language, but if there's a python GPL project, and it's tests (spec) were used to rewrite specs in rust, and then an implementation in rust, can the second project be legally MIT, or any other? If yes, this in a sense allows a path around GPL requirements. Linux's MIT version would be out in the next 1-2 years.

No, GPL still holds even if you transform the source code from one language to another language.

That why I carved it out to just the specs. If they can be read as "facts", then the new code is not derived but arrived at with TTD.

The thesis I propose is that tests are more akin to facts, or can be stated as facts, and facts are not copyright-able. That's what makes this case interesting.

Re: Relicensing with AI-Assisted Rewrite

#17
> The ownership void: If the code is truly a “new” work created by a machine, it might technically be in the public domain the moment it’s generated, rendering the MIT license moot.

How would that work? We still have no legal conclusion on whether AI model generated code, that is trained on all publicly available source (irrespective of type of license), is legal or not. IANAL but IMHO it is totally illegal as no permission was sought from authors of source code the models were trained on. So there is no way to just release the code created by a machine into public domain without knowing how the model was inspired to come up with the generated code in the first place. Pretty sure it would be considered in the scope of "reverse engineering" and that is not specific only to humans. You can extend it to machines as well.

EDIT: I would go so far as to say the most restrictive license that the model is trained on should be applied to all model generated code. And a licensing model with original authors (all Github users who contributed code in some form) should be setup to be reimbursed by AI companies. In other words, a % of profits must flow back to community as a whole every time code-related tokens are generated. Even if everyone receives pennies it doesn't matter. That is fair. Also should extend to artists whose art was used for training.

Re: Relicensing with AI-Assisted Rewrite

#18

This is precedent setting. In this case the rewrite was in same language, but if there's a python GPL project, and it's tests (spec) were used to rewrite specs in rust, and then an implementation in rust, can the second project be legally MIT, or any other? If yes, this in a sense allows a path around GPL requirements. Linux's MIT version would be out in the next 1-2 years.

Its very important to understand the "how" it was done. The GPL hands the "compile" step, and the result is still GPL. The clean Room process uses 2 teams, separated by a specification. So you would have to

1. Generate specification on what the system does. 2. Pass to another "clean" system 3. Second clean system implements based just on the specification, without any information on the original.

That 3rd step is the hardest, especially for well known projects.

Re: Relicensing with AI-Assisted Rewrite

#20
I mean in my opinion GPL licensed code should just infect models forcing them to follow the license.

You can do this a lot by saying things like: complete the code "".

And if now the models are GPL licensed the problem of relicensing is gone since the code produced by these models should in theory be also GPL licensed.

Unfortunately, there is a dumb clause that computer generated code cannot be copyrighted or licensed to begin with.

Post reply on HN