[development] Modules that integrate non-GPL PHP apps violate the GPL.

[Jakob Petsovits]

On Monday, 3. September 2007, Bryan Ruby wrote:
> In some way it's sad that a strict GPL license that helps us keep "free
> code" free prevents us from freely sharing the code we use to connect
> with non-GPL software. The reality is such a variant in the GPL license
> would reflect the "real world" realities that Laura Scott discussed in
> an earlier post (
> http://lists.drupal.org/pipermail/development/2007-August/026167.html )
> and really how Drupal's own open source culture has evolved.

That may be true, but if that is the case then the GPL is simply the wrong 
license for Drupal. My impression is that all the people requesting
"more freedom" (which is a wrong statement in itself because there's obviously 
various opinions on "what software freedom actually is") would rather have an 
LGPL Drupal than a GPL one.

Also (I believe this has been mentioned before), you can't add such a license 
exception without tracking down *all* the copyright holders of Drupal code 
and getting their approval for this license change. (It's really a change, 
yes.)

I find it tiresome to read about license amendments when we haven't even got a 
list of copyright holders. Could we please defer the "license exception" 
discussion until there's proper copyright headers in the source files?
It's impossible to change the license until we've got those.

Thanks,
  Jakob