public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Mark Wielaard <mark@klomp.org>, <bzip2-devel@sourceware.org>,
	Rahul Kumar <rahulk@mvista.com>
Subject: Re: bzip2-testing LICENSE
Date: Tue, 2 Jun 2020 09:57:18 -0400	[thread overview]
Message-ID: <888cff90-9336-3e7b-2090-2c0b01be970b@windriver.com> (raw)
In-Reply-To: <8626017cf79e37c62fd963bc717cf11a58e00d7f.camel@klomp.org>

On 2020-05-26 5:28 p.m., Mark Wielaard wrote:
> 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.

Okay, I'm glad you agree with my opinion and we may change the
Yocto recipe license summary.

Your position regarding keeping the bzip2-tests README and licenses
files makes sense now that I've had some time mull it over and see
things from your point of view. In summary no change is required.

Thanks for your response and your work on bzip2,

../Randy

> 
> Cheers,
> 
> Mark
> 


-- 
# Randy MacLeod
# Wind River Linux

      reply	other threads:[~2020-06-02 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 20:35 Randy MacLeod
2020-05-26 21:28 ` Mark Wielaard
2020-06-02 13:57   ` Randy MacLeod [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=888cff90-9336-3e7b-2090-2c0b01be970b@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=bzip2-devel@sourceware.org \
    --cc=mark@klomp.org \
    --cc=rahulk@mvista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).