From owner-freebsd-ports@FreeBSD.ORG Sat Mar 29 11:01:44 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 303A752A; Sat, 29 Mar 2014 11:01:44 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92A592B4; Sat, 29 Mar 2014 11:01:43 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 901BC438BE; Sat, 29 Mar 2014 06:01:20 -0500 (CDT) Message-ID: <5336A7F0.6040104@marino.st> Date: Sat, 29 Mar 2014 12:01:04 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Chris Rees , freebsd-ports@freebsd.org Subject: Re: LPPL10 license consequences intended? (arabic/arabtex) References: <532DC88A.7010104@marino.st> <532DFDB2.1090200@cyberleo.net> <532ED19F.1090100@marino.st> <533541E5.6040003@marino.st> <20140329031431.GA21162@village.abthorpe.org> <533686CE.6040706@marino.st> <20140329101455.GA21319@lonesome.com> <5336A1B5.3080200@marino.st> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2014 11:01:44 -0000 On 3/29/2014 11:48, Chris Rees wrote: > On , John Marino wrote: >> This licensing topic is actually kind of a big mess that nobody seems to >> be leading, and it's not even clear if missing licenses is a problem. >> What's the policy? It would be better to disable the entire framework >> than continue with this half-support. > > The policy on the licensing framework is that it was submitted by a GSoC > student who has disappeared, and tabthorpe was the only one to step up > and take care of the "mess". > > Unfortunately that's the case with a lot of stuff here-- someone drops > something, someone else generously picks it up and gets flak for > historical issues, as well as not being able to devote 110% of their > time to it. Ok, Chris, but that is not what happened here. I noted that tabthorpe committed a license PR without changes 3 years ago and basically from courtesy I offered that he take the first look. He wasn't getting any flak for making a mistake[1]. He also could have said, "no thanks" which, while disappointing, is his prerogative. The problem was that the offer put the topic in tabthorpe's court and without response the topic died. So the issue isn't lack of action, it's lack of response I guess. [1] It hasn't even fully been established that LPP10 is actually defined incorrectly although it leaning that way > If you're interested in the license framework, PLEASE fix it up! That is just the thing, I'm not pro-license framework. I support it because it seems that ports wants it, but if you leave it to me, I'd remove all package-blocking capability and state publicly that LICENSE is a best guess, a courtesy, and not legally binding in any way (and FreeBSD isn't legally responsible in any way). e.g. FYI, AS-IS, no guaranty I am not the person you want leading the license framework if you are a license nut. John