We've filed a lawsuit against GitHub Copilot

Re:We've filed a lawsuit against GitHub Copilot by Etheryte on Thursday November 03, 2022 @05:40PM (#33458107)

> Your code is open source - irregardless of license, one might read it as a text book and then remember or even copy snippets and re-use this somewhere else unrelated to the original application.

Yes, but attribution should still be given. Just because you don't copy-paste someone else's creation doesn't mean you're licensed to use it.

[ Parent | on HN ]

Re:We've filed a lawsuit against GitHub Copilot by shagie on Thursday November 03, 2022 @05:49PM (#33458244)

Is it the role of the tool (in this case copilot) to include the license information? Or is it the responsibility of the organization using the code to make sure that it wasn't copied from somewhere?

What if, instead of a tool, you had a random consultant do some work, and it was found out that he asked a ton of stuff on Stack Overflow and copied the CC-BY-SA 4.0 answers into his work? What if it was then found out that one of those answers was based on copying something from the Linux kernel? Who is responsible for doing the license check on the code before releasing the product?

[ Parent | on HN ]

Re:We've filed a lawsuit against GitHub Copilot by alpaca128 on Thursday November 03, 2022 @06:44PM (#33458990)

> Or is it the responsibility of the organization using the code to make sure that it wasn't copied from somewhere?

Do you know whether the code you got from Copilot has an incompatible license? No, so if you plan to use Copilot for serious projects you need it to include sources/licenses either way. In fact that would be a very helpful feature as it would let you filter licenses.

[ Parent | on HN ]