From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: PATCH] Change EDK II to BSD+Patent License
Date: Mon, 18 Mar 2019 18:25:54 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9C6C441@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <155258662331.20276.3714209093894340086@jljusten-skl>
Hi Jordan,
No proposed changes to the Signed-off-by tags. If you have
a proposal, please provide an RFC or bring to the monthly
EDK II community meeting.
This series is focused on the license change, the use of SPDX
identifiers, and removing the Contributed-under tag from
commit messages.
I will update the V2 version of the patch series in to make
sure the content from Contributions.txt that is not part of
the TianoCore Contribution Agreement is added to Readme.md.
The RFC mentioned the need to update documentation. I will
send that out as a separate Wiki patch series for review.
Best regards,
Mike
> -----Original Message-----
> From: Justen, Jordan L
> Sent: Thursday, March 14, 2019 11:04 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>;
> edk2-devel@lists.01.org
> Subject: Re: [edk2] PATCH] Change EDK II to BSD+Patent
> License
>
> On 2019-03-13 10:54:22, Kinney, Michael D wrote:
> >
> > 84141eacac edk2: Remove Contributions.txt and update
> Readme.md
>
> I guess this removes the requirement for the
> 'Contributed-under' tag
> in commit messages?
>
> But, what about Signed-off-by? Is it desirable to
> remove that
> requirement?
>
> Relatedly, some open source projects have standardized
> on tying the
> Signed-off-by to this text:
>
> https://developercertificate.org/
>
> So, the contributor doesn't have to agree to give the
> project the
> contribution under the Contributed-under terms, but
> they still
> indicate that they believe that the project can use the
> code under the
> project's indicated license.
>
> There is also other information in Contributions.txt
> that appears to
> have been deleted, rather than moved. I guess it is
> mostly duplicated
> on the wiki. That doesn't mean it's not a good idea to
> duplicate it in
> the source tree, or at least provide a web-link. It
> seems like the
> first place devs might look for such information is
> either the readme,
> or Contributions.txt.
>
> Regarding the wiki, I guess it has to be updated after
> this change is
> made. It might be good to add that to the bug so it
> can't be closed
> until that is fixed.
>
> How about updating BaseTools/Scripts/PatchCheck.py?
>
> -Jordan
next prev parent reply other threads:[~2019-03-18 18:25 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
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 [this message]
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=E92EE9817A31E24EB0585FDF735412F5B9C6C441@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