Live data from Hacker News

GitHub Copi­lot inves­ti­ga­tion

githubcopilotinvestigation.com

21–30 of 1001 posts

Re: GitHub Copi­lot inves­ti­ga­tion

#21

Copyright only covers the expressive parts and not the utilitarian parts: https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari... https://en.wikipedia.org/wiki/Idea–expression_distinction https://h2o.law.harvard.edu/cases/5004 Most of your code is probably not subject to copyright in the first place, regardless of license.

Doesn't Copilot reproduce the exact expression given the right prompt, though?

Re: GitHub Copi­lot inves­ti­ga­tion

#22

Does GitHub not have the right to view and train from your content when you agree to their Terms of Service and upload your code? People are conflating their open source license with the one they give GitHub when making a GitHub account, but they are two entirely separate and parallel licenses. The former is for other people to use your code, the latter is for GitHub to host your code. If you don't like it, you are f…

The current github terms of service don't seem to mention this use when they describe the license granted github.

https://docs.github.com/en/site-policy/github-terms/github-t...

4. License Grant to Us

We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.

This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program.

Re: GitHub Copi­lot inves­ti­ga­tion

#24
post #13

> Microsoft char­ac­ter­izes the out­put of Copi­lot as a series of code "sug­ges­tions". Microsoft "does not claim any rights" in these sug­ges­tions. But nei­ther does Microsoft make any guar­an­tees about the cor­rect­ness, secu­rity, or exten­u­at­ing intel­lec­tual-prop­erty entan­gle­ments of the code so pro­duced. Once you accept a Copi­lot sug­ges­tion, all that becomes your prob­lem: > "You are respon­si­ble…

> Steve Ballmer

They have some really good blow in Redmond.

If anybody could win an award for being coked up and sweaty on stage...

https://www.youtube.com/watch?v=Vhh_GeBPOhs

Re: GitHub Copi­lot inves­ti­ga­tion

#26
post #9
post #2

Doesn't really explain how co-pilot is stealing your community. I've used co-pilot and it works great until you are past boilerplate than it falls apart.

> Over time, this process will starve these com­mu­ni­ties. User atten­tion and engage­ment will be shifted into the walled gar­den of Copi­lot and away from the open-source projects them­selves The author seems to be implying that since Copilot can reproduce the code of open source repository X in certain scenarios there'd be no reason for programmers to learn/use/engage with repository X. But this is silly. Maybe s…

It also doesn't make any sense. Copilot suggesting to me the signature of a function from some library is not actually the same as executing that library. That library still needs to be downloaded onto my computer to be executed. And who will write new features to a library if not for the people who are interested in that?

Re: GitHub Copi­lot inves­ti­ga­tion

#27
post #9
post #2

Doesn't really explain how co-pilot is stealing your community. I've used co-pilot and it works great until you are past boilerplate than it falls apart.

> Over time, this process will starve these com­mu­ni­ties. User atten­tion and engage­ment will be shifted into the walled gar­den of Copi­lot and away from the open-source projects them­selves The author seems to be implying that since Copilot can reproduce the code of open source repository X in certain scenarios there'd be no reason for programmers to learn/use/engage with repository X. But this is silly. Maybe s…

It strips GPL, or any license.

Re: GitHub Copi­lot inves­ti­ga­tion

#28

Does GitHub not have the right to view and train from your content when you agree to their Terms of Service and upload your code? People are conflating their open source license with the one they give GitHub when making a GitHub account, but they are two entirely separate and parallel licenses. The former is for other people to use your code, the latter is for GitHub to host your code. If you don't like it, you are f…

The current github terms of service don't seem to mention this use when they describe the license granted github. https://docs.github.com/en/site-policy/github-terms/github-t... 4. License Grant to Us We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as n…

That mentions everything: Parsing the content, showing it to/sharing it with other users, using it to improve and provide the service. GitHub and all of its features are "the service".

Re: GitHub Copi­lot inves­ti­ga­tion

#29
post #2

Doesn't really explain how co-pilot is stealing your community. I've used co-pilot and it works great until you are past boilerplate than it falls apart.

Agree, the argument seems pretty threadbare. Millions of programmers use open-source software every day and incorporate it into their own projects without ever engaging the authors of the code upon which they rely.

Perhaps the author means that there’s a possibility that the programmer to whom the code was suggested won’t necessarily know its provenance and how to engage the community from whence it came. If so, that’s a stronger argument, but I don’t know that it’s the best one they can make.

Re: GitHub Copi­lot inves­ti­ga­tion

#30

Copyright only covers the expressive parts and not the utilitarian parts: https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari... https://en.wikipedia.org/wiki/Idea–expression_distinction https://h2o.law.harvard.edu/cases/5004 Most of your code is probably not subject to copyright in the first place, regardless of license.

Doesn't Copilot reproduce the exact expression given the right prompt, though?

Even if it does, it may not matter. For example, APIs are not copyrightable (see Google v Oracle), and if there is only one obvious efficient way to make something work, it does not follow that the user must be prohibited from using that way even if someone else did it first.
Post reply on HN