If there is barely any code in those repos that you wrote, how can you license them under the GPL? You don't hold the copyright for it.
This genuinely isn't an attack, I just don't think you can? The AI isn't granted copyright over what it produces.
This genuinely isn't an attack, I just don't think you can? The AI isn't granted copyright over what it produces.
For code generated by an LLM the human user would likely be considered the author if you provided sufficient creative input, direction, or modification.
The level of human involvement matters, simply prompting "write me a function" might not be enough, but providing detailed specifications, reviewing, and modifying the output would strengthen the claim.
the Copyright, Designs and Patents Act 1988 (CDPA), Section 9(3) staes, "In the case of a literary, dramatic, musical or artistic work which is computer-generated, the author shall be taken to be the person by whom the arrangements necessary for the creation of the work are undertaken". This was written before LLM's existed, but recent academic literature has supported this position, https://academic.oup.com/jiplp/article/19/1/43/7485196?login...
However, a comparable situation was tested with Thaler v Comptroller-General, where courts emphasised that legal rights require meaningful human involvement, not just ownership of the AI system. - https://www.culawreview.org/journal/unlocking-the-canvas-a-l... and https://www.whitecase.com/insight-our-thinking/uk-supreme-co...
I do acknowledge there is uncertainty, and this is highlighted here in "The Curious Case of Computer-Generated Works under the Copyright, Designs and Patents Act 1988.", with "section 9(3): the section is either unnecessary or unjustifiably extends legal protection to a class of works which belong in the public domain" - https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4072004
Today, I think it's doubtful that a functional application can be entirely vibe coded without decent direction and modification, but I don't think that will always be the case.
for code it hasn't been challenged yet, but I find it doubtful they'd decide differently there
So far, the judge believe that training models on open source code is not a license violation as the code is public for anyone to read, but by "distribution or redistribution" (I assume, of the model's outputs?) it is still up for the court's decision whether that violate the terms of the license, among other laws.
The case is currently moved to Ninth Circuit without a decision in the district court, as there are other similar cases (such as Authors Guild's) and they wanted that the courts would offer a consistent rules. I believe one of the big delay in the case is in damages, which I think the plaintiff tried to ask for details of Microsoft's valuation of GitHub when it was acquired, as GitHub's biggest asset is the Git repositories and may provide a monetary value of how much each project is worth. Microsoft is trying to stall and not reveal this.
The legal standards in the United States for software copyrights are Jaslow and Altai, known to Federal courts as SSO [0] and AFC [1], respectively.
These standards consider the overall structure of code as being copyrightable. This means that you can't just rename a bunch of variables and class names. The overall organization of the code is considered an arbitrary expression. Someone would be infringing on copyright if they took your Java code and converted it to Python with different class, variable and function names but kept the same relationships between classes and the same general structure.
So what does this have to do with LLMs? Well, if the author directed the code to be structured in a certain way, directed to create specific APIs, etc, then there is a legal argument that the author has at least copyright over the arbitrary and expressive decisions that were made while building a software system.
[0] https://en.wikipedia.org/wiki/Structure,_sequence_and_organi...
[1] https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari...
The "barely" part may be important and I would like to know what others are doing.
I get that people do it anyway but I guess it's kind of a grey-area because it's hard to tell after the fact that some snippet has been copied from SO.
There was a much appealed case of a monkey taking a photo, where it was decided the photo was in the public domain.
https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
It boiled down to the creator not being a "legal person" and so could not hold copyright.
The real problem for software is where the line is for a "sufficient" transformation from the source material by a human to make it acquire copyright. You can write a Dickens' character derived novel and have copyright in it, but not gain control over those characters as Dickens described them.
Claim partial copyright without specifying clearly what exactly?
People sell annotated Bibles, or Shakespeare etc. You can transform it in to something that can acquire copyright, but it must have an artistic step.
This is a big thing in the fine art world as well, you can take inspiration, you can in some circumstances outright copy, but then you need to transform it sufficiently that it becomes your own art. People argue in front of judges about this stuff, of course.
Verne is a good example too, because if you print an English version, the translator acquires copyright in the translated version.
Unless the product includes code licensed by others, then - like any other repo - I don't see any license issue here.
If you mean there is no insight as to whether licensed code is included, that's one of the constraints of vibe-coding (which people often confuse with AI-assisted coding).
Its the job of the user to check and curate the contributions as they would any third-party human input (eg. via prs). Again though - that's not an AI coding issue, but a human process decision.
If you tried to sue someone for copyright infringement based on code that an LLM generated for you, you'd be laughed out of court.
Use a hammer, you own the output. Use an intern, the intern does.
Of course if you're aren't a person you can't own anything.
Take whatever you want and relicense it cause it doesn't belong to the "author"
Lolololololol "author"
They can say the code is in the public domain.
This is distinct from open source, yes, but in almost all cases less restricted than anything with a (open source or otherwise) license.