4 ms·
I think my comment makes it clear that I assumed (correctly) that you did not mean "only BSD", but all the similar licenses (e.g., MIT). Your second paragraph
by cryptonector 8y ago
I think my comment makes it clear that I assumed (correctly) that you did not mean "only BSD", but all the similar licenses (e.g., MIT).
Your second paragraph above is unclear as to which licenses businesses won't accept, or why.
In my experience businesses do not accept:
- copyleft'ing in any code that could be integrated into proprietary code that might be distributed to customers
- advertising clauses (not all BSD licenses have these)
- or any clauses that are onerous in any way (the above two are onerous)
(I'm not addressing trademark or patent issues here, just copyright. Obviously code distributed under a friendly license but requiring non-free patent grants is generally out.)
I'm not sure what you mean by "personal work", but I get the feeling that you mean "not easy to monetize" or "impossible to monetize". Why would you use the GPL for such work? Why would anyone make significant changes to software that can't be monetized and not share alike even without being required to by a GPL-like license? I would absolutely prefer BSD (sans advertising clause) or MIT licensing for "personal work", and I would absolutely recommend it.
- kemitchell 8y agoMany businesses blacklist FPL/0BSD, Unlicense, and especially WTFPL. Those that blacklist CC0 for software do so for patent-related reasons, and not, in my experience, because it's styled a public domain dedication. CC0 actually includes an extensive license, as fallback if dedication doesn't work. When I wrote "personal work", I meant work for which the developer has control of licensing. Not code for an employer or client with their own licensing policy.