Ben Bucksch wrote:
> Hi Mitchell, hi Frank,
> 
> is the following addition to the MPL/GPL/LGPL boilerplate OK for new 
> files in existing Seamonkey modules ("Mozilla.org code"), reflecting the 
> fact that I'm not AOL ;-P ?
> 
> Quick answer appreciated, since I'd like this code to get into 1.0.
> 
> Thanks in advance.
> 
> Ben
> 
> /*
>  * Unlike stated in the License, this License shall be governed by
>  * German law provisions. Any litigation relating to this License shall be
>  * subject to German jurisdiction.
>  * Once Covered Code has been published under a particular version of the
>  * License, You may always continue to use it under the terms of that 
> version.
>  * The Initial Developer and no one else has the right to modify the terms
>  * applicable to Covered Code created under this License.
>  */

Essentially you're changing the MPL, creating a derivative of it. This is
allowed under section 6.3 but with the requirement that you not call it the
Mozilla Public License anymore. So now you have the Beonex Public License.
Since the terms are compatible with the MPL it's not going to cause
distributors any problems, but [EMAIL PROTECTED] would have to approve its
use in the tree.

There have been a lot of derived versions of the MPL whose sole purpose is
to change the things you have changed, and so far each has given itself a
new name and added to the crowd of open source licenses. It would have been
nice if there were some approved way to parameterize these points just as
the Initial Developer and Original Code are parameterized in Exhibit A (this
was raised long, long ago), but currently there is not.

-Dan Veditz

Reply via email to