mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grzegorz Kulewski <kangur@polcom.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: Patrick McFarland <diablod3@gmail.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Anonymous User <anonymouslinuxuser@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Thu, 17 Aug 2006 14:39:24 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0608171410570.14828@alpha.polcom.net> (raw)
In-Reply-To: <20060817080243.GN7813@stusta.de>

On Thu, 17 Aug 2006, Adrian Bunk wrote:
> On Thu, Aug 17, 2006 at 03:32:51AM -0400, Patrick McFarland wrote:
>> Closed source modules are lame, and against the spirit of open source, but
>> that still doesn't make them against the license.
>
> This is _your personal interpretation_ of what consists a "derived work"
> under the GPL.
>
> Other people have other opinions on this issue.
>
> Other people even have asked lawyers that said they'd disagree with
> interpretations like the one you expressed.

Right.

Then why not make some official and only right interpretation of what is 
derived work for GPL2 in Linux and what is not, make it part of license or 
COPYING file and end this type questions, doubts and flamewars once for 
ever?

Why does Linus and others let lawyers and courts decide in such 
(important?) thing like what is allowed in Linux (or with Linux) and what 
is not?

Why not be brave, make the decission (preferably as liberal as possible) 
and end all of this instead of letting others decide (worse: letting 
others decide based on different and changing local, national rights and 
probably also on who is paying them)?

If it would mean changing Linux license (and getting every contributor 
agreement) then it could be made at least as a clear comment ("What is and 
what is not derived work for GPL2 in Linux kernel in opinion of main Linux 
kernel developers?") in the begining of the COPYING file, signed by most 
important kernel developers (that produced 99% of the code and headers 
used or touched by controversial modules anyway).


Thanks,

Grzegorz Kulewski


  parent reply	other threads:[~2006-08-17 12:39 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17  5:48 Anonymous User
2006-08-17  6:14 ` Arjan van de Ven
2006-08-17  9:38   ` Ben B
2006-08-17 12:02     ` linux-os (Dick Johnson)
2006-08-17 16:11       ` Stefan Richter
2006-08-17 19:21   ` James Courtier-Dutton
2006-08-17 23:26     ` Ian Stirling
     [not found]       ` <20060817193540.dc819396.seanlkml@sympatico.ca>
2006-08-17 23:35         ` Sean
2006-08-18  0:32       ` Alan Cox
2006-08-18  7:23       ` Xavier Bestel
2006-08-18 12:23         ` Ian Stirling
2006-08-18  9:04       ` Helge Hafting
2006-08-17  6:42 ` Patrick McFarland
2006-08-17  6:54   ` Arjan van de Ven
2006-08-17  7:32     ` Patrick McFarland
2006-08-17  8:02       ` Adrian Bunk
2006-08-17  9:03         ` Patrick McFarland
2006-08-18 17:56           ` Adrian Bunk
2006-08-17 12:39         ` Grzegorz Kulewski [this message]
2006-08-17 13:41           ` Alan Cox
2006-08-17 13:31             ` Grzegorz Kulewski
2006-08-17 15:52               ` Theodore Tso
2006-08-18  2:03             ` Chase Venters
2006-08-17  8:32   ` Stefan Richter
2006-08-17  9:36     ` Patrick McFarland
2006-08-17 11:25       ` Alan Cox
2006-08-17 11:48         ` Neil Brown
2006-08-17  9:37   ` David Woodhouse
2006-08-17 23:45     ` Ian Stirling
2006-08-18  8:28       ` David Woodhouse
2006-08-18 12:52         ` Ian Stirling
2006-08-18  8:53       ` Bernd Petrovitsch
2006-08-18  9:04         ` David Woodhouse
2006-08-18  9:15           ` Bernd Petrovitsch
2006-08-20 22:05     ` Andrea Arcangeli
2006-08-20 22:20       ` Arjan van de Ven
2006-08-18  9:51   ` David Schwartz
2006-08-18 16:52     ` Alan Cox
2006-08-18 22:42       ` David Schwartz
2006-08-19 10:48         ` David Greaves
2006-08-19 16:29           ` Patrick McFarland
2006-08-19 17:28             ` David Greaves
2006-08-19 11:30         ` Helge Hafting
2006-08-19 15:44           ` Michael Buesch
2006-08-19 23:01           ` David Schwartz
2006-08-20  3:20           ` Chase Venters
2006-08-21  7:58             ` Helge Hafting
2006-08-21 11:27               ` Stefan Richter
2006-08-21 13:06               ` Alan Cox
2006-08-21 14:59               ` Horst H. von Brand
2006-08-17  9:30 ` Alan Cox
2006-08-17  9:29   ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User
2006-08-17 15:52   ` Stefan Richter
2006-08-17 16:19   ` Michiel de Boer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0608171410570.14828@alpha.polcom.net \
    --to=kangur@polcom.net \
    --cc=anonymouslinuxuser@gmail.com \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=diablod3@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®