The scenario is a project which is a collection of various scripts/code from different original authors which have been modified to work in conjunction with the project as a whole, in much the same way as Mozilla.
Note that depending on license requirements, such a combination is not always possible. The answer to your problem may end up being "just don't use that code, then."
The intent/purpose of the re-license is similar to the reasoning behind Mozilla's re-license, the biggest question being and how or what is the best way to approach this. Based on your answers I imagine the steps taken by mozilla.org in their re-license would be the appropriate course of action.
Be careful before you go down that road. It took us two and a half years to get everyone's permission.
Can a modified version of the original file released under the GPL be re-released under the MPL/GPL dual license without conflict, or would that also fall under the same constraints as the re-license?
You can make your _changes_ available under the dual-license, but not the original code. Making this fact clear would be very complicated, and a recipe for confusion.
Gerv _______________________________________________ mozilla-license mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-license
