linux-kernel - Re: targetcli -fb now also Apache 2.0 licensed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 24 Jul 2013 13:09:25 -0700
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Andy Grover <agrover@...hat.com>
Cc:	target-devel <target-devel@...r.kernel.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	Ritesh Raj Sarraf <rrs@...ian.org>,
	targetcli-fb-devel@...ts.fedorahosted.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: targetcli -fb now also Apache 2.0 licensed

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..?".

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..?

--nab

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/