All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Tim.Bird@sony.com>
To: daniel.sangorrin@toshiba.co.jp, fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] [PATCH] bash-completion: add completion script for ftc
Date: Thu, 28 Feb 2019 23:55:32 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF8E0F9719@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <OSAPR01MB3763DD60C01FD6CBA7DA2FABD0750@OSAPR01MB3763.jpnprd01.prod.outlook.com>

OK.  I'd like to apply the patch to Fuego, but with a slight word change
to the notification text.

Here is what you have now:
> +# This library is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU Lesser General Public License as
> +# published by the Free Software Foundation; either version 2 of the
> +# License, or (at your option) any later version.

I propose changing this to:
> +# This library is free software; you can redistribute it and/or modify
> +# it under the terms of version 2 of the GNU Lesser General Public License as
> +# published by the Free Software Foundation.

Note that this doesn't change the current license of the file (it leaves it LGPL v2).
This is not a change of the license, but of the notification text for the license.
This wording is NOT part of the LGPL v2 license.  The change would limit the
license to LGPL v2, and prevent conversion to some successor license (including
a license that is yet-unwritten, and could be substantially different in terms
from LGPL v2.)

Please let me know if that's OK.
 -- Tim


> -----Original Message-----
> From: daniel.sangorrin@toshiba.co.jp
> 
> Hi Tim,
> 
> I have no problem with changing the License to BSD 3-clause but it seems
> that bash-completion is GPLv2
> 
> https://github.com/scop/bash-completion/blob/master/COPYING
> 
> If we contribute the script to them, it will probably be on any distribution.
> For that reason, I think that it is wiser to release it as GPLv2.
> 
> The script itself is mostly my code, but I did some copy paste from other
> scripts such as the function in_array.
> 
> Best regards,
> Daniel
> 
> > -----Original Message-----
> > From: Tim.Bird@sony.com <Tim.Bird@sony.com>
> > Sent: Thursday, February 28, 2019 9:30 AM
> > To: sangorrin daniel(サンゴリン ダニエル ○SWC□OST)
> <daniel.sangorrin@toshiba.co.jp>;
> > fuego@lists.linuxfoundation.org
> > Subject: RE: [Fuego] [PATCH] bash-completion: add completion script for
> ftc
> >
> >
> >
> > > -----Original Message-----
> > > From: Bird, Timothy
> > > ...However, the default license for Fuego is MIT.
> >
> > Nope.  Correction:  The default license for Fuego is BSD 3-clause.
> > See http://fuegotest.org/wiki/License_And_Contribution_Policy
> >
> > Apparently ftc is GPL v2 only.  That's probably my fault, for basing
> > the original code on Sony's 'ttc', which is GPL v2 only.  There's probably
> > not much of 'ttc' left, but thems the breaks.  With multiple contributors
> > it would be exceedingly difficult to change the ftc license now.
> >
> > But if we can keep new code BSD 3-clause that would be my preference.
> >  -- Tim
> >
> >


  reply	other threads:[~2019-02-28 23:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25  0:46 [Fuego] Add bash-completion script for ftc Daniel Sangorrin
2019-02-25  0:47 ` [Fuego] [PATCH] bash-completion: add completion " Daniel Sangorrin
2019-02-28  0:21   ` Tim.Bird
2019-02-28  0:30   ` Tim.Bird
2019-02-28  7:47     ` daniel.sangorrin
2019-02-28 23:55       ` Tim.Bird [this message]
2019-03-01  0:41         ` daniel.sangorrin
  -- strict thread matches above, loose matches on Subject: below --
2019-02-25  0:42 Daniel Sangorrin
2019-02-28  0:14 ` Tim.Bird

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=ECADFF3FD767C149AD96A924E7EA6EAF8E0F9719@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=fuego@lists.linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.