3 ms·

> I think the argument for why it’s copyright violation today is pretty compelling. I still don't see how there is any footing for a copyright infringement cla

> I think the argument for why it’s copyright violation today is pretty compelling. I still don't see how there is any footing for a copyright infringement claim here, given that users who put public code on github.com explicitly grant GitHub a license to use that code to provide services to other GitHub users. that license grant is above and beyond what any specified license terms the repo itself grants to users of the code. you literally grant GitHub the right to do this when you put your code on github.com.

vineyardmike 4y ago
Actually no you don’t. The ToS is obviously long, but it’s surprisingly human readable and tech friendly (eg they have verbiage on reproduction of your content for search indexing). Relevant snippet: > you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you adopt a license. They key parts are the “through GitHub” portion. GitHub is being careful to not give people rights to your content beyond the right to view it through GitHub. Performance refers to multimedia like music and video assets (according to others parts I didn’t reproduce). No one is gaining a license to use your code through the inclusion on GitHub. Section D is the relevant section. https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#d-user-generated-content https://docs.github.com/en/site-policy/github-terms/github-t...