[Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

Chris Mason clm at fb.com
Fri Jul 17 20:02:47 UTC 2015


On Fri, Jul 17, 2015 at 03:46:33PM -0400, Steven Rostedt wrote:
> On Fri, 17 Jul 2015 15:30:13 -0400
> Chris Mason <clm at fb.com> wrote:
> 
> > On Fri, Jul 17, 2015 at 01:53:13PM -0400, Steven Rostedt wrote:
> > > On Fri, 17 Jul 2015 20:43:12 +0300
> > > James Bottomley <James.Bottomley at Hansenpartnership.com> wrote:
> > > 
> > > 
> > > > >--- Some Maintainer's prefer these styles ---
> > > > >
> > > > > These are some extra styles that maintainers prefer. Some are strict
> > > > > about these, others may not care. It doesn't hurt to add them.
> > > > >
> > > 
> > > 
> > > 
> > > > 
> > > > If you do that, and I get 500 coccinelle generated patches for SCSI switching the includes to reverse Christmas tree one file at a time, I'm afraid I'll have to shoot you.
> > > 
> > > I'll remember to wear my bullet proof vest coming to KS.
> > > 
> > > Should stress that just some people prefer them. Heck, we can teach
> > > checkpatch.pl to look at what file is being modified and see what
> > > formats the maintainer of the file wants. :-)
> > 
> > We're way off in the weeds here, and whenever this topic comes up, we
> > end up focusing on the minor annoyances that come from submitting
> > new code.  Small variations in coding style, function naming and
> > general methods for working with a maintainer are sure to vary.
> > 
> > Looking at Jon's statistics, we don't have a problem bringing
> > new people into the kernel.  What can we do to help the new
> > people be more productive?  My own feeling is feedback,
> > testing and documentation are more important than
> > 100% consistency between maintainers.
> > 
> > I love Greg's swag idea, I'm sure
> > more than one LF member would
> > be willing to help sponsor
> > such a thing.
> > 
> > -chris
> 
> I wondered
> why I felt like
> I needed to look for
> my lawn mower. Yeah, we are
> bike shedding here. We need to
> figure out how to get people not
> afraid of submitting their first patch.
> I agree, that swag idea may be a good one.

The first patch really doesn't seem to be a problem.  At least from
the stats I've seen so far.  How do we get the 10..100th patches,
hopefully without 90% of them being whitespace fixes?

We're not going to be able to answer these without
actual data.  This means surveys and talking with
new developers that we really hope to turn into
long term members of the community.

-chris


More information about the Ksummit-discuss mailing list