From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Andy Grover <agrover@redhat.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Ritesh Raj Sarraf <rrs@debian.org>,
targetcli-fb-devel@lists.fedorahosted.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: targetcli -fb now also Apache 2.0 licensed
Date: Wed, 24 Jul 2013 13:21:04 -0700 [thread overview]
Message-ID: <1374697264.7382.39.camel@dabdike> (raw)
In-Reply-To: <1374696565.7397.1292.camel@haakon3.risingtidesystems.com>
On Wed, 2013-07-24 at 13:09 -0700, Nicholas A. Bellinger wrote:
> On Tue, 2013-07-23 at 23:27 -0700, Andy Grover wrote:
> > Hi Nick,
> >
> > I just wanted to let you know that I finally received permission from
> > all contributors, and have matched RisingTide's relicensing of targetcli
> > and its dependencies to Apache 2.0, by relicensing the additional
> > contributions in the targetcli-fb branch under the same license.
> >
> > I'm not quite sure the next steps are, except enjoying all our newly
> > non-viral source code, but much thanks for getting the ball rolling.
> >
>
> Making this type of announcement without coordinating with us on a plan
> for moving forward is pretty lame. Especially considering that we've
> kept asking you privately about how to work together to reconcile -fb
> with upstream, and your response essentially boiled down to "What's in
> it for me..?".
Oh good grief, children, how about you both play nicely in the sand box
or I'll fetch your parents to make you see sense.
> So if you really, really need an incentive to "do the right thing", how
> about I start not accept kernel patches from you until you're ready to
> drop -fb and start working with upstream for real..?
Well, the thing is, being a maintainer in Linux is a position of trust.
The fastest way to lose that trust is to hold your tree to ransom or
indeed refuse to accept patches for anything other than technical or
licensing reasons.
James
next prev parent reply other threads:[~2013-07-24 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 6:27 targetcli -fb now also Apache 2.0 licensed Andy Grover
2013-07-24 20:09 ` Nicholas A. Bellinger
2013-07-24 20:21 ` James Bottomley [this message]
2013-07-24 20:54 ` Nicholas A. Bellinger
2013-07-25 0:06 ` Andy Grover
2013-07-25 1:19 ` Nicholas A. Bellinger
2013-07-26 3:31 ` Andy Grover
2013-07-26 7:24 ` Ritesh Raj Sarraf
2013-07-26 15:18 ` Marc Fleischmann
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=1374697264.7382.39.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=agrover@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rrs@debian.org \
--cc=target-devel@vger.kernel.org \
--cc=targetcli-fb-devel@lists.fedorahosted.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