[Ksummit-discuss] Self nomination - Sasha Levin

Julia Lawall julia.lawall at lip6.fr
Fri Aug 26 13:55:18 UTC 2016



On Fri, 26 Aug 2016, Levin, Alexander wrote:

> On Fri, Aug 26, 2016 at 08:11:19AM -0400, Greg KH wrote:
> > On Fri, Aug 26, 2016 at 01:55:27PM +0200, Julia Lawall wrote:
> > > Not sure if I was clear about what I was asking you to agree to :)
> > >
> > > Basically, we can take the patches sent to stable and the patches not sent
> > > to stable as a training set, but then the machine learning comes up with
> > > some algorithm that produces some results.  An expert is needed to evaluate
> > > the results.  Ie for a thousand (number chosen at random) patches, if the
> > > algorithm says it is a bug fixing patch, is it or isn't it, and vice versa.
> > > Of course, we could also evaluate on patches that previously have and have
> > > not been sent too stable, but there is a problem there, because our goal is
> > > to have more patches sent to stable than are already being sent there, so we
> > > need to show that the algorithm can capture what humans are missing.
> >
> > I think that is very interesting research and I would be glad to help
> > out with it how ever I can, as the result might be very useful for us.
> >
> > So sign me up!
>
> I'd be happy to do this as well.
>
> Per Greg's advice, I'm reviewing distro kernels for upstream commits that
> they carry which should have been in our LTS trees, those commits usually
> aren't tagged in any way and can be a good set of commits for training or
> validation.
>
> I do think that we should be using the algorithm to produce a list of authors
> and maintainers who don't provide proper tags when they should and have a
> discussion with them about why that doesn't happen and how we can help them
> to get it "right" (vs just using the algorithm to apply patches).

Thanks for volunteering and for the suggestions.  I will get back to you
about this shortly.

julia


More information about the Ksummit-discuss mailing list