From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
bkuhn@sfconservancy.org, Andy Grover <agrover@redhat.com>,
Marc Fleischmann <mwf@risingtidesystems.com>,
legal@lists.gpl-violations.org
Subject: Re: [PATCH] target: Update copyright ownership to 2012
Date: Sat, 10 Nov 2012 18:44:59 -0800 [thread overview]
Message-ID: <1352601899.4168.35.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <CAGZ=bqJ26Y2x9j+QuARAdfxSsU3ncSZV+YRU8ZiCvS6fSx=X_A@mail.gmail.com>
On Sat, 2012-11-10 at 16:18 -0800, Kyle Moffett wrote:
> On Fri, Nov 9, 2012 at 3:00 PM, Nicholas A. Bellinger
> <nab@linux-iscsi.org> wrote:
> > This patch to update copyright year to current for principal target core
> > ownership is now being pushed into target-pending/for-next.
>
> Pardon me, but you were just publicly accused of violating the GPL, so
> your response is to send a patch removing the copyright notices of all
> other organizations from the SCSI-target code? Have you obtained
> ownership of all the relevant copyrights for Linux-iSCSI.org, PyX
> Technologies, Inc, and SBE, Inc?
I understand and appreciate your concerns.
To answer your question, we have rightfully obtained ownership of all
relevant copyrights to the target code for PyX Technologies LLC, and
SBEi, Inc.
I co-founded PyX in 2002, where we started the development of the target
code. PyX was subsequently acquired by SBEi in 2005. In 2007, I
purchased (at significant personal cost) all rights, title and interest
(incl. the copyright) in the target code. I then co-founded RisingTide
with this code in 2009.
Linux-iSCSI.org is only a URL and website that is owned by RisingTide
Systems, and not a legal entity or person, so listing it as a copyright
holder is meaningless.
> If not, then this patch is an
> attempted violation of those organizations copyrights and of the GPL
> (which requires that you preserve copyright notices).
>
> Further, while these notices are the only ones listed in those files,
> they are not the only individuals outside of RisingTide Systems which
> have significant copyright interest in this code.
>
> If your goal is to
> obtain exclusive copyright ownership over this code then there are a
> great many other people you must contact and convince first.
>
The goal is to update the copyright to the current year, and to remove
legal entities that no longer exist or were meaningless.
I hope this clarifies your concerns.
Thank you,
--nab
next prev parent reply other threads:[~2012-11-11 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 23:00 [PATCH] target: Update copyright ownership to 2012 Nicholas A. Bellinger
2012-11-10 10:15 ` Kirill A. Shutemov
2012-11-10 19:18 ` Pasi Kärkkäinen
2012-11-11 0:18 ` Kyle Moffett
2012-11-11 2:44 ` Nicholas A. Bellinger [this message]
2012-11-11 8:56 ` James Bottomley
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=1352601899.4168.35.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=agrover@redhat.com \
--cc=bkuhn@sfconservancy.org \
--cc=kyle@moffetthome.net \
--cc=legal@lists.gpl-violations.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwf@risingtidesystems.com \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).