From owner-freebsd-ports@freebsd.org Fri Jan 12 08:57:23 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8760E7BC7D for ; Fri, 12 Jan 2018 08:57:23 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B68727E92D for ; Fri, 12 Jan 2018 08:57:23 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id B5E0CE7BC7B; Fri, 12 Jan 2018 08:57:23 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B590BE7BC7A for ; Fri, 12 Jan 2018 08:57:23 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 79C687E92C for ; Fri, 12 Jan 2018 08:57:23 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1eZv9N-000OXV-F5; Fri, 12 Jan 2018 09:57:21 +0100 Date: Fri, 12 Jan 2018 09:57:21 +0100 From: Kurt Jaeger To: Franco Fichtner Cc: FreeBSD Ports Subject: Re: RESTRICTED in net/frr Message-ID: <20180112085721.GS2827@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 08:57:23 -0000 Hi! > Can somebody please explain: > > > Mark net/frr as RESTRICTED, it contains a possible GPL violation of some > > of the Quagga software that it includes. > > > > Submitted by: Paul Jakma (author of Quagga) > > With hat: portmgr > > MFH: 2018Q1 > > If there is an open reason it should certainly be cited in the commit. As far as I understand it (and I'm by no means authoritative on this)! - Paul is employed by HPE and maintains quagga - HPE is/was also cooperating with cumulus, the folks behind https://cumulusnetworks.com/ and the network operation system cumulus linux - cumulus decided to fork quagga (first on github, on some private repo) see: https://lists.frrouting.org/pipermail/dev/2016-October/000000.html which mentions https://github.com/opensourcerouting/cumulus-private_quagga.git - in the past Paul probably maintained it partially on company-time, but also in his private time. See: https://lists.quagga.net/pipermail/quagga-users/2017-October/014856.html This no longer seems to have the support of HPE (for whatever political reasons, I don't know). HPE might even have forced Paul to be silent about details. - The cause of the rift seems that Paul did not integrate patches suggested by cumulus (?) as fast as cumulus requested. That was probably because cumulus did not provide patches in a piecemeal way that allows to understand interactions between, but in larger patches without much docs to understand the details. - An early sign for this rift was this posting from 2012, where there was a quarrel on GPL (or the way GPL was forced unto those patches): https://lists.quagga.net/pipermail/quagga-users/2012-March/012846.html If anyone has more links to more details, please provide them! -- pi@opsec.eu +49 171 3101372 2 years to go !