If you really don't care about the license, just use MIT. It has the best combination of simplicity, compatibility with every other license, and it's already known and used in just about every collection of any sizeable amount of free or proprietary software.
Trying to go even further by using a weird, probably not legally enforceable declaration like this one, or other oddball things like public domain dedications, the Unlicense, the WTFPL, or CC0 is just likely to lead to more confusion, more problems with legal ambiguities in different jurisdictions, simply more time spent reading and evaluating the licenses to make sure there's nothing hidden or that it does have legal meaning in your jurisdiction, etc.
Yes, there are a few prominent examples of public domain dedication that are widely used, like SQLite. They make it work out by actually having all contributors sign an affidavit, and additionally charging a fee for people who really do want or need a license rather than the public domain dedication. Thus, being public domain is actually more work and more friction for the project than if everyone just licensed their contributions under a permissive license like MIT.
(Apropos of nothing, I generally prefer the BSD-2 clause license to the MIT one because I think it's clearer and easier to understand, but they're fundamentally equivalent.)
> I'm here to write code
Exactly. So why not just add a brief MIT license [1] to your code, painlessly clarifying your legal stance?
Yes.
> Exactly. So why not just add a brief MIT license [1] to your code, painlessly clarifying your legal stance?
Because that does not clarify my legal stance at all. My legal stance is that code does/can/should not have a license and that no license is necessary to use any code. I feel like adding a license (even a permissive one) undermines this very idea.
The only people who insist on a license are exactly the people that this form of protest is meant to oppose.
Is this an aspirational stance? Because at the moment that's not what the law says (in any country I know of) and simple licenses like the MIT are probably the easiest way to legally say that you're allowing any use the recipient likes.
If the argument is that everyone should be free to use whatever code however they want, then MIT lets delivers on the "however", but not the "whatever". GPL slightly limits the "however", but delivers on some of the "whatever" due to its viral nature.
Obviously.
> Because at the moment that's not what the law says (in any country I know of) [...]
True. But that's also why I'm unwilling to play along and express my views on the matter within a framework that I perceive to be immoral and wrong.
Adding a free license isn't something you do to appease lawyers, it makes the principles you profess to hold into a reality rather than a trap.
Your comparison with the freeman on the land / sovereign citizen line of thinking made me reflect on my own views on the subject, as these people are obviously nutjobs. However, I view my approach as a valid act of civil disobedience with no ill effects for anyone involved.
I think the ownership of physical items is an intuitive concept that comes naturally from the scarcity of such items.
Code, algorithms or ideas on the other hand are not scarce and I think that the legal framework that makes it possible to own such immaterial things is immoral.
By doing so, he doesn't give up any (exclusive) rights he has as an author. It's not the best from a user's perspective, but it's the simplest and most conservative from an author's perspective (short of not releasing the code at all).
Could you please expand on this a little bit ? CC0 is not only public domain dedication, it has terms for "when public domain dedication isn't possible, here's a list of things that are possible"
See OSI's comments on why it hasn't been approved here -
And using an existing widely known license has benefits, as in what is unlicense? This is the first time I hear from this, but I'm pretty used to deal with MIT licensed software.
Some licenses, like GPL/AGPL/LGPL, has been written by teams of lawyers to ensure protection for developers and users against lawsuits and patents. Other licenses has been written by people with no legal background.
So I can understand why some people do act like that.
If people believe that Software Should Not Have Owners, they should use the GPL.
djb did, before he released everything (or practically everything?) into the public domain. Look for my other comment thread to see the practical results of that.
Very well, I want an exclusive license, meaning I'm the only person who can use this software. Also perpetual, of course, so the license never expires. And don't forget to indemnify me. But don't bother indemnifying yourself, so I can sue you if the software doesn't do everything I ever dreamed. And...
(I'm being sarcastic here. My point is that you can't get away with not licensing your free software, or saying the equivalent of "I don't care." It's not like there's a dearth of free licenses to choose from.)