I apologize for using a term that is derisive. I'd be fine if contributing back was the only requirement. The other terms however at the very least inconvenienc

I apologize for using a term that is derisive. I'd be fine if contributing back was the only requirement. The other terms however at the very least inconvenience developers in how they build and deploy applications, and at worst simply exclude entire platforms. Therefore, I disagree that LGPL is 'the best' for contributing back because the MPL maximizes utility and potential targets. On the other hand with the additional LGPL terms, I don't see how they improve the 'contributing back' part. They instead extend additional user level freedoms which in my opinion are orthogonal to contribution. I'm not starting a permissive/restrictive flamewar here, both the MPL and LGPL have a very similar flavor so I think its fair to compare them. Most developers I know use the LGPL only because they want any improvements contributed back and not because they want to restrict linking or platforms. Plenty of LGPL libraries come with linking exceptions, and lots of devs don't even know about potential platform limitations.