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]

Message-ID: <51F06C17.50306@redhat.com>
Date:	Wed, 24 Jul 2013 17:06:47 -0700
From:	Andy Grover <agrover@...hat.com>
To:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
CC:	James Bottomley <James.Bottomley@...senPartnership.com>,
	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 07/24/2013 01:54 PM, Nicholas A. Bellinger wrote:
> Yes, which is why I've been accepting his kernel patches the entire time
> that user-space has been forked into -fb.  Now that the user-space code
> has been relicensed as promised, there is no longer any reason for a
> separate -fb fork to exist.
>
> That said, it's time to start moving forward toward a single set of
> source trees for upstream userspace, so that all distributions can
> mutually benefit from the effort.  As mentioned above, this has so far
> not been enough to get -fb reconciled with upstream.
>
> So I don't consider the above 'holding for ransom' or any nonsense like
> that, considering the end goal is for everyone (not just Fedora) to
> benefit from -fb.

There's nothing stopping any other distro (or commercial entity) from 
adopting targetcli-fb. I don't know why they haven't, except that 
there's a default attitude that the originator of the project is the 
"upstream" forever.

I think I've done a pretty good job maintaining -fb over the past two 
years -- -fb has bug tracking, a list, tarballs, and is actively 
maintained and improved, all things that are not true of upstream.

My question to you (Nick) is, why don't we all just unify on -fb?

Regards -- Andy
(at oscon this week, replies may be delayed)

--
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/