linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: "Theodore Ts'o" <tytso@mit.edu>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Andy Grover <agrover@redhat.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Marc Fleischmann <mwf@risingtidesystems.com>,
	Nicholas Bellinger <nab@risingtidesystems.com>
Subject: Re: scsi target, likely GPL violation
Date: Sun, 11 Nov 2012 10:15:02 -0500	[thread overview]
Message-ID: <87390gxjbd.fsf@ebb.org> (raw)
In-Reply-To: <20121111130553.GA30943@thunk.org> (Theodore Ts'o's message of "Sun, 11 Nov 2012 08:05:53 -0500")

> On Sun, Nov 11, 2012 at 09:34:16AM +0000, James Bottomley wrote:
>> Anybody who does enforcement will tell you that you begin with first
>> hand proof of a violation.  That means obtain the product and make
>> sure it's been modified and that a request for corresponding source
>> fails.

I agree with James that the text quoted above is generally good advice.
However, sometimes, it's very difficult to follow this advice.  In such
cases, it's worth raising the issue directly with the company to learn
the facts.  The discussion thread here indicates there's a very good
chance that this situation was one of the times when such was necessary.
Thus, Andy's actions seem pretty reasonable to me given the facts that
seemed to be before him when he wrote his first email earlier this week.

Theodore Ts'o wrote at 08:05 (EST):
> this is a generalized statement and not one where I have attempted to
> apply the facts to the law --- that requires the expertise of a
> lawyer, and please let's not play lawyer on LKML

I agree fully with that.  IANAL either. :) I'd add, though, that lawyers
aren't magicians -- they simply have an area of expertise and it's worth
seeking a copyright law specialist in matters related to copyright.

But, such lawyers don't necessarily know better how the GPL works simply
because they passed a bar exam; I'm sure no bar exam that has questions
about the GPL.  For example, many copyright law experts understand how
copyright law works with regard to music but are lost when it comes to
applying it to software.  Also, lawyers disagree, and will often just
take the position their client wants them to take even if it's asinine
and unsupported by the law.  I've seen it happen many times.

> [I]t *is* possible for the copyright owner to license the code under
> more than once license.
...
> The bottom line is that copyright licensing can get *complicated*

I think the second sentence I've quoted above is the most salient.
While Ted's right that it *is* theoretically possible for a copyright
holder to release code under more than one license, that copyright
holder may however be confined to a single license choice due to the
fact that his/her work is derivative of another work.  The detailed
facts of a given situation, plus the license text in GPLv2§2¶2-3 and
GPLv2§7, all become very important in such situations.  In short, the
details always matter in such situations, and it's IMO impossible to
generalize beyond that.

> and so before you start flinging about accusations, one would be wise
> to be 100% sure of the facts.

Andy's initial email ended with the request: "Please explain."  Thus,
Andy's email seemed designed to seek facts, which I think is a
reasonable and good thing to do here.  Meanwhile, the facts *still*
aren't clear here yet.

James wrote:
>> [I'd like to see] a genuine public apology for the libel...
>> Because any further discussion of unsubstantiated allegations of this
>> nature exposes us all to jeopardy of legal sanction.

That's a gross overstatement.  I've seen nothing on this thread
that IMO puts anyone on the hook for libel or legal sanctions.  Can you
show us the statue that you believe was violated here?
-- 
Bradley M. Kuhn, Executive Director, Software Freedom Conservancy

  reply	other threads:[~2012-11-11 15:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 16:50 scsi target, likely GPL violation Andy Grover
2012-11-08  1:02 ` Jon Mason
2012-11-08  1:57   ` Chris Friesen
2012-11-08 16:57     ` Andy Grover
2012-11-08 20:05       ` Nicholas A. Bellinger
2012-11-08 20:22         ` Dave Airlie
2012-11-08 21:22         ` Andy Grover
2012-11-09  2:08           ` Nicholas A. Bellinger
2012-11-09 11:03             ` Alan Cox
2012-11-09 19:52               ` Andy Grover
2012-11-09 20:26                 ` Alan Cox
2012-11-11 22:13               ` Lawrence Rosen
2012-11-11 22:41                 ` Julian Calaby
2012-11-11 23:03                   ` Dave Airlie
2012-11-12 14:21                 ` Bradley M. Kuhn
2012-11-15 18:21                 ` Andy Grover
2012-11-09 23:16             ` Andy Grover
2012-11-10 23:32             ` Bradley M. Kuhn
2012-11-08 16:57   ` Andy Grover
2012-11-11  9:34 ` James Bottomley
2012-11-11 13:05   ` Theodore Ts'o
2012-11-11 15:15     ` Bradley M. Kuhn [this message]
2012-11-11 18:22       ` James Bottomley
2012-11-11 18:32         ` Alan Cox
2012-11-14  2:32           ` James Bottomley
2012-11-12 14:08       ` Theodore Ts'o
2012-11-12 14:15         ` Alan Cox
2012-11-12  0:39   ` Douglas Gilbert

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=87390gxjbd.fsf@ebb.org \
    --to=bkuhn@sfconservancy.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agrover@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mwf@risingtidesystems.com \
    --cc=nab@linux-iscsi.org \
    --cc=nab@risingtidesystems.com \
    --cc=target-devel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).