- respect attribution
- respect copyleft
- respect proprietary licences
- give the user appropriate hints about the above
Or does it just copy code without doing any of this?
11–20 of 838 posts
- respect attribution
- respect copyleft
- respect proprietary licences
- give the user appropriate hints about the above
Or does it just copy code without doing any of this?
I guess the question is where you draw the line between a derivative work and "learnt by an AI algorithm"
If GitHub could guarantee that the code Copilot had ingested was only made with OSS licenses, then I don't see what the problem is. But as far as I understand, GitHub trained Copilot on any public repository on GitHub, meaning even if it doesn't have a license specified (so the user publishing it still has the copyright to it), then I don't see how it can be OK.
The whole thing is just bizarre when the vast majority of developers constantly look at OSS code daily and lift ideas/patterns/snippets from there regularly without once looking at whatever license is attached.
Is it smart enough to: - respect attribution - respect copyleft - respect proprietary licences - give the user appropriate hints about the above Or does it just copy code without doing any of this?
If GitHub could guarantee that the code Copilot had ingested was only made with OSS licenses, then I don't see what the problem is. But as far as I understand, GitHub trained Copilot on any public repository on GitHub, meaning even if it doesn't have a license specified (so the user publishing it still has the copyright to it), then I don't see how it can be OK.
It is hard to see how verifying licenses is a solvable problem, when licensing for code dependencies can be transitive. For ex - if I copy code from a GPL codebase like Linux and create a Github repository with an MIT license.
But that would mean Microsoft acknowledging license violations.
If GitHub could guarantee that the code Copilot had ingested was only made with OSS licenses, then I don't see what the problem is. But as far as I understand, GitHub trained Copilot on any public repository on GitHub, meaning even if it doesn't have a license specified (so the user publishing it still has the copyright to it), then I don't see how it can be OK.
> I checked if it had code I had written at my previous employer that has a license allowing its use only for free games and requiring attaching the license. yeah it does