From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: <devel@edk2.groups.io>, <pedro.falcato@gmail.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "lersek@redhat.com" <lersek@redhat.com>,
"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
Andrew Fish <afish@apple.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Oliver Steffen <osteffen@redhat.com>
Subject: Re: [edk2-devel] CodeQL and Apache Licensed Files
Date: Wed, 1 Nov 2023 11:11:25 +0000 [thread overview]
Message-ID: <ac58f796-df45-4b82-8ce2-a06a06f3a09d@quicinc.com> (raw)
In-Reply-To: <CAKbZUD12c7sA5Jwr6heMhY2fpJ6bF-TrLqHOcBG0G+r-odX8Rw@mail.gmail.com>
On 2023-10-31 19:49, Pedro Falcato wrote:
> On Tue, Oct 31, 2023 at 7:43 PM Kinney, Michael D
> <michael.d.kinney@intel.com> wrote:
>>
>> Hi Pedro,
>>
>> SPDX is only for licenses, not copyrights.
>
> IANAL, but several FOSS projects (including Linux) have generally
> replaced the "Copyright (c) ..." verbiage with SPDX.
They may have decided to get rid of the copyright statements at the same
time as they switched to SPDX instead of full boilerplate licenses, but
that is not the same thing.
/
Leif
> I assume there has to be some legal basis for this, although I don't
> know if it depends on the license, etc
> (IIRC I /think/ one could state that copyright holders are stored in
> git information, but, again, I'm not a lawyer)
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110475): https://edk2.groups.io/g/devel/message/110475
Mute This Topic: https://groups.io/mt/102230244/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-11-01 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 21:11 [edk2-devel] CodeQL and Apache Licensed Files Michael Kubacki
2023-10-28 11:51 ` Laszlo Ersek
2023-10-31 16:07 ` Michael Kubacki
2023-10-31 17:22 ` Laszlo Ersek
2023-10-31 19:19 ` Michael D Kinney
2023-10-31 19:34 ` Michael Kubacki
2023-10-31 19:45 ` Michael D Kinney
2023-10-31 21:29 ` Michael Kubacki
2023-10-31 19:22 ` Pedro Falcato
2023-10-31 19:42 ` Michael D Kinney
2023-10-31 19:49 ` Pedro Falcato
2023-11-01 11:11 ` Leif Lindholm [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-list 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=ac58f796-df45-4b82-8ce2-a06a06f3a09d@quicinc.com \
--to=devel@edk2.groups.io \
/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