3 ms·
Parent's post explicitly listed FSL as a possible solution. We also recently adopted it in our startup. (Edit to add: I think his beef with FSL is just that it'
by senko 2y ago
Parent's post explicitly listed FSL as a possible solution. We also recently adopted it in our startup. (Edit to add: I think his beef with FSL is just that it's not OSS. I like the "fair" term as sort of in-between commercial and FOSS).
Agree that if non-lawyers (or corporate lawyers with no experience in open source licensing) craft something, they might regret it down the road. Better to pick and choose between now plethora of available options.
- gavinhoward 2y agoI have no beef with FSL. FSL is totally fine. I would just prefer to have more liability protection.
- the_mitsuhiko 2y ago> I would just prefer to have more liability protection. Would be curious what you have in mind. The FSL comes with a default no warranty disclaimer.
- gavinhoward 2y agoSpecifically, a disclaimer of duty. https://yzena.com/yzena-noncommercial-license/#no-duty https://yzena.com/yzena-noncommercial-license/#no-duty . For why, see questions 33-36 at https://yzena.com/yzena-noncommercial-license-faq/ https://yzena.com/yzena-noncommercial-license-faq/ .
- the_mitsuhiko 2y agoI'm not a lawyer but I think licenses like this have a potential to be very problematic. Even the termination clause of the GPL has turned out to be challenging and primarily is not an issue because it's being ignored / re-instantiated despite the license text. If a court however would ever rule on this, that might be problematic. (Also the fact that this license was not written by a lawyer in itself seems … less than ideal)
- gavinhoward 2y agoThat is why I need lawyer money. But I have actually gotten halfway with a lawyer. A lawyer actually wrote the No Duty clause.