Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

Hi Fengguang,

On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu wrote:
> On Mon, Jul 25, 2016 at 10:23:43PM +0200, Alexandre Belloni wrote:
> >On 25/07/2016 at 21:01:25 +0200, Luis R. Rodriguez wrote :
> >> It surprises Fengguang Wu <fengguang.wu@intel.com> hasn't been nominated
> >> yet, so I'd like to nominate him. The mechanical process should probably
> >> include in the future a scrape for top Reported-by contributors.
> >
> > That's a good point.
> >
> >> Fengguang's 0-day infrastructure is invaluable to day to day kernel
> >> development, having him present would be great for any questions that may
> >> come up. Getting a statistical overview / update of impact / any major
> >> architectural changes of the 0-day infrastructure would also be very
> >> useful. If maintainers are not yet using 0-day it would be great to hear
> >> why. If your contributors are not using 0-day (I know some of you exist)
> >> I'd like to know why you don't use it, I often run into issues on
> >> linux-next which at times I have to fix, if 0-day would have been used a
> >> folowup fix would not have been needed.
> >
> > Well, I think it would also help to know how the patch/git tree
> > selection is done. Lately, I've been receiving less reports from 0-day
> > and some issues were found by Arnd's autobuilders after hitting
> > linux-next. I used to get report of compilation breakage 10-15 minutes
> > after the patch submission.
> 
> Yeah sorry about that! There are many things that can impact 0-day
> system's stability: regressions, hard disk replacement, proxy issues,
> mailing list kicking off, vocations, etc. Which should improve over
> time as we add monitoring and self-test facilities. On the other hand,
> if you find such issues, please don't hesitate forwarding the error
> emails to us, so that we can check and take action quickly.

There's no need to apologize, really. You've done and keep doing an amazing 
work for which we're all thankful. The biggest problem I see that would stop 
me from fully relying on 0-day is the lack of information about such 
downtimes, leading me to wonder if the absence of a report really means that 
everything is fine. A 0-day status page with information about the current 
status and the planned downtime, as well as possibly the list of trees covered 
by 0-day (I don't know whether part of that information could be considered as 
confidential), would help a lot.

-- 
Regards,

Laurent Pinchart