nanogui: Re: [linuxce-devel] Re: Microwindows plans
Subject:
Re: [linuxce-devel] Re: Microwindows plans
From:
"Bradley D. LaRonde" ####@####.####
Date:
12 Oct 1999 02:03:52 -0000
Message-Id: <024801bf1455$108dd710$b8119526@ltc.com>
----- Original Message -----
From: Greg Haerr ####@####.####
To: Bradley D. LaRonde ####@####.####
Cc: ####@####.#### ####@####.####
Sent: Monday, October 11, 1999 9:46 PM
Subject: Re: [linuxce-devel] Re: Microwindows plans
> : 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.
>
> This means that we have to be careful about allowing GPL only code in the
> project, doesn't it? As then a portion of the project becomes GPL only.
> I appears that we can only allow code in the project that will be dual
MPL/GPL.
I don't mind allowing GPL-only code into the project, but yes, the parts
that are GPL-only can't be used in other proprietary projects.
Regards,
Brad
