From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: PJ Waskiewicz <pjwaskiewicz@gmail.com>,
Dirk Hohndel <hohndel@infradead.org>,
Anton Arapov <arapov@gmail.com>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel
Date: Sun, 11 May 2014 18:37:47 +0200 [thread overview]
Message-ID: <1995824.rdvEX5SOIt@avalon> (raw)
In-Reply-To: <20140511162918.GA2527@linux.com>
On Sunday 11 May 2014 18:29:18 Levente Kurusa wrote:
> On Sun, May 11, 2014 at 08:57:01AM -0700, Sarah A Sharp wrote:
> > On Sat, May 10, 2014 at 9:14 PM, Jason Cooper wrote:
> > > All,
> > >
> > > I recently came across a patch series attempting to implement encoding
> > > kernel oops into a QR code [1]. The QR code is then dumped to the
> > >
> > > framebuffer. The QR code is a URL of the form:
> > > https://oops.kernel.org/?qr=<base64 compressed oops>
> > >
> > > This proposal is interesting because it fundamentally changes the way
> > > users report bugs to the kernel community. First and foremost, it makes
> > > it much easier.
> > >
> > > 1) oops occurs
> > > 2) user pulls out phone, scans QR code
> > > - at this point, the oops is recorded on the server. Nothing more
> > > is required of the user.
>
> To be precise, most scanners don't automatically open the links
> found in QR codes and hence a tap/click from the user is required. :-)
>
> > > optionally:
> > >
> > > 3) user fills out a minimal web form
> > > - Name
> > > - email address (do you want to receive emails re this oops?)
> > > - what were you doing when it occurred?
> > > - is it repeatable?
> >
> > By "web form", do you mean a new form or something that's part of
> > kerneloops.org?
> >
> > It would be great if we could allow users to open a new
> > bugzilla.kernel.org entry for the oops. I believe Teodora is working
> > on an Android app that could do this. Hopefully it could store
> > information about the person's system, and pre-propagate the bugzilla
> > entry with this information.
>
> Yes, opening a bugzilla entry might be a good idea if the user fills
> out the form. To be honest, I think for that to work we would need to
> clean up bugzilla a bit. I try to do some work there every now and
> then, but nobody is closing the bugs I have fixed...
>
> Not sure about how would we create the bugzilla entry? I mean, which
> section, urgency, etc. how would we decide on those solely based on
> the OOPS? Or should we ask the user to fill it out?
Filling a complex form on a handheld device can be pretty tedious. A two steps
procedure that would allow entering long text on a real computer could be an
interesting option.
> > > I recall discussing this with some RedHat devs at the 2012 KS, so I know
> > > there is some interest in this capability.
> > >
> > > I'd be interested in having this as a tech topic for several reasons.
> > > First, to raise awareness of the project among the kernel community
> > > (where did all these oops reports start coming from?). Second, to
> > > solicit opinions on how to feed those oops reports into the community.
> > > And last, to sit down with the maintainer of oops.kernel.org and scope
> > > out what work needs to be done to support this on the server side.
> > >
> > > Of course, all of this assumes the patches get accepted. There's been
> > > no rejections so far, though. :)
> > >
> > > If accepted, I would expect the authors to be the ones leading the
> > > discussion (Levente, Teodora).
> >
> > I would recommend that Teodora lead the discussion, since this is her
> > project. Levente has been provided helpful commentary and additional
> > patches, and should definitely participate in the discussion as well.
>
> I was just about to say that the order might not be the most correct. :-)
>
> However, I am more than happy to help Teodora lead the discussion if
> she decides so.
>
> > > Nominations:
> > >
> > > Levente Kurusa <levex@linux.com>
> > > Teodora Băluţă <teobaluta@gmail.com>
> > >
> > > Relevant folks:
> > >
> > > Konstantin Ryabitsev <mricon@kernel.org>
> > > Jason Cooper <jason@lakedaemon.net> (auto-nominated)
> >
> > Another relevant person to include would be PJ Waskiewicz. Teo worked
> > on the QR code generator during her internship with the FOSS Outreach
> > Program for Women (OPW) and PJ was her mentor for the project.
> >
> > You mentioned the kerneloops.org maintainer, but didn't list him here?
> >
> > Anton Arapov looks to be the maintainer, since he's the only
> >
> > contributor to the kerneloops.org github repo.
> >
> > The idea for the oops QR code generator came from Peter Anvin and Dirk
> > Hohndel, so they may want to participate in the discussion as well.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-05-11 16:37 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 4:14 Jason Cooper
2014-05-11 15:57 ` Sarah A Sharp
2014-05-11 16:29 ` Levente Kurusa
2014-05-11 16:37 ` Laurent Pinchart [this message]
2014-05-11 17:18 ` Levente Kurusa
2014-05-11 17:52 ` Teodora Băluţă
2014-05-11 21:49 ` Laurent Pinchart
2014-05-12 16:15 ` Jason Cooper
2014-05-12 16:36 ` Levente Kurusa
2014-05-12 16:53 ` H. Peter Anvin
2014-05-30 18:55 ` Steven Rostedt
2014-05-12 17:00 ` Johannes Berg
2014-05-12 17:46 ` Teodora Băluţă
[not found] ` <CACV2jQCV=rRFg-+x1B3H1=GM5rB_YWp1UU1p7xXkozHKv1Ewvg@mail.gmail.com>
2014-05-13 6:44 ` [Ksummit-discuss] Fwd: " Teodora Băluţă
2014-05-13 7:08 ` Josh Triplett
2014-05-13 15:52 ` Levente Kurusa
2014-05-13 18:42 ` Andy Lutomirski
2014-05-13 20:18 ` josh
2014-05-14 8:20 ` Johannes Berg
2014-05-14 15:52 ` Josh Triplett
2014-05-14 16:00 ` H. Peter Anvin
2014-05-14 16:09 ` Andy Lutomirski
2014-05-14 18:54 ` Josh Triplett
2014-05-14 20:00 ` Levente Kurusa
2014-05-14 20:24 ` Daniel Vetter
2014-05-19 11:59 ` David Herrmann
2014-05-14 22:55 ` Josh Triplett
2014-05-15 12:44 ` Levente Kurusa
2014-05-15 19:19 ` H. Peter Anvin
2014-05-15 19:18 ` H. Peter Anvin
2014-05-15 20:41 ` Levente Kurusa
2014-05-13 14:45 ` [Ksummit-discuss] " David Woodhouse
2014-05-15 19:21 ` H. Peter Anvin
2014-05-15 19:53 ` Jiri Kosina
2014-05-12 15:53 ` Jason Cooper
2014-05-12 16:49 ` Levente Kurusa
2014-05-12 17:09 ` H. Peter Anvin
2014-05-12 17:50 ` Teodora Băluţă
2014-05-13 11:25 ` Greg KH
2014-05-13 14:41 ` Sarah A Sharp
2014-05-13 15:05 ` Greg KH
2014-05-13 15:51 ` Sarah A Sharp
2014-05-13 15:59 ` Josh Boyer
2014-05-13 16:07 ` Theodore Ts'o
2014-05-13 17:43 ` Levente Kurusa
2014-05-13 18:14 ` Teodora Baluta
2014-05-15 14:24 ` Levente Kurusa
2014-05-15 16:02 ` Teodora Băluţă
2014-05-14 1:14 ` Josh Boyer
2014-05-15 17:01 ` Levente Kurusa
2014-05-15 17:11 ` Josh Boyer
2014-05-17 15:02 ` Levente Kurusa
2014-05-15 5:41 ` PJ Waskiewicz
2014-05-15 15:41 ` Theodore Ts'o
2014-05-17 16:36 ` Levente Kurusa
2014-05-20 14:47 ` Theodore Ts'o
2014-05-21 18:03 ` Levente Kurusa
2014-05-25 19:49 ` Teodora Băluţă
2014-05-15 19:24 ` H. Peter Anvin
2014-05-15 21:13 ` Levente Kurusa
2014-05-13 16:03 ` Greg KH
2014-05-12 17:24 ` Jason Cooper
2014-05-11 17:49 ` Sarah A Sharp
2014-05-12 10:13 ` Masami Hiramatsu
2014-05-12 2:38 ` H. Peter Anvin
2014-05-12 6:13 ` Josh Triplett
2014-05-12 9:23 ` David Woodhouse
2014-05-12 13:48 ` Lukáš Czerner
2014-05-12 16:24 ` Jason Cooper
2014-05-12 16:45 ` H. Peter Anvin
2014-05-12 16:22 ` Jason Cooper
2014-05-12 16:46 ` H. Peter Anvin
2014-05-12 17:32 ` Jason Cooper
2014-05-12 17:42 ` Sarah A Sharp
2014-05-12 15:46 ` Jason Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1995824.rdvEX5SOIt@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=arapov@gmail.com \
--cc=hohndel@infradead.org \
--cc=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pjwaskiewicz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox