From: J Lovejoy <opensource@jilayne.com>
To: Christoph Hellwig <hch@infradead.org>,
Prarit Bhargava <prarit@redhat.com>
Cc: Dave Miller <davem@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
jschlst@samba.org, linux-kernel <linux-kernel@vger.kernel.org>,
linux-spdx@vger.kernel.org
Subject: Re: SPDX: Appletalk FW license in the kernel
Date: Tue, 26 Sep 2023 09:45:54 -0600 [thread overview]
Message-ID: <7fc54cc9-a53a-46ba-9f16-02d8c638dd26@jilayne.com> (raw)
In-Reply-To: <ZRKJa+cMsFxiizKb@infradead.org>
On 9/26/23 1:34 AM, Christoph Hellwig wrote:
> On Fri, Sep 15, 2023 at 09:39:05AM -0400, Prarit Bhargava wrote:
>>
>> Is there anyone you know of that we could approach to determine a proper
>> SPDX License for these files?
Answering this question generally, even though it sounds like it wasn't
needed for this particular situation:
YES! If you find a license in the kernel that does not match a license
already on the SPDX License List and want to submit the license for
inclusion on the SPDX License List (which, if accepted, means the
license will get an SPDX id assigned), please follow this process:
https://github.com/spdx/license-list-XML/blob/main/DOCS/request-new-license.md
By the way, people on the linux-spdx list may be interested to know that
Fedora has adopted the use of SPDX license ids in the license field of
Fedora package metadata. There has been close collaboration between the
two projects, which has resulted in 95 licenses or exceptions added to
the SPDX License List so far. I think this is a great thing (even if a
lot of work) as it is making the SPDX License List more reflective of
the reality of open source software licensing (including all the
variations on old permissive licenses).
Jilayne
prev parent reply other threads:[~2023-09-26 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6100798b-ab1d-262a-fd5b-435d6dfc4a53@redhat.com>
2023-09-26 7:34 ` SPDX: Appletalk FW license in the kernel Christoph Hellwig
2023-09-26 8:02 ` Greg KH
2023-09-26 13:49 ` Prarit Bhargava
2023-09-26 15:45 ` J Lovejoy [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=7fc54cc9-a53a-46ba-9f16-02d8c638dd26@jilayne.com \
--to=opensource@jilayne.com \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--cc=jschlst@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=vkuznets@redhat.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).