Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Santa_Cruz_Operation They were a partner with Microsoft maintaining a version of Xenix
That doesn't imply ownership and the article [20] that you pointed out doesn't make a specific claim. All good, but MSFT never fully owned or operated SCO at any level is the point I'm trying to make.
Copilot sells code other people wrote
831–838 of 838 posts
Re: Copilot sells code other people wrote
#832Pretty soon the world is going to come to realize art/creation is just blending, incrementing and repurposing prior art. No book, painting, codebase, sonnet, design is theft-less. The art is the space reduction, otherwise we’d just bruteforce away.
That applies to everything, its even a basic law of physics, and there's absolutely nothing wrong with it. Any layperson already knows what a remix is anyway so not sure what you think will change
Re: Copilot sells code other people wrote
#833Earlier quoted context omitted.
I sometimes read people's open source code on github and use the ideas from that to develop my own ideas. In fact sometimes I copy and paste short passages and then rework them. I also employ a team of people who may do the same. Is that fair use, yes of course it is. Is co-pilot automating that fair use, I would say so.
What you are doing is very certainly illegal
It reminds me of the Google vs Oracle case. Apparently a court found that copying even a small amount of code in breach of its licence is not permitted. [0]
[0] https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_.... (ctrl-f for de minimis)
Re: Copilot sells code other people wrote
#834Earlier quoted context omitted.
They’re not selling you code. They’re selling you an engine that helps you find the right free code at the right time. If you read free code yourself it’s fine, but if a machine does it for you it’s not? We overvalue humans.
> If you read free code yourself it’s fine, but if a machine does it for you it’s not? We overvalue humans. No, it's not fine. Apparently, you missed SCO & Oracle vs. Google cases. Both of these cases argued that somebody looked to the code, and copied it. In SCO case it was not true, but the argument stretched the timeline rather successfully. In Oracle vs. Google, copying function signatures opened a big can of wor…
Re: Copilot sells code other people wrote
#835Earlier quoted context omitted.
> If you read free code yourself it’s fine, but if a machine does it for you it’s not? We overvalue humans. No, it's not fine. Apparently, you missed SCO & Oracle vs. Google cases. Both of these cases argued that somebody looked to the code, and copied it. In SCO case it was not true, but the argument stretched the timeline rather successfully. In Oracle vs. Google, copying function signatures opened a big can of wor…
I suppose you learned to code without reading any code?
On the other hand, this is irrelevant to the issue at hand.
GitHub copilot is not a tool for education. It's tool for auto-completing code, which can be put to production, where licenses and other stuff come into play.
The issue is not code sharing per se. It's more of a legal problem, and an important one at that. In the software copyright sense, even reading code you can't import to a project (let it be leaked, not compatibly licensed or for any reason), puts you at risk of legal troubles. This is why we have methodologies like "clean room development".
In Copilot's case, you're possibly deriving a code from a source which contains many licenses, and some of them are not compatible with that you're doing. As a result, you're in direct breach of the license which is not compatible with your code.
On a more higher level, you're also breaching the ethics code and morality by using a code or its derivation with an incompatible license to your code, and disregarding other peoples desires codified as a case-tested and valid license.
As a result, if you think that using a derivative of a GPL licensed code in your closed source application is OK on every front, then the vice versa is true. I can disassemble and reverse every part of your code and re-implement it as GPL bug for bug and open it.
Because if you can breach my license, and expect no consequences, I can breach your license without consequences, as well. It's a two way street.
Re: Copilot sells code other people wrote
#836Earlier quoted context omitted.
Well, I hope your viewpoint doesn't win the day, because making code as freely shareable and remixable as possible is a huge boon for humanity.
I feel like you're missing the forest for the trees here - making code freely shareable and remixable is exactly the purpose of GPL and other free-software licenses, but you can bet that the proprietary codebases Copilot will be used in will go out of their way to prevent any such uses of _their_ particular code snippets. IMO, the only way to use Copilot's output in an ethically sound way is to only use the output it…
Re: Copilot sells code other people wrote
#837Earlier quoted context omitted.
Just as a mind experiment: couldn't CoPilot just publish a list of every github user and attribute the work to all of them?
CoPilot is a black box at the moment. Microsoft claims they used the public corpus on GitHub. There are plenty of GPL, AGPL, and "source available" projects in the public corpus. So what exactly is the licensing? The argument may make sense if they limited themselves to public-domain (CC0) works, but that is not what happened here. If CoPilot attributed something to an AGPL project, does it mean the "virality" applie…
Re: Copilot sells code other people wrote
#838Earlier quoted context omitted.
You are making a lot of assumptions about what someone wants/intends when they contribute to open source codebases. If an author chooses, for example, the AGPL, I think they clearly had a different intention. Like it or not, not everyone wants to dedicate their work to the public domain.
Then why contribute to open source if you want to still be a gatekeeper? In that case better to fork it and work in a private repo.