BTW, this wouldn't solve the legal hurdles of Copilot.
The model needs to mention which license the code has, which AFAIK Amazon's competitor to Copilot already does that.
If the outputs of the model are found to be not covered by copyright in the first place due to established legal doctrine [0] then developers will not be liable for copyright infringement.
So the only reason for providing attribution will be as a product feature that some developers might want to use.
I personally don’t list every artist that has used a I-IV-V progression in one of their songs and generally lump it into the recognition that my artistic foundation relies on preexisting culture. But hey, you do you.
[0] https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari...
That is, the way GitHub describes Copilot working might pass as fair use. The way it (sometimes) works in real-life will not.
The outputs will always be a liability for a developer using the tool. So far the outputs are not covered by copyright due to the merger doctrine of the idea-expression distinction.
https://en.wikipedia.org/wiki/Idea%E2%80%93expression_distin...
I don't think an explanation of how it's okay since it's an AI model is going to impress a judge, if the plaintiff shows long passages of verbatim copyrighted code coming out of it.
https://texaslawreview.org/fair-learning/
Here's some relevant case law:
https://en.wikipedia.org/wiki/Baker_v._Selden
https://en.wikipedia.org/wiki/Whelan_v._Jaslow
https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_....
Here's some relevant legal doctrine:
https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari...
https://en.wikipedia.org/wiki/Structure,_sequence_and_organi...
https://en.wikipedia.org/wiki/Idea–expression_distinction
The only thing I can say is that if there is a tool that is consistently outputting copyright protected works that this burden would not be worth it for most people. But as I have yet to see a single output from my own use or from Twitter that would pass the filtration test I am not worried about my personal liability.
Not at all.
The reason for providing attribution is to create a incitement for anyone to even publish their work as FOSS in the first place.
We even put it explicit in our LICENSE files.
MIT license:
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
BSD 4-clause:
> Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
When working at Google, developers generally open-source their private projects (which are legally owned by Google) under a Google umbrella, with a Google copyright. This rarely stops developers. When I worked there, my incentive was to make my work more useful and give something back. I'm pretty sure many other Googlers feel the same way.
If Github found another way of making my work more useful to others, all the better. I would prefer if Copilot wasn't the only option, and if there was a good open-source alternative, but that's completely independent of the fact that my code was used to teach a neural network how to complete code snippets.
What? You think people only develop open source simply to have attribution? Personally I publish open source because I made something others could use and I don't want them to waste time duplicating effort. I don't even care whether they list me or not, it doesn't factor into my decision to open source at all.
I agree that if SSO [0] didn’t exist that it would create poor incentives for open source software but that is not what these tools accomplish. They are the poetic equivalents of rhyming dictionaries. Should I figure out everyone that has rhymed “book” with “look” when I publish a new song?
[0] https://en.wikipedia.org/wiki/Structure,_sequence_and_organi...