|| ||"Bradley M. Kuhn" <bkuhn-AT-sfconservancy.org> |
|| ||Theodore Ts'o <tytso-AT-mit.edu>,
James Bottomley <James.Bottomley-AT-HansenPartnership.com>,
Andy Grover <agrover-AT-redhat.com> |
|| ||Re: scsi target, likely GPL violation |
|| ||Sun, 11 Nov 2012 10:15:02 -0500|
|| ||"Nicholas A. Bellinger" <nab-AT-linux-iscsi.org>,
Marc Fleischmann <mwf-AT-risingtidesystems.com>,
Nicholas Bellinger <nab-AT-risingtidesystems.com>|
|| ||Article, Thread
> 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
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.
>> [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
to post comments)