From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
Lars Kurth <lars.kurth@citrix.com>,
Julien Grall <julien.grall@arm.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>
Subject: Re: PATCH] Change EDK II to BSD+Patent License
Date: Sat, 23 Mar 2019 00:44:21 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9C70546@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <f6273821-5463-6007-1690-d9718da528f0@redhat.com>
Hi Laszlo,
I have entered the following BZ for SPDX identifiers for
MIT licensed content in OvmfPkg.
https://bugzilla.tianocore.org/show_bug.cgi?id=1654
Best regards,
Mike
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Wednesday, March 20, 2019 5:10 AM
> To: Lars Kurth <lars.kurth@citrix.com>; Julien Grall
> <julien.grall@arm.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Cc: edk2-devel@lists.01.org; Ard Biesheuvel
> <ard.biesheuvel@linaro.org>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Anthony Perard
> <anthony.perard@citrix.com>; Marc-André Lureau
> <marcandre.lureau@redhat.com>; Stefan Berger
> <stefanb@linux.ibm.com>
> Subject: Re: [edk2] PATCH] Change EDK II to BSD+Patent
> License
>
> On 03/15/19 18:48, Lars Kurth wrote:
> >
> >
> > On 15/03/2019, 10:18, "Julien Grall"
> <julien.grall@arm.com> wrote:
> >
> > >
> > > EDK2 is converting the full copyright in
> each file to SDPX identifier. While the
> > > copyright looks like an MIT license, it has
> never been confirmed. Andrew Cooper
> > > suggested you might be able to confirm.
> > >
> > > Is there a web-link to the files/repos such that
> I don’t have to clone the repo
> > > Lars
> >
> > Here an example of files from Xen public headers:
> >
> >
> https://xenbits.xen.org/gitweb/?p=xen.git;a=tree;f=xen/in
> clude/public;h=0618b0134d2b9babcba71a3f0f86be5a84468b50;h
> b=HEAD
> >
> > OK, this makes this easy then. Because in all
> likelihood, the files were copied from xen/include/public
> and then the COPYING file
> https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/in
> clude/public/COPYING applies, which states that
> everything in this directory is MIT, unless stated
> otherwise in the file.
> >
> > So as long as someone confirms that the files in
> OvmfPkg/Include came from xen/include/public, this is a
> clear case of a MIT license
> > If they are files from other directories in Xen, check
> the COPYING file in the original directory (or if there
> is none in the parent directory) and check the COPYING
> file
> >
> > I am not so clear about where the files in XenBusDxe
> came from, but the same principle applies.
> >
> > If someone groups these files by "original directory in
> Xen" to File ... I am happy to do a final sanity check
> and sign it off and/or deal with any unclear cases
>
> Replacing MIT license blocks with SPDX identifiers is
> something we
> should do later -- I think it's out of scope for Mike's
> current patch
> series, it's just something I noticed and pointed out for
> the future,
> while I was verifying the "license block -> SPDX ID"
> replacements for
> 2-BSDL (i.e., *not* MIT).
>
> Mike mentioned that he was going to file a number of
> TianoCore BZs as a
> result of the discussion in this thread. Mike, can you
> please file one
> for the MIT->SPDX "refactoring" (under OvmfPkg) as well?
> If not, I can
> file it myself later, I just wouldn't like us to end up
> with duplicates.
>
> Once we have that separate BZ, we can discuss it in
> isolation.
>
> Thanks
> Laszlo
next prev parent reply other threads:[~2019-03-23 0:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 17:54 PATCH] Change EDK II to BSD+Patent License Kinney, Michael D
2019-03-14 10:55 ` Laszlo Ersek
2019-03-14 19:06 ` Julien Grall
[not found] ` <8F40F2BF-B40F-4338-A832-70AE84B26408@citrix.com>
2019-03-15 9:35 ` Julien Grall
[not found] ` <6FBC013D-4BC9-454C-9D4D-87C96F435704@citrix.com>
2019-03-15 17:18 ` Julien Grall
[not found] ` <C2A0176C-8197-421A-9CA9-2B416DF17EAB@citrix.com>
2019-03-20 12:09 ` Laszlo Ersek
2019-03-23 0:44 ` Kinney, Michael D [this message]
2019-03-25 10:04 ` Laszlo Ersek
[not found] ` <720E0EE9-2AED-4110-827D-B87DE5F52862@citrix.com>
2019-03-20 18:25 ` Laszlo Ersek
2019-03-20 18:42 ` Julien Grall
2019-03-20 20:03 ` Laszlo Ersek
[not found] ` <8A1C7ED9-000A-4EBB-A196-10CE5B9B522F@citrix.com>
2019-03-21 17:41 ` Laszlo Ersek
2019-03-18 18:17 ` Kinney, Michael D
2019-03-14 18:03 ` Jordan Justen
2019-03-18 18:25 ` Kinney, Michael D
2019-03-18 19:42 ` Jordan Justen
2019-03-19 17:58 ` Leif Lindholm
2019-03-19 19:09 ` Kinney, Michael D
2019-03-19 19:57 ` Jordan Justen
2019-03-19 20:06 ` 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=E92EE9817A31E24EB0585FDF735412F5B9C70546@ORSMSX112.amr.corp.intel.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