[development] Modules that integrate non-GPL PHP apps violate theGPL.
gerhard at killesreiter.de
Thu Aug 30 19:46:57 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Boris Mann schrieb:
> On 8/30/07, Gerhard Killesreiter <gerhard at killesreiter.de> wrote:
>>>> its purpose is to make a single
>>>> unit of software out of those parts.
>>> Don't agree. The purpose is to loosely couple two separate pieces of
>>> code (for licensing, code maintenance, or 1000s of other reasons). Do
>>> you want me to put a web services interface in between just to jump
>>> through hoops?
>> [x] SEND PIX!!!^1
> As you know, I'm totally in favor of GPL everywhere....I just see it
> as unnecessary hoop jumping because of this IMHO arbitrary shared
> address space business.
Well, you need to draw a line _somewhere_.
> basically, I just don't have enough time to
> re-write *everything* as GPL :P
> In any case....it's really more of an FYI....if people stick stuff in
> Drupal CVS, it's GPL'd. What this causes after the fact is not our
Well, that's not so easy. We are distributing the stuff in our cvs by
making nice little packages from it. If distribution of this code
violates the GPL we might actually lose the right to run Drupal on
drupal.org since we are breaking our own license. ;)
This is of course a rather important problem for me as the CVS
maintainer. There are currently 146 modules that list "3rd party
integration" as their category. Most of them are probably ok, but a few
might be problematic. But alone looking at all of them will be a huge
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the development