Re: [Ksummit-discuss] More productive uses of enthusiastic new kernel developers

[Greg KH <greg@kroah.com>]

On Fri, May 30, 2014 at 10:07:02PM -0400, Theodore Ts'o wrote:
> On Sat, May 31, 2014 at 09:44:17AM +0800, Li Zefan wrote:
> > This is similar to my idea in "stable issues" to find a co-maintainer
> > for Greg to do this work. While I sugguest to find a experienced and
> > trustful person, you sugguest newcomers.
> > 
> > I share the same concern with David, and I doubt newcompers are
> > enthusiastic in doing backport for stable trees.
> 
> All I can say is that I've seen it work.  Granted, it was in a
> corporate environment, where if the person gets stuck, they can easily
> call for help from a teammate at an adjacent desk.  The commits were
> also in generally well annotated with testing instructions, and all of
> the patches went through a code review process.  And, while these
> people may have been newcomers to kernel programming, they had all
> passed the Google hiring interview process.

I think you just listed all of the reasons why this is a totally
different environment from the "normal" stable kernel patch backport
process.

Not to mention the fact that we don't usually have tests for any
specific patch, to ensure that they fix what they say they do, and that
nothing got messed up in the backport.

thanks,

greg k-h