Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance

[Alexandre Belloni <alexandre.belloni@bootlin.com>]

On 18/09/2018 14:03:24-0400, Konstantin Ryabitsev wrote:
> On Tue, Sep 18, 2018 at 07:49:13PM +0200, Greg KH wrote:
> > > 1. Allows people to generate an account
> > > 2. Verifies their email address
> > > 3. Instructs people how to generate a patch or series of patches
> > > 4. Gives a way to upload generated patches
> > > 5. Runs checkpatch to make sure there are no errors
> > > 6. Runs get_maintainer to find out where the patch(es) should be sent to
> > > 7. (Does more imaginary magic, such as looking up message-id references)
> > > 8. Mails it out
> > 
> > That last step might be hard, you have to "mail it out" to look like it
> > came from the original author, right?  Then all crud breaks out as you
> > can't deliver an email from "sony.com" successfully.
> 
> We already do nasty things to work around this. E.g. if you look at the
> envelope-sender for mail delivered via mail.kernel.org you'll see that it
> all looks like this: SRS0=crc=stuff=orig-domain.com=orig-local@kernel.org
> 
> So, mailing it out and having it pass DKIM/SPF checks to be reliably
> delivered is something we can do. Or, we can send it from
> "vapor-git-thingy@kernel.org" and put the original sender into Reply-To,
> which is also kosher.
> 

Wouldn't that break patchwork? I remember having to edit patches because
it changed the name of the author to its previous named based on the
email address (the name changed but not the email).

Else, I find that a generally good idea.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com