I feel like MPL2 does that just as well, but by adding a file-level firewall ensures that it will gain adoption among people/organizations who need to be able t

I feel like MPL2 does that just as well, but by adding a file-level firewall ensures that it will gain adoption among people/organizations who need to be able to distribute it in a binary along with other code that has another license. This way people still add features and upstream bugfixes, but a) it doesn't get forked to hell like the 200 Linux kernels that each Android manufacturer has to publish and b) you get much wider adoption faster, with more people being paid to fix bugs and add features to your code because it is being used alongside proprietary code. Sure, it doesn't give you a nice stick-it-to-the-corporations dose of righteous satisfaction, but it feels to me far more pragmatic, and healthy for the project in the long run.