Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel

[Sarah A Sharp <sarah@thesharps.us>]

[-- Attachment #1: Type: text/plain, Size: 2923 bytes --]

On May 11, 2014 9:37 AM, "Laurent Pinchart" <
laurent.pinchart@ideasonboard.com> wrote:
>
> 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.

It would be interesting to see if the app could use Google voice
recognition to fill in the text fields. Even just partially filling out the
bugzilla form and allowing it to be edited later would be useful.

To be clear: I'm suggesting the bugzilla entry be an *optional* part of the
Android app. I suspect that if we automatically uploaded every oops,
maintainers would shortly make a mail filter to ignore the reports from
bugzilla.

Sarah Sharp

[-- Attachment #2: Type: text/html, Size: 3981 bytes --]