From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Laszlo Ersek <lersek@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: contribution of code licensed other than bsd+patent
Date: Tue, 28 May 2019 16:32:02 +0100 [thread overview]
Message-ID: <20190528153202.edeajogga3mjf2vg@bivouac.eciton.net> (raw)
Hi stewards, and other interested people.
Readme.md lists a few licenses acceptable but not preferred (this text
used to live in Contributions.txt before the bsd+patent relicensing
effort). However, it does not explicitly state anything about the gap
that was left by the dropping of the TianoCore contribution agreement:
the explicit patent grant given by bsd+patent and TianoCore
contribution agreement.
As we have what I think is the first bit of code about to go in with a
non-bsd+patent license (the new ArmSoftFloat library), is this
something we need to worry about?
If nothing else, I think we should form an official opinion and add it
to Readme.md.
Best Regards,
Leif
next reply other threads:[~2019-05-28 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:32 Leif Lindholm [this message]
2019-05-29 15:24 ` [edk2-devel] contribution of code licensed other than bsd+patent Liming Gao
2019-05-29 15:42 ` 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=20190528153202.edeajogga3mjf2vg@bivouac.eciton.net \
--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