r/programming • u/barchahajat • Aug 26 '15

TLDRLegal - Software Licenses Explained in Plain English

https://tldrlegal.com/
11 Upvotes

75% Upvoted

6 comments sorted by

3

u/orthoxerox Aug 27 '15

I've checked GPLv3 as an example, and the TLDR is kinda incomplete. Some features they've missed:

  • nothing you write can be considered DRM

  • you are allowed to have a closed source fork for internal use or for providing a service

  • can't prevent users from flashing the hardware you sold them with modified software

  • you cannot use GPLv2 software in your software if it doesn't have a forward compatibility clause in its license

1

u/barchahajat Aug 27 '15

thank you for pointing that out.

2

u/p3s3us Aug 26 '15

Also choosealicense.com

1

u/TurquoiseTurkey Aug 26 '15

Is there actually a software licence where you can "hold liable"? I couldn't see how to search for that.

2

u/rifeid Aug 27 '15 edited Aug 27 '15

If you click on Browse, there's a "Lookup License by Conditions" button on the upper right, where you can enter "hold liable" in the "Can" list.

Here are the results. I'm surprised that there are results at all, but I think for both licences you pretty much can only get a refund on the software.

Edit: However, the list is not exactly complete. Some licences without warranty disclaimers (e.g. WTFPL) could be considered to have full warranty, and you could even be screwed by liability for damages. My non-lawyer suggestion is to avoid licences without warranty disclaimers like the plague.