Then you shouldn't release it under the MIT license, which has restrictions and requirements on speech. You have to release it to the public domain. Pretending MIT doesn't dictate terms under which you can release your own software is just a fantasy.
But please don't forget about the users. Only the copyleft licenses guarantee (legally) that the user gets to enjoy the freedoms, too.
MPLv2 is copyleft, but not "viral": so you can use an MPLv2 dependency just like if it was MIT, but if you modify it, you have to distribute the changes.
Especially in a modern day and age where agents are more powerful when they can quickly privately vendor a dependency, patch it, and move on, with zero political ceremony or fuss, MPLv2 feels like an anachronism.
> except if they want to benefit from patching code they didn't write without contributing back. But I don't think we should encourage that.
The spirit of free, open-source software is that you are free to do as you like with the software, no matter who you are. It somewhat boggles my mind that people will hold up licenses like GPL that do not forbid military use, it's totally fine if you deploy GPL software in war, because we wouldn't dare tell you what you may or may not do with the software.... unless you want to make changes to the software, in which case, see you in court!
If you don't modify it, it behaves exactly like MIT. If you want to modify it but not maintain a fork, you can contribute upstream. Or you distribute the sources, which does not require a public repository.
But mostly, why would I care about companies making profit by using my code privately? As an individual, what I care about is being able to fix the devices I own. And copyleft helps with that.
> unless you want to make changes to the software, in which case, see you in court!
Right. So you don't really understand how GPL works, do you? GPL requires you to distribute the sources to the users. It does NOT, at all, require you to make the changes publicly available. So GPL works really well for the military: if you sell a product to the military that contains GPL code, you just have to distribute the sources to them. It's actually better for the military as well! It's better for all the users.
Also you can not mix propriety code that you don't own with GPL which is also a showstopper in many cases.
Yes that's correct. Which makes GPL viral, but not MPLv2. My point was that while I understand how GPL may be too much for companies, I don't think MPLv2 would be.
I have been in big companies that were fine with using (properly) LGPL and MPLv2, by the way.
> Also you can not mix propriety code that you don't own with GPL which is also a showstopper in many cases.
I am not sure I understand that. You can mix proprietary code with GPL, the licence has nothing against that. What you cannot do, though, is distribute proprietary code you don't own and don't have a right to distribute. But that's independent from GPL.
Say you use some software to provide data you host to end-users. Say that software relies on some system package or architecture that isn't available on your server, so you make minor changes and rebuild it to run.
Now if you wanted to make a proper change to the software to accommodate different target architectures/packages, you'd do things very differently; you'd write some check and delegate to the provided apis based on that.
But you didn't do that, you did a find and replace.
This has no value to anyone else, and it also reveals internal information about your system that you may not want to reveal.
I know that many people would disagree with me on this, but thankfully I'm free to choose what license I consider "free".