They did not actually calculate damages in terms of lost movie tickets or estimates vs actually sales number of sold game copies. When it came to pre-releases where such product wouldn't have been sold legally in the first place, they simply added a multiplier to indicate that the copyright owner wouldn't have been willing to sell.
For software code, an other practice I have read is to use the man-hours that rewriting copyrighted code would cost. Using such calculations they would likely estimate the man hours based on number of lines of code and multiply that with the average salary of a programmer.
The average salary of a programmer in which country?
So much programming is outsourced these days, and in some places programmers are very cheap.
If the court wanted to distinguish between Microsoft using their own programmers to generate code vs taking code from github users, then the salary in question would likely be that of Microsoft programmers. It would then be used to illustrate how a legal training data would look like compared to an illegal one.
If "I took your code and trained an AI that then generated your code" is a legal defense, the GPL and similar licenses all become moot.
https://docs.github.com/en/site-policy/github-terms/github-t...
"You grant us and our legal successors the right to store, archive, parse, and display Your Content"
Copilot displays content. Case closed.
"This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content"
Sometimes damages are statutory, i.e. they have a fixed dollar amount written right into the law. This lawsuit references one such law: https://www.law.cornell.edu/uscode/text/17/1203
If you have co-pilot trained on my code base (which was private), that then reproduces near replica's of my code then they sell it for $5/year...
Well, I'm eligible for damages.
(If it was, please tell me how, since that would save me $5/year across multiple libraries..!)
Copying a few lines is not the same as copying the whole thing. Sharing quotes from a book is not copyright infringement.
Using clips from a movie in a movie review is probably fair use.
Using clips from a movie in knock-off of that movie for profit? Probably not fair use if it's not a parody.
Copilot is not like a movie reviewer using clips to review a movie. Copilot is like a production team for a movie taking clips from another movie to make a ripoff of that movie and selling it.
Consider every repo on github to be a movie. Copilot is taking individual frames out of every movie on github and composting them into a new film.
I think most of us would agree that individually, each frame is copyrighted. But what if you take one frame from a million different movies and put them in an order that produces a new coherent movie?
The core question we need to settle in court is: does the new movie become its own copyrightable work, or is it plagiarism?
https://en.wikipedia.org/wiki/Sampling_(music)#Legal_and_eth...
I.e. any use without permission is illegal.
I can't think of a 5 line snippet I've written or read that makes sense to claim ownership of. They don't stand on their own in the way even a 30s movie clip does.
Copilot is fair use and transformative -- that is unless there is an open source Copilot that Copilot is training on, only then would it be competing and it's easy for GitHub or OpenAI to exclude those repos of copilot alternatives from the training set.
It is if I take those quotes and publish them as my own in my own book.
Code which anybody can view is called "source available". You aren't necessarily allowed to use the code, but some companies will let their customers see what is going on so they can better integrate the code, understand performance implications, debug and fix unexpected issues, etc. The customers would probably face significant legal risks if they took that code and started to sell it.
"Open source" code implies permission to re-use the code, but there is still some nuance. Some open-source licenses come with almost no restrictions, but others include limiting clauses. The GPL, for example, is "viral": anybody who uses GPL code in a project must also provide that project's source code on request.
What do you think the chances are that Microsoft would surrender the Copilot codebase upon receipt of a GPL request?
Unrelated, how is it that Mechanical Turk was never truely integrated w/ AWS?
If someone wants to use it commercially without complying with the GPL, I have no problem with allowing that, for a price.
Either use the code freely and openly, or pay me so you can make money on my code.
Copilot could conceivably allow someone to use my code commercially (and in a closed manner) without negotiating with me, the copyright holder.