3 ms·
Releasing under a different name would have the opposite problem. No one would use it because they wouldn't know that it was the MIT license with the attributio
by paxys 5y ago
Releasing under a different name would have the opposite problem. No one would use it because they wouldn't know that it was the MIT license with the attribution condition removed, even if that was exactly what they were looking for.
The 0- convention is also somewhat standard for this category of licenses (like 0BSD).
- eyelidlessness 5y agoNot a problem in actual practice, derivative licenses are commonly identified as such and their slight differences are much easier to explain than the whole of any one original license.
- idealmedtech 5y agoSee: AGPL, LGPL for very popular examples of such modifications
- Jenk 5y agoNeither of which use -0 suffix, however, which I believe to be GGGP's point.
- giancarlostoro 5y agoAGPL adds more constraints, LGPL is probably a slightly better example.
- sq_ 5y agoHa, 0BSD makes me realize they could’ve called it 0MIT, as in “omit attribution.” Would’ve been funny and arguably more understandable.
- forty 5y agoSubmit a PR!
- brian_herman 5y agoI submitted a PR if they dont accept ill just fork and have my own.
- chrisshroba 5y agoThis begs the question, do licenses have licenses?
- remram 5y agoWith "MIT" in the title, this might be a trademark issue. And to answer your question, yes, for example the GPL starts with: > Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
- ksec 5y agoThis is actually a brilliant idea, may be you should submit a PR.
- tedivm 5y agoThe proliferation of BSD licenses is exactly why I use the MIT license for things.