nanogui: Re: [linuxce-devel] Re: Microwindows plans


Previous by date: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Next by date: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Previous in thread: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Next in thread: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr

Subject: Re: [linuxce-devel] Re: Microwindows plans
From: "Bradley D. LaRonde" ####@####.####
Date: 12 Oct 1999 01:52:00 -0000
Message-Id: <022e01bf1453$6918fe70$b8119526@ltc.com>

----- Original Message -----
From: Greg Haerr ####@####.####
To: Bradley D. LaRonde ####@####.####
Cc: ####@####.#### ####@####.####
Sent: Monday, October 11, 1999 9:32 PM
Subject: Re: [linuxce-devel] Re: Microwindows plans


> In order to use that our project will
> : need a GPL license, so I think that means dual MPL/GPL instead of
> : convertible.
>
> What's the difference between dual and convertible?

Here's my interpretation: dual means both licenses are simultaneously
availabe, while convertible means that you have to give up MPL to get GPL,
and then can't go back.

I think if we freely want to mix with GPL code, our stuff has to have a
persistent GPL license along side of the MPL license.

That way, we can mix in GPL-only code freely, and others can use our dual
code (but not the mixin GPL-only parts) in other MPL or even proprietary
projects.

Regards,
Brad


Previous by date: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Next by date: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Previous in thread: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr
Next in thread: 12 Oct 1999 01:52:00 -0000 Re: [linuxce-devel] Re: Microwindows plans, Greg Haerr


Powered by ezmlm-browse 0.20.