Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: wireguard@lists.zx2c4.com
Subject: What's the wireguard-tools
Date: Thu, 10 Aug 2023 11:51:35 +0800	[thread overview]
Message-ID: <ZNRex9yqvEekpU/h@Laptop-X1> (raw)

Hi Jason,

I'm maintaining the RHEL wireguard-tools rpm. Recently, There is a request to
convert the license tag in the spec file to SPDX format[1]. The current License
tag in wireguard-tools spec file is GPLv2, which is the same with the COPYING
in upstream. But when I searched the src files, I found there are kinds of
license identifier. e.g. GPL-2.0, LGPL-2.1+, MIT, GPL-2.0 OR MIT, etc.

Do you know which one I should use at the end? Should we unify the src files?

[1] https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1

Thanks
Hangbin

             reply	other threads:[~2023-08-10  3:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  3:51 Hangbin Liu [this message]
2023-08-10 10:46 ` Jason A. Donenfeld
2023-08-11  1:53   ` Hangbin Liu

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=ZNRex9yqvEekpU/h@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=Jason@zx2c4.com \
    --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).