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

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

On Tue, Sep 11, 2018 at 02:44:23PM +0200, Alexandre Belloni wrote:
> On 11/09/2018 00:44:57+0200, Daniel Vetter wrote:

> > gitlab (or well anything with a concept like pull requests) makes the
> > 90% so much easier. And it doesn't take more work for contributors if
> > you set things up right - it's just a git push instead of a git
> > send-email. At least after initial setup is done.

> I would like to chime in and remind you that there are many subsystems
> where you get a lot of drive-by contribution from random people. I'm
> obviously thinking about rtc but I think this would also apply to codec,
> IIO, power/supply, hwmon... In that case any initial setup would be
> prohibitive.

Right, and this is also a potential issue for people working kernel wide
if we end up with a bunch of different instances of gitlab or something
similar.  

> So I need to emphasise that there are subsystem where people are not
> backed by a company to contribute or review. What I often see is someone
> having $random hardware and submitting a patch adding support for it.
> That developer will definitively not review other patches because he has
> no particular interest in them. He also probably doesn't have the
> experience to do a review.

Even where people do have corporate backing for what they're doing
they've often worked pretty hard to even get the time to do submissions,
or they're doing it as a byproduct of whatever the "real" goal is.  It
also reduces the impact from CI quite a bit if you've got lots of random
drivers with most of the changes going in there, though it's still a win
for the core and for any hardware which does manage to make it into a CI
system.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]