3 ms·
> As we mentioned, GitHub trains Copilot on numerous pieces of public code, many of which are covered by strong copyleft licenses (i.e. GPL v2, GPL v3). Copylef
by wolverine876 5y ago
> As we mentioned, GitHub trains Copilot on numerous pieces of public code, many of which are covered by strong copyleft licenses (i.e. GPL v2, GPL v3). Copyleft licenses require that derivative works (of the copyleft-licensed code) must carry the same license as the original code.
Even when no GPL v2/3 code is quoted by Copilot, is using the code for training a non-free product allowed under the license? Under the license, is Copilot therefore now licensed GPL v2/3? The GPL code was certainly used to create a critical, integral part of Copilot, and to create its output.
If I understand correctly, GPL v2/3 were designed to prevent non-free products from being parasites on FOSS code, taking and not giving. If that's the spirit of GPL, Copilot seems to clearly violate it.
- invokestatic 5y agoWhen you upload code to Github, you agree to license it to them under Github's terms, and not whatever license the software is typically distributed under. You are effectively "dual licensing" software by uploading it to Github, whether you realize it or not. Of course, there are edge cases in which you don't have the rights to license the software to Github, but in those cases, I don't have the answer.