Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Adam Stiles <ajstiles@gmail.com>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH wireguard-apple] Update SPDX-License-Identifier tags from GPL-2.0 to MIT
Date: Sun, 13 Dec 2020 19:16:46 -0800	[thread overview]
Message-ID: <CAB5G8p8Y7+TcjBQYWQy+kZMjD=-qv0WoY+vn0dp5A_6FkSGDQw@mail.gmail.com> (raw)
In-Reply-To: <X9am5M94oX00YKU4@latitude>

Hi Jonathan,

Thanks for looking at the patch. In retrospect, I should have asked
about this before I submitted it. I wasn't intending a re-license.
Rather, I assumed those SPDX identifiers were missed when repo was
converted from GPL to MIT a couple of years ago. Apologies,

Adam


On Sun, Dec 13, 2020 at 3:42 PM Jonathan Neuschäfer
<j.neuschaefer@gmx.net> wrote:
>
> Hi,
>
> a little drive-by review, since I happened to see the patch.
> In case I misunderstood something, I apologise in advance.
>
> On Thu, Dec 10, 2020 at 03:54:12PM -0800, Adam Stiles wrote:
> > Signed-off-by: Adam Stiles <ajstiles@gmail.com>
> > ---
> >  Sources/WireGuardApp/UI/macOS/View/highlighter.c | 2 +-
> >  Sources/WireGuardApp/UI/macOS/View/highlighter.h | 2 +-
> >  Sources/WireGuardKitC/key.c                      | 2 +-
> >  Sources/WireGuardKitC/key.h                      | 2 +-
> >  Sources/WireGuardKitC/x25519.c                   | 2 +-
> >  Sources/WireGuardKitGo/Makefile                  | 2 +-
> >  Sources/WireGuardKitGo/wireguard.h               | 2 +-
> >  7 files changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/Sources/WireGuardApp/UI/macOS/View/highlighter.c b/Sources/WireGuardApp/UI/macOS/View/highlighter.c
> > index e0d4e04..55fabfd 100644
> > --- a/Sources/WireGuardApp/UI/macOS/View/highlighter.c
> > +++ b/Sources/WireGuardApp/UI/macOS/View/highlighter.c
> > @@ -1,4 +1,4 @@
> > -// SPDX-License-Identifier: GPL-2.0
> > +// SPDX-License-Identifier: MIT
>
> AFAIUI, such a change expresses a relicensing of the code, and it should
> (IMHO) be made clear in the commit message that this is the case.
>
> All authors of the code must agree to a relicensing. It would be nice
> to see the list of authors in the commit message, along with a
> confirmation that all agreed to relicense the code to MIT.
>
> > -/* SPDX-License-Identifier: GPL-2.0+
> > +/* SPDX-License-Identifier: MIT+
>
> I think MIT+ is an editing error. It's not on the official SPDX license
> identifier list, in any case.
>
>
> Best regards,
> Jonathan Neuschäfer

  reply	other threads:[~2020-12-15  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 23:54 Adam Stiles
2020-12-13 23:42 ` Jonathan Neuschäfer
2020-12-14  3:16   ` Adam Stiles [this message]
2020-12-14 10:34     ` Jonathan Neuschäfer

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='CAB5G8p8Y7+TcjBQYWQy+kZMjD=-qv0WoY+vn0dp5A_6FkSGDQw@mail.gmail.com' \
    --to=ajstiles@gmail.com \
    --cc=j.neuschaefer@gmx.net \
    --cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).