>>
|
No. 1802
[Edit]
>C) ensure, that your code isn't stolen by big corporations without credit.
The GPL may help prevent this, but the Four Essential Freedoms aren't relevant to this.
>I prefer the CC0, because I don't want to impose artificial restriction on other people.
The FSF recommends against using this for software.
https://www.gnu.org/licenses/license-list.en.html
If you want to release your non-software work to the public domain, we recommend you use CC0. For works of software it is not recommended, as CC0 has a term expressly stating it does not grant you any patent licenses.
The relevant term:
No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.
>I don't see how you lose freedom, when you have only a binary. Of course it's better, when the source code is available, but I don't think there is any harm done, as long you can do with it whatever you want.
It makes it much more inconvenient and difficult to study how it works and to modify it to do what you want it to do (freedom 1). It needlessly wastes users' time, hindering users from doing A and B that you mentioned above. That is harmful.
>ISC/Clause-2 BSD/MIT still impose artificial restriction, that are, in my opinion, needless and hence harmful.
Then you could try the 0BSD (actually modified ISC) or MIT-0 licenses, which remove these artificial restrictions and are also considered to be public-domain-equivalent. You can also release your works under multiple licenses so that users can choose whichever one works for them.
Message too long. Click here to view the full text.
|