public inbox for linux-spdx@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Richard Fontana <rfontana@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-spdx@vger.kernel.org, David Howells <dhowells@redhat.com>,
	Tadeusz Struk <tadeusz.struk@linaro.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
	Hyunchul Lee <hyc.lee@gmail.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Steve French <sfrench@samba.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tom Talpey <tom@talpey.com>,
	linux-cifs@vger.kernel.org, Taehee Yoo <ap420073@gmail.com>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Jozsef Kadlecsik <kadlec@netfilter.org>,
	Florian Westphal <fw@strlen.de>,
	coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] treewide: Add SPDX identifier to IETF ASN.1 modules
Date: Sun, 22 Oct 2023 10:53:19 +0200	[thread overview]
Message-ID: <20231022085319.GA25981@wunner.de> (raw)
In-Reply-To: <CAC1cPGx-cb+YZ9KgEFvSjtf+fp9Dhcn4sm9qHmFFDRDxb=7fHg@mail.gmail.com>

On Sat, Oct 21, 2023 at 09:23:55AM -0400, Richard Fontana wrote:
> On Sat, Oct 21, 2023 at 7:25???AM Lukas Wunner <lukas@wunner.de> wrote:
> >
> > Per section 4.c. of the IETF Trust Legal Provisions, "Code Components"
> > in IETF Documents are licensed on the terms of the BSD-3-Clause license:
> >
> > https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5/
> >
> > The term "Code Components" specifically includes ASN.1 modules:
> >
> > https://trustee.ietf.org/documents/trust-legal-provisions/code-components-list-3/
> 
> Sorry if this seems super-pedantic but I am pretty sure the license
> text in the IETF Trust Legal Provisions does not actually match SPDX
> `BSD-3-Clause` because of one additional word in clause 3 ("specific"
> before "contributors"), so IMO you should get SPDX to modify its
> definition of `BSD-3-Clause` prior to applying this patch (or get IETF
> to change its version of the license, but I imagine that would be more
> difficult).

I've submitted a pull request to modify the SPDX definition of
BSD-3-Clause for the IETF variant:

https://github.com/spdx/license-list-XML/pull/2218

I assume this addresses your concern?  Let me know if it doesn't.

If anyone has further objections to this patch please speak up.

Thanks,

Lukas

  reply	other threads:[~2023-10-22  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 11:23 [PATCH] treewide: Add SPDX identifier to IETF ASN.1 modules Lukas Wunner
2023-10-21 13:23 ` Richard Fontana
2023-10-22  8:53   ` Lukas Wunner [this message]
2023-10-31  2:23     ` J Lovejoy
2023-10-27 10:55 ` Herbert Xu

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=20231022085319.GA25981@wunner.de \
    --to=lukas@wunner.de \
    --cc=ap420073@gmail.com \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=hyc.lee@gmail.com \
    --cc=kadlec@netfilter.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=rfontana@redhat.com \
    --cc=senozhatsky@chromium.org \
    --cc=sfrench@samba.org \
    --cc=tadeusz.struk@linaro.org \
    --cc=tglx@linutronix.de \
    --cc=tom@talpey.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