News for hackers. Stuff that matters.
Re:New GitHub Terms of Service require removing many open-so... by Lazare on Wednesday March 01, 2017 @08:32PM (#13770610)
But in that case, you've never been able to upload code to github, right?
Re:New GitHub Terms of Service require removing many open-so... by caf on Wednesday March 01, 2017 @09:07PM (#13770799)
Not necessarily. If the license allows you to redistribute the code, you're just redistributing it to GitHub, and you're OK as far as the software license goes.

If GitHub then does things with that code that the license doesn't allow, it was GitHub that is doing something it's not allowed to - unless, as uploader, you've agreed to indemnify GitHub for this sort of thing.

Re:New GitHub Terms of Service require removing many open-so... by comex on Wednesday March 01, 2017 @08:50PM (#13770700)
It may be the case that what the license permits (combined with fair use law) is sufficient to allow what GitHub actually, currently does with the code, but not everything their TOS claims the right to do.

In particular, "store and display your Content [..] as necessary to render the Website and provide the Service" is rather broad given that the functionality included in the "Service" (defined as "the applications, software, products, and services provided by GitHub") can change at any time, without notice.

Re:New GitHub Terms of Service require removing many open-so... by vsl on Friday March 03, 2017 @02:39AM (#13781347)
Wrong. My OSS project has over 15 years of history, uploaded to GitHub after migration from SF.net. It has third party dependencies that I use under their licenses - which often do require attribution.