1) A cleanup of the license policy of the project is needed
2) A file by file license is more appropriate for the project.
You may not get a choice, depending on the status of the code which makes it up :-)
If the code has been modified from the original code in a manner that makes it specific to the project, or a new, mostly original, source file is created that contains parts of another original source file, and then a license (MPL/GPL/ and possibly LGPL) is applied to the file that pertains to the project as a whole, how is it a new license with respect to the original code when the end user has the option of using the modified code (in whole or part of) under the license the original source was distributed with?
The end user still has the option of using the relevant original source under the terms it was originally released under,
But that's not the problem. The problem is that (some of) the original source is now available to be distributed under MPL terms, and the original authors did not give that permission. They said "you can distribute this under the GPL, and only the GPL."
It's not a case of subtracting permissions you're not allowed to subtract, it's a case of adding permissions you aren't allowed to add.
Gerv _______________________________________________ mozilla-license mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-license
