From: Daniel Hazelton <dhazelton@enter.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: davids@webmaster.com, espie@nerim.net, linux-kernel@vger.kernel.org
Subject: Re: GPL weasels and the atheros stink
Date: Mon, 3 Sep 2007 14:11:51 -0400 [thread overview]
Message-ID: <200709031411.51598.dhazelton@enter.net> (raw)
In-Reply-To: <m3bqcjwtuc.fsf@maximus.localdomain>
On Monday 03 September 2007 13:18:35 Krzysztof Halasa wrote:
> Daniel Hazelton <dhazelton@enter.net> writes:
> > Then go yell at Mr. Floeter. The code is dual-licensed and he put
> > BSD-License
> > only code in it. Because that's the *EXACT* *SAME* thing you're talking
> > about.
>
> Actually it is not.
>
> Dual BSD/GPL licence essentially means BSD, because rights given by
> BSD are a superset of these by GPL.
Actually, I was pointing out a logical fallacy. I'll spell it out long here so
everyone can see the point I was trying to make.
Person A writes a device driver and releases it under a dual license.
Person B modifies said device driver and licenses his changes under only one
of the licenses on the device driver. Nobody complains.
Person C modifies the same device driver and licenses his changes under the
other license on the device driver. People start complaining.
In this case either the actions of both persons B and C are legal - in which
case neither person B or person C is likely to lose a lawsuit (or even face
one) - or they are illegal, in which case the second a lawsuit is brought
against person C, the same lawsuit must be brought against person B.
The exact nature of the licenses and whether one is a superset or subset of
the other doesn't matter. Either the action of making modifications licensed
solely under one or the other of the two licenses on the original code-base
is illegal or it isn't.
<snip out the straw-man>
> The other thing is copyright notices. I think one can't legally
> alter someone else's licence conditions (in his/her name), unless
> something like that is explicitly permitted.
Fully agreed. I've even said such myself.
> However, we're talking about derivative works. A derivative
> work may be, for example, GPL-licenced:
>
> "Copyright (C) 1234 Joe the GPL lover
> licenced under the GPL as published"
>
> but could lawfully use code originally licenced under BSD:
>
> "Portions copyright (C) 1234 Bill the BSD lover
> originally licenced under no-ad BSD"
>
> Thus his (Joe's) work is GPL only, but Bill's licence notice is
> intact as required by it (BSD).
I've suggested that such be done in the future - if just because it *IS* how
it should be done.
>
> IANAL, maybe you (all of us) should consult one if required.
Would cost me money to consult a lawyer over this, but I do have a few friends
that have completed law school and are waiting on the results of the BAR.
They have told me that they are not legally allowed to dispense legal
advice - but I got around that by asking them to recount what the law
actually says.
Apparently the above suggestion would meet the letter of the law.
DRH
--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
next prev parent reply other threads:[~2007-09-03 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 14:03 Marc Espie
2007-09-02 16:52 ` Kyle Moffett
2007-09-02 16:54 ` Alan Cox
2007-09-02 17:16 ` Oleg Verych
2007-09-02 17:34 ` Michael Tharp
2007-09-02 17:41 ` Jeff Garzik
2007-09-02 17:57 ` Jeff Garzik
2007-09-02 20:22 ` Bernd Petrovitsch
2007-09-03 2:01 ` David Schwartz
2007-09-03 2:57 ` Daniel Hazelton
2007-09-03 9:47 ` David Schwartz
2007-09-03 17:43 ` Daniel Hazelton
2007-09-04 0:23 ` David Schwartz
2007-09-04 0:49 ` Daniel Hazelton
2007-09-04 15:10 ` Valdis.Kletnieks
2007-09-04 17:20 ` Daniel Hazelton
2007-09-03 17:18 ` Krzysztof Halasa
2007-09-03 18:11 ` Daniel Hazelton [this message]
2007-09-03 16:12 ` Valdis.Kletnieks
2007-09-04 15:01 ` Jarek Poplawski
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=200709031411.51598.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=davids@webmaster.com \
--cc=espie@nerim.net \
--cc=khc@pm.waw.pl \
--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
Powered by JetHome