4 ms·
From the mailing list, on using Github: > Plus, in order to use their services, you need to assume liability That sounds bad, as in really bad. One important
by cronjobber 10y ago
From the mailing list, on using Github:
> Plus, in order to use their services, you need to assume liability
That sounds bad, as in really bad. One important function of Open Source licenses is to get as far away from liability as possible.
Do people here know whether that's just a misunderstanding, or a realistic risk of keeping code on Github?
- nerdponx 10y agoJust read through their terms of service, and I don't see anything to that effect. You are responsible for not violating other people's copyright with stuff you upload to GitHub, and GitHub is not responsible for damage, etc. due to service outages. But that's it.
- oceanswave 10y agoI think you're conflating the role of a host and the role of a OSS license. As with most hosts, the issue of liability rests on the owner. I couldn't upload 50gb of pirated movies to github and cry "github save me, I used you and now I need you to protect me." Your software license dictates your liability to users of your code. GitHub is saying we're just a host, and we defer to the software liscensors on how their code should be used
- kriro 10y agoAlso worth mentioning that liability laws can be rather different from country to country. Germany (and Austria iirc) is somewhat notorious in that regard as you can't completely "get rid of" liability and warranty. There's no public domain for example (technically that's still debated but the main opinion seems to be it's not possible for me to release anything as public domain, see §29 UrhG-D).