From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id C195348E for ; Thu, 15 May 2014 19:24:55 +0000 (UTC) Received: from mail.zytor.com (terminus.zytor.com [198.137.202.10]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4BDB22020D for ; Thu, 15 May 2014 19:24:55 +0000 (UTC) Message-ID: <53751466.1030401@zytor.com> Date: Thu, 15 May 2014 12:24:22 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: "Theodore Ts'o" , Josh Boyer References: <20140511171824.GB2527@linux.com> <20140512155320.GW12708@titan.lakedaemon.net> <20140512164921.GB3509@linux.com> <53710053.4040100@zytor.com> <20140513112525.GB10733@kroah.com> <20140513150520.GA15857@kroah.com> <20140513160743.GA11391@thunk.org> In-Reply-To: <20140513160743.GA11391@thunk.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: PJ Waskiewicz , Sarah A Sharp , ksummit-discuss@lists.linuxfoundation.org, Anton Arapov , Jason Cooper , Dirk Hohndel Subject: Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/13/2014 09:07 AM, Theodore Ts'o wrote: > I'll note this discussion has started mutating to a more general "how > do we get more useful bug reports in front of developers", which I > think is a good thing. > > However, I'm still not sure how useful it would be to have a tech > topic (or a core topic) dedicated to the matter, because we've had > discussions about and at the end of the day, what's probably really > necessary is to have someone, or a small team, dedicated all or most > of their time to: > > a) improving kerneloops.org > b) finding interesting patterns in the bulk reported data, and then > forwarding that on to developers > c) finding ways of automating (b) > > QR encoded oops might be a means towards that end, but there might be > other things that could be done as well. > > If someone were to *do* all of this work, then reporting on it and > then asking for suggestions about how this service could be improved, > might make a great tech topic. > > But in the absence of that, can folks suggest ways that this doesn't > turn into a "I know, let's put a bell on the cat!" sort of discussion > that doesn't lead to anything useful? > A workflow discussion for gathering fault information in general *might* be useful, but I'm not sure we have the right people for it. As far as I understand, kerneloops.org pretty much lost its usefulness when Fedora (and other distros?) stopped participating and redirected to their own internal sites. -hpa