4 ms·
No thank you. My licenses are my choice. For my open source libraries, I use the Unlicense, because I want to minimize licensing friction. But if I'm distribut
by ekidd 12y ago
No thank you. My licenses are my choice.
For my open source libraries, I use the Unlicense, because I want to minimize licensing friction. But if I'm distributing (say) a complete end-user application that represents programmer-years of work, I'm likely to use the GPL, because I may not want somebody to fork it and make it proprietary. It's my code and my decision.
If you want to use my GPLed code in your proprietary product, you can find my email address and pay my company an appropriate license fee. And if you think this is somehow unfair, my wisest course of action is probably to avoid doing any business with you: You're raising all kinds of "horrible customer" warning flags.
- MetaCosm 12y agoRandom aside about Unlicense. Unlicense depends on two core ideas that are not anywhere near universally applicable... public domain and relinquishment rights. This makes unlicense a non-starter in Germany, and most likely completely invalid in Australia. These issues are why SQLite offers special licenses (http://www.sqlite.org/copyright.html http://www.sqlite.org/copyright.html) -- and the SQLite license was the inspiration for Unlicense. My point is -- Unlicense doesn't do too much to minimize license friction and actually creates complicated international issues. I don't use it -- because I don't want to have to hand out "special" licenses based on where my users live.