3 ms·
>The ToS changes here grant such a license to all GitHub users, and not just to use site functionality (e.g. hitting the "fork" button). Sure. But if you have
by spott 10y ago
>The ToS changes here grant such a license to all GitHub users, and not just to use site functionality (e.g. hitting the "fork" button).
Sure. But if you have code that has a licence that doesn't allow that... you shouldn't be putting it on Github.
This is the clause you are referring to "If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to access your Content through the GitHub Service, and to use, display and perform your Content, and to reproduce your Content solely on GitHub as permitted through GitHub's functionality." The key words here are "solely on GitHub as permitted through GitHub's functionality." This doesn't appear to be giving users license to do anything with the code off GitHub's site.
- JoshTriplett 10y agoThat is, at best, ambiguous and in need of clearer drafting. The author of the article linked here, and others, are reading the "access" and "reproduce" as only for GitHub, but the "use, display, and perform" as granted to each User of GitHub and not just for use/display/performance through the site itself. The ideal scenario is that the concerns are all drafting errors or otherwise missed details, and can be fixed via clearer drafting of a new version. I don't think there's a systematic intent here to undermine FOSS licensing, just a set of mistakes that didn't take such licensing into account very well.