[development] Modules that integrate non-GPL PHP apps violate the GPL.
pwolanin at gmail.com
Sun Sep 9 00:12:59 UTC 2007
Can I again suggest that the most pragmatic change would be to license
core under "GPL 2.0 or any later version". Moving to only 3.0 would
be a mistake, since there are contrib modules and other open source
projects that may stay as GPL 2.0 only.
On 9/8/07, Thomas Barregren <thomas at webbredaktoren.se> wrote:
> I agree that we first of all should boot code that links to code and
> call functions and share data structures with another code which has a
> licnse not compatible with GPL. But we should of course not boot code
> that use another code using GPL compatible license (e.g. BSD, MIT and LGPL).
> The second most important thing we can do is to use GPL v3 instead of
> GPL v2. By doing so, many more licenses, most notable Apache, is
> compatible with GPL.
> Best regards,
More information about the development