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

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Tue, Sep 18, 2018 at 05:08:02PM +0000, Tim.Bird@sony.com wrote:
>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__korg.wiki.kernel.org_userdoc_mail-23sending-5Foutgoing-
>> 5Fmail&d=DwICAg&c=fP4tf--1dS0biCFlB0saz0I0kjO5v7-
>> GLPtvShAo4cc&r=rUvFawR4KzgZu1gSN5tuozUn7iTTP0Y-
>> INWqfY8MsF0&m=90EMZrRfkvlzWBNtrJ8QnHDj3-EwehEZhQiC5YJY-
>> Uk&s=xtUgBLn5bjLazevAEIdAoHAGclbgin-D9Cek15hsuZk&e=

Ick.

>Thank you for the offer.  However, while that's a solution that might 
>work
>for me (modulo my ability to punch my way through the firewall to that mail
>server), it doesn't scale or help my colleagues at Sony who I'm trying to
>remove barriers for as well.   I'm senior enough at Sony to have a somewhat
>different situation than other Sony Linux developers, however  I intentionally
>work through the IT department and use commonly provided tools here
>in order to 1) understand the hurdles other developers at Sony have, and
>2) work on general solutions.

Ah, I understand your situation better now.

So, what if we imagine that there's an imaginary web tool that does 
this:

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

Would that be useful or solve any problems? Or would that, on the 
contrary, create more problems than it solves?

-K