[EMAIL PROTECTED] wrote:
>
> We'd like to use the mfcEmbedding code from Mozilla for a Windows
> embedded browser which is GPL'd.
> However mfcEmbed seems to be NPL'd and I recall these two licenses
> being incompatible.
>
> a) Is that true about being incompatible and
Yes, the stock licenses are incompatible. But see below.
> b) would it make sense to publish the embedding samples under a dual
> license MPL/GPL as it might be likely used by other open source
> projects as well?
That's why mozilla.org announced it was going to dual license the codebase,
but it's much harder to do that to say. For one thing there is the
bookkeeping job of finding all the contributors and getting their OK to
change the license on their code, or else we have to rewrite/replace that
section of code in a pretty much clean-room fashion.
The mfcEmbedding shell could be switched easily, but the actual Gecko-plus
engine is large and has many contributors.
There is, however, another way in the meantime, an approach tried by the
Galeon browser I believe. See the section on the Qt license at
http://www.fsf.org/philosophy/license-list.html#GPLIncompatibleLicenses for
wording you could add to your project to smooth over some of the rough spots
in the license compatibility.
This would only work for *your* code. If you link to or compile in GPL'd
code from other authors you'd have to get similar exception permission from
each of them. This is not a complete solution, but may suffice.
-Dan Veditz
