4 ms·

I think you might find this post interesting, especially the "Attribution Doesn't Mean Credit" section: https://writing.kemitchell.com/2018/08/28/Unhappy-Coinc

I think you might find this post interesting, especially the "Attribution Doesn't Mean Credit" section: https://writing.kemitchell.com/2018/08/28/Unhappy-Coincidences.html https://writing.kemitchell.com/2018/08/28/Unhappy-Coincidenc... You might also like to look at the tools that have been written for front-end JavaScript bundlers, like Browserify and Webpack, that automatically assemble and concatenate license notices. That's not a complete solution for all projects, but it shows what tools can do with workable license metadata. https://www.npmjs.com/search?q=webpack+licenses https://www.npmjs.com/search?q=webpack+licenses

skissane 8y ago
Are you able to explain why one needs a "no warranty" disclaimer on software you are giving away for free? All consumer protection laws I've seen are predicated on a sale, and so I would not expect them to apply to gifts. A warranty is a contract term, an implied warranty is an implied contract term, but if someone distributes open source software without charge, there is no exchange, no consideration, no contract–so how can there be any warranties, express or implied?
- kemitchell 8y ago
  You should get accountable legal advice for any specific project you may be involved in. This is not that. Consider that at least common law countries don’t require payment to honor contracts. They require legal consideration, which can include mere promises in return. Have a look at Jacobsen v. Katzer and more recently Artifex v. Hancom. Both copyright and contract claims. There are other interpretations. I’m not aware of any US case law on warranty claims against open source contributors. I’d expect to see it first in jurisdictions with laws limiting broad disclaimers, like Germany.