From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 2D041386F432 for ; Tue, 26 May 2020 21:28:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2D041386F432 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 84B06300074D; Tue, 26 May 2020 23:28:28 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 30AFA4BBE7EC; Tue, 26 May 2020 23:28:28 +0200 (CEST) Message-ID: <8626017cf79e37c62fd963bc717cf11a58e00d7f.camel@klomp.org> Subject: Re: bzip2-testing LICENSE From: Mark Wielaard To: Randy MacLeod , bzip2-devel@sourceware.org Date: Tue, 26 May 2020 23:28:28 +0200 In-Reply-To: <8ae8f70a-1b78-1520-244b-aaddd235feaa@windriver.com> References: <8ae8f70a-1b78-1520-244b-aaddd235feaa@windriver.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-8.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-8.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: bzip2-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bzip2-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2020 21:28:33 -0000 Hi Randy, On Tue, 2020-05-26 at 16:35 -0400, Randy MacLeod wrote: > I've been reviewing the work that Rahul has done to package > bzip2-testing for Yocto / Open Embedded. One question that I have > is about the license terms of the repo. In brief it seems > that the COPYING/LICENSE files are left over from the original > projects and that it's possible that since the remaining > files are data rather than source You are right. For the purpose of the bzip2-testing project the only "source" is the test runner script run-tests.sh. Everything else can be seen as data. The top-level README file does explain: This is a collection of "interesting" .bz2 files that can be used to test bzip2 works correctly. They come from different projects. Each directory should contain a README file explaining where the .bz2 files originally came from. Plus a reference to the (Free Software) license that the project files were distributed under. > If you agree, then I'd be happy to send a commit to remove > the license files in the sub-directories and include a nice long > explanation in the commit log based on the email referenced above. > If not that's certainly fine as well but I would be puzzled by such > a result! :) But I would like to keep the subdir README files and the license files that describe how those projects distributed their data (and code). Even if we are only redistributing the data files from those projects it seems more correct to keep the license files and copyright claims. Even if we did claim all the data files are not copyrightable and we don't need a license, we already have a license that allows the using, sharing and modification of the data. Having explicit permission to redistribute these file seems a good thing. Even if some people might claim we don't need any such permission in the first place. And it just seems polite to mention the origins and the terms people made these files available under. Cheers, Mark