c_xong {l Wrote}:Sorry, just because you don't like copyright and lawyers doesn't mean you're not affected by them. Your licenses have problems and that will discourage many people from using your code as a result. When non-lawyers write licenses, it's the same as if non-programmers write code - it's going to be broken. I suggest you read up on bad licenses like the "JSON evil license" for what kind of problems that may cause.
Julius {l Wrote}:I split this off, as it is really a different topic. But yes... really don't make your own "license"... you might not like certain aspects, but a standard license is still always much preferable over a custom "license". If it isn't a standard license, most people will put it (justifiably) in the same category as "meh what ever" releases.
hathor {l Wrote}:I am more interested in communicating my intentions clearly to the end user than I am worried about getting sued.
But the bit in all-caps is not about threatening to sue the person using the work, it's about protecting the original author.To me, licensing schemes should have more of a handshake vibe than a "see you in court" vibe.
c_xong {l Wrote}:No, don't change the case of the license. The uppercase has legal significance, so you're effectively changing the license if you do that: http://opensource.stackexchange.com/que ... n-licenses
I don't really understand this aversion to all-caps; it's a legal document, not something you read for your pleasure.
Akien {l Wrote}:There's a lot of capslock legalese in Unlicense...
Users browsing this forum: No registered users and 0 guests