public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"lersek@redhat.com" <lersek@redhat.com>
Cc: "mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
	"Leif Lindholm" <quic_llindhol@quicinc.com>,
	Andrew Fish <afish@apple.com>,
	"Sean Brogan" <sean.brogan@microsoft.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Oliver Steffen <osteffen@redhat.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] CodeQL and Apache Licensed Files
Date: Tue, 31 Oct 2023 19:42:59 +0000	[thread overview]
Message-ID: <CO1PR11MB4929F941CE3E18206758EFEAD2A0A@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAKbZUD3vod3zgammnVu=-RNmH7B2QaTMjUq7X327f7qjduRQfg@mail.gmail.com>

Hi Pedro,

SPDX is only for licenses, not copyrights.

There used to be a requirement for Intel copyright end year to be updated.
That is no longer a requirement, and should reduce the churn on the file
headers.

Mike


> -----Original Message-----
> From: Pedro Falcato <pedro.falcato@gmail.com>
> Sent: Tuesday, October 31, 2023 12:23 PM
> To: devel@edk2.groups.io; lersek@redhat.com
> Cc: mikuback@linux.microsoft.com; Kinney, Michael D
> <michael.d.kinney@intel.com>; Leif Lindholm
> <quic_llindhol@quicinc.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
> 
> On Sat, Oct 28, 2023 at 12:51 PM Laszlo Ersek <lersek@redhat.com>
> wrote:
> >
> > On 10/27/23 23:11, Michael Kubacki wrote:
> > > I'd like to bring attention to Apache License 2.0 code in the
> CodeQL
> > > series I sent to the mailing list for steward review.
> > >
> > > In particular, the files in the BaseTools/Plugin/CodeQL/analyze
> > > directory of this patch:
> > >
> > > https://edk2.groups.io/g/devel/message/109696
> > >
> > > Please let me know if any next steps are needed.
> >
> > (1) I don't know if edk2 accepts contributions under Apache License
> 2.0;
> > just want to point out that this license is acceptable in Fedora
> (and so
> > RHEL too), per
> > <https://docs.fedoraproject.org/en-US/legal/allowed-licenses/>.
> Assuming
> > we're talking about "Apache Software License 2.0".
> >
> > (2) Should we extend "License Details" and "Code Contributions" in
> > "ReadMe.rst"?
> >
> > (3) Should the new files (under Apache License 2.0) use an SPDX
> > identifier tag, for easy greppability?
> 
> I would welcome replacing *all* copyright notices with SPDX tags.
> Would also end the "Copyright (c) Corp Corporation" churn that
> regularly happens in EDK2!
> 
> --
> Pedro


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110445): https://edk2.groups.io/g/devel/message/110445
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]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-10-31 19:43 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 [this message]
2023-10-31 19:49       ` Pedro Falcato
2023-11-01 11:11         ` Leif Lindholm

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=CO1PR11MB4929F941CE3E18206758EFEAD2A0A@CO1PR11MB4929.namprd11.prod.outlook.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