Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 27 Nov 2019 12:25:28 +0100
From:   Eugeniu Rosca <erosca@de.adit-jv.com>
To:     Geert Uytterhoeven <geert@linux-m68k.org>
CC:     Eugeniu Rosca <erosca@de.adit-jv.com>,
        Jonathan Corbet <corbet@lwn.net>,
        Joe Perches <joe@perches.com>,
        Andy Whitcroft <apw@canonical.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Eugeniu Rosca <roscaeugeniu@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] checkpatch: whitelist Originally-by: signature
Message-ID: <20191127112445.GA21836@vmlxhi-102.adit-jv.com>
References: <20191115150202.15208-1-erosca@de.adit-jv.com>
 <05ba4e29fb78885cf9abf7bfc87e0a7bcda099fe.camel@perches.com>
 <20191115154627.GA2187@lxhi-065.adit-jv.com>
 <20191115092943.7c79f81e@lwn.net>
 <20191115172141.GA3085@lxhi-065.adit-jv.com>
 <CAMuHMdUhPV2B4dpgpPogpFQPprX-VOCC5RuwLLv3MiHzp-pq3Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAMuHMdUhPV2B4dpgpPogpFQPprX-VOCC5RuwLLv3MiHzp-pq3Q@mail.gmail.com>
User-Agent: Mutt/1.12.1+40 (7f8642d4ee82) (2019-06-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Geert,

On Wed, Nov 27, 2019 at 10:25:29AM +0100, Geert Uytterhoeven wrote:
[..]
> On Fri, Nov 15, 2019 at 6:24 PM Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
[..]
> > I will give a real-life example. Say, I have some patches in my
> > local tree and they've been developed by somebody who is no longer
> > interested/paid to upstream those.
> >
> > I first submit those patches with the original authorship, plus my SoB.
> > Then, the reviewers post their findings. I put my time into fixing those
> > and re-testing the patch or the entire series. The final patch/series
> > may look totally different compared to the original one.
> >
> > Which way would you suggest to give credits to the original author?
> > I personally think that "Co-developed-by:" conveys the idea/feeling of
> > "teaming up" with somebody, which doesn't happen in my example.
> 
> What I typically do is this:
>   1. If the changes due to review are minor, I just add my SoB below the
>      original SoB,
>   2. If the changes are not insignificant, I also add a line "[geert: Did foo]"
>      in between the original SoB and mine,
>   3. If the patch needed a complete rewrite, I assume ownership, and add
>      "Based on/inspired by ..." to the patch description to give credit.
> 
> Hope this helps (and is acceptable for other people ;-)

Thank you for your time to share the best practices from the heart of
Linux kernel community. This looks like a reasonable blueprint to follow
and I will personally bookmark and quote it whenever appropriate.

The way I see "Originally-by" is that it attempts to replace the free
wording implied at #3 (i.e. patch rewrite case) and hence its benefit.

The less words I have to creatively write by myself, the less errors
I'll make, the less ambiguous my patch will be, the more time I'll have
to dedicate to the important parts of the patch description (feature
overview, bug reproduction, test scenario, etc).

I also understand the desire not to make the process more complicated
than it needs to be. I expect the signature to still pop up here and
there and whether it makes sense to whitelist it, time will tell.

-- 
Best Regards,
Eugeniu