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

[Konstantin Ryabitsev]

On Tue, Sep 18, 2018 at 06:58:45PM +0000, Tim.Bird at sony.com 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
>This could help solve a lot of e-mail issues that contributors have, 
>but also
>I'm very interested in step 5 - the testing aspect.  I would like to be involved in
>discussions of the design of that step, so we could plug lots of different tests
>in, at the request of various sub-system maintainers.  I maintain the Fuego
>test system, so I'd be interested in making available our test suites for that
>step.

I'm not sure this is going to be the right tool for test-suite 
integration -- in fact, I'd argue that CI stuff should remain wholly 
outside of its scope. The goal is to make it easier to send good, 
acceptable patches (even if their content is no good). CI and any other 
automated testing should happen after these patches have hit LKML (and 
any other lists), if only because there is no One True Place That Does 
CI, and things like 0daybot/syzbot/etc are already honed to work via the 
mailing list.

That said, I'm open to be convinced otherwise if others want this to 
happen *before* patches land on the mailing lists. If that is the case, 
we will want to rope kernelci folks into this discussion.

>Please let me know if there's some opportunity to follow up with you on 
>this
>( ie, a list where this might be discussed in more detail, or an event where we
>could talk face-to-face).

I'll be at the Kernel Summit in Vancouver, and I believe at least Kevin 
of KernelCI fame will be there, too.

-K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/attachments/20180918/aebd406f/attachment.sig>