|
|
Log in / Subscribe / Register

Class action against GitHub Copilot

Class action against GitHub Copilot

Posted Nov 14, 2022 22:17 UTC (Mon) by Wol (subscriber, #4433)
In reply to: Class action against GitHub Copilot by LtWorf
Parent article: Class action against GitHub Copilot

" including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,"

You clearly didn't read the thread you pointed at.

The MIT licence allows SUBlicencing, ie applying other terms on top. According to your thread, there is no such thing as relicencing, certainly I've never seen that in any legal document.

And as I understand English, RElicencing means throwing out the old licence, and replacing it with a new one. No open source licence I've come across allows any such thing. As I understand the meaning of the word "relicencing", in practice this has precious little difference from handing over the copyright.

And that's also why/how you can extract the original code under the original licence. If it had been RElicenced, you wouldn't be able to get the original licence back.

Cheers,
Wol


to post comments

Class action against GitHub Copilot

Posted Nov 15, 2022 23:46 UTC (Tue) by NYKevin (subscriber, #129325) [Link] (2 responses)

I'm not sure "relicensing" is even a thing in legal terms. Let's clarify a few ideas. Suppose we have some software that was written by person A. A gives a copy to B, and B gives a copy to C. Then:

* With both the GPL and the MIT license, A automatically extends a license to each person who obtains a copy of the software, by whatever means. In our example, this means that A gives a license to B and to C.
* With the MIT license, B may optionally give a different license to C (or, in principle, the same license, but that would be kind of pointless). This is called a "sublicense." It does not extinguish the original license, so C can decide which license to comply with. However, as a general rule in most jurisdictions, the sublicense cannot be broader than the rights that B already enjoys under the MIT license in the first place - you can't give what you don't have.
* In the context where the sublicense is the GPL, C is still required to comply with the MIT license's formalities. Obviously, B is also required to comply with those formalities. In practice, this is usually done simply by copying the copyright and license into a comment at the top of the file, but there are other ways of complying. If you're distributing binaries, you might need to take additional measures to ensure a copy of the license is still visible somewhere.
* Under the GPL, sublicensing is forbidden - C can only get the license directly from A. A and C never need to communicate in order to do this. The license, as mentioned above, springs into being automatically as soon as C has a copy of the software, regardless of how A or B may feel about that. I'm pretty sure the FSF did this to prevent B from placing "additional restrictions" on the sublicense.
* In principle, we could imagine a license which does not have this automatic property, where all rights have to be conveyed by explicit sublicensing (sort of the inverse of how the GPL works). This is inconvenient, so nobody does it in the FOSS world, but I imagine it's more common in environments where permissions are more closely guarded.
* We could also imagine a license which terminates as soon as you accept a sublicense from somebody else. This would make sublicensing have the effect of extinguishing the original license, and allow intermediaries to restrict downstream users' rights via clickwrap licenses. Again, this is unheard of in the FOSS world, but to my understanding it is not unlawful. I suppose you could call that operation "relicensing," but in practice, I don't think this is really a thing that anyone does.

Class action against GitHub Copilot

Posted Nov 16, 2022 5:50 UTC (Wed) by unilynx (guest, #114305) [Link] (1 responses)

I’m not sure anything of this works this way for a sub license from B to C if B is just providing a copy

The license is a promise not to sue for copyright infringement providing you follow certain requirements.

C has the same rights as B in your case no matter what B said, as B has no standing to sue for copyright infringement as he does not have any copyright.

(Unless A specifically provided the product to B with the understanding that the MIT license would only be valid to B)

Class action against GitHub Copilot

Posted Nov 17, 2022 19:48 UTC (Thu) by NYKevin (subscriber, #129325) [Link]

As I mentioned, C can decide which license to comply with. In the scenario you describe, C would (probably) choose to comply with the license provided by A rather than the sublicense provided by B, so B's sublicense has no legal effect and may as well not exist. Thus, this is a distinction without a difference.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds