public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [Patch 05/10] OvmfPkg: Add SafeIntLib and BmpSupportLib to DSC files
Date: Thu, 8 Feb 2018 10:47:36 +0100	[thread overview]
Message-ID: <937f0d65-2131-43ea-72ae-acb98c9a0479@redhat.com> (raw)
In-Reply-To: <CAKv+Gu_Ysu5G1jE_1Dzrg_sHshF4wyfFeCB1U3fEqN6_AaJZ=A@mail.gmail.com>

On 02/08/18 10:32, Ard Biesheuvel wrote:
> On 8 February 2018 at 09:25, Laszlo Ersek <lersek@redhat.com> wrote:
>> On 02/08/18 09:32, Jordan Justen wrote:
>>
>>> Given the wording from the contribution agreement, it appears that it
>>> would also be fine to just use Mike's Signed-off-by if he is
>>> authorized to contribute the code even though he didn't author it.
>>
>> So basically just
>>
>>   """
>>   Contributed-under: TianoCore Contribution Agreement 1.1
>>   Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
>>   """
>>
>> implies Mike saying, "trust me guys, I got Microsoft's authorization (or
>> whoever the original authors were) to contribute their code under the
>> 2-clause BSDL". Is that right?
>>
>> Dunno why but this concept is hard for me to accept. :) "whoever the
>> original authors were" is super vague to me. Let's say I want to verify
>> that authorization myself: whom do I contact? Are the
>> "https://github.com/Microsoft/MS_UEFI/..." references considered
>> sufficient origin information?
>>
> 
> This is exactly the reason: if someone contributes code under a
> suitable license, they should take full responsibility that the code
> in question is actually covered by that license.

OK. If that works, then patches #5 and #10 are

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

as they are in this series.

(This keeps boggling my mind -- I honestly wonder whether responsibility
*can* stop at the submitter, as opposed to "catching up" with the whole
project --, so I'm pretty sure I'll forget about this interpretation
again, and you'll have to remind me again. Please bear with me. :( )

> I refuse any responsibility for verifying the origin of code that
> others contribute, and I'm sure your workload doesn't allow it either.

It's definitely not that I'd take any responsibility for origin
verification; I just figured that contributors could (or should)
semi-formally support such efforts, *should* someone in the future feel
like verifying the origin.

Thanks
Laszlo


  reply	other threads:[~2018-02-08  9:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 22:58 [Patch 00/10] Add BmpSupportLib class and instance Kinney, Michael D
2018-02-07 22:58 ` [Patch 01/10] MdeModulePkg: " Kinney, Michael D
2018-02-08  5:10   ` Zeng, Star
2018-02-07 22:58 ` [Patch 02/10] MdeModulePkg/DxeCapsuleLibFmp: Use BmpSupportLib Kinney, Michael D
2018-02-07 22:58 ` [Patch 03/10] MdeModulePkg/BootGraphicsResourceTableDxe: " Kinney, Michael D
2018-02-07 22:58 ` [Patch 04/10] IntelFrameworkModulePkg/GenericBdsLib: " Kinney, Michael D
2018-02-07 22:58 ` [Patch 05/10] OvmfPkg: Add SafeIntLib and BmpSupportLib to DSC files Kinney, Michael D
2018-02-07 23:17   ` Laszlo Ersek
2018-02-07 23:48     ` Kinney, Michael D
2018-02-08  0:35       ` Laszlo Ersek
2018-02-08  7:43         ` Ard Biesheuvel
2018-02-08  8:32           ` Jordan Justen
2018-02-08  9:25             ` Laszlo Ersek
2018-02-08  9:32               ` Ard Biesheuvel
2018-02-08  9:47                 ` Laszlo Ersek [this message]
2018-02-08  8:55           ` Laszlo Ersek
2018-02-07 22:58 ` [Patch 06/10] Vlv2TbltDevicePkg/Override/GenericBdsLib: Use BmpSupportLib Kinney, Michael D
2018-02-07 22:58 ` [Patch 07/10] QuarkPlatformPkg: Add SafeIntLib and BmpSupportLib to DSC files Kinney, Michael D
2018-02-07 22:58 ` [Patch 08/10] DuetPkg: " Kinney, Michael D
2018-02-07 22:58 ` [Patch 09/10] EmulatorPkg: " Kinney, Michael D
2018-02-08  8:33   ` Jordan Justen
2018-02-07 22:58 ` [Patch 10/10] ArmVirtPkg: " Kinney, Michael D
2018-02-07 23:25   ` Laszlo Ersek
2018-02-11  0:16 ` [Patch 00/10] Add BmpSupportLib class and instance Bret Barkelew
2018-02-11  0:19 ` Bret Barkelew

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=937f0d65-2131-43ea-72ae-acb98c9a0479@redhat.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