I thought this was a pretty good thread (by an ex-Wikipedia lawyer) on Twitter about the IP meaning of Copilot. https://twitter.com/luis_in_brief/status/1410242882523459585... And this is a longer article about how IP and AI interact: https://ilr.law.uiowa.edu/print/volume-101-issue-2/copyright... I am not a lawyer, but I am capable of summarizing the thoughts of lawyers, so my take is that in general, fair use allow…
> As a human, I am allowed to read copyrighted code and learn from it. Of course not. Reading some copyrighted code can have you entirely excluded from some jobs - you can't become a wine contributor if it can be shown you ever read Windows source code and most likely conversely. Likewise, you can't ever write GPL VST 2 audio plug-ins if you ever had access to the official Steinberg VST2 SDK. Etc etc... Did people fo…
That's not a law. That's a cautionary decision made by those companies or projects to make it more difficult for competitors to argue that code was copied.
Those projects could hire people familiar with competitor code and assign them to competing projects if they wanted. The contributors could, in theory, write new code without using proprietary knowledge from their other companies. In practice, that's actually really difficult to do and even more difficult to prove in court, so companies choose the safe option and avoid hiring anyone with that knowledge altogether.
Now the question is whether or not GitHub's AI can be argued to have proprietary knowledge contained within. If your goal is to avoid any possibility that any court could argue that GitHub copilot funneled proprietary code (accessible to GitHub copilot) into your project, then you'd want to forbid contributors from using CoPilot.