Re: [RFC PATCH 1/1] docs: submitting-patches: Add Sponsored-by tag to give credits to who sponsored the patch
From: Giulio Benetti
Date: Sat Aug 19 2023 - 20:12:04 EST
Hello Matthew, Laurent,
On 18/08/23 02:21, Matthew Wilcox wrote:
On Fri, Aug 18, 2023 at 02:23:48AM +0300, Laurent Pinchart wrote:
Just adding one data point here, without judging on the merits of this
proposal. I've been requested previously by customers to increase their
visibility in the kernel development statistics, and the way we found to
do so was to sign-off patches with
Laurent Pinchart <laurent.pinchart+customer@xxxxxxxxxxxxxxxx>
(where "customer" is to be replaced with the customer name).
I quite like Sponsored-by: but yet another approach could be the
same as that used by those of us whole use personal email addresses
while being employed by someone. So my SoB is:
Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx>
but you might have (eg)
Laurent Pinchard (Coca-Cola) <laurent.pinchart@xxxxxxxxxxxxxxxx>
and then when working for another sponsor:
Laurent Pinchard (Ford) <laurent.pinchart@xxxxxxxxxxxxxxxx>
This is a good solution too. It's only that it gives me the idea that
Laurent Pinchard actually works inside Coca-Cola then Ford and so on.
At the least this is my understanding at first sight.
What I've found not easy at all instead in my patch is to deal with the
Acked-by: from the Sponsor, because he could have to do that for(let's
say) 100 patches, and it becomes not easy to check.
I've been pointed that there is already the DCO the prevents from fake
Sponsored-by: tags removing the need to send Acked-by: from the Sponsor.
So I would modify this patch.
But before I'd really like to have more feedback by someone else if
possible.
--
Giulio Benetti
CEO&CTO@Benetti Engineering sas