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

[Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>]

(2014/05/12 1:29), Levente Kurusa wrote:
> Hi,
> 
> 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 <jason@lakedaemon.net> 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. :-)

I guess we might need a smartphone application for sending oops
to correct server. So, I'd like to suggest following; at step 0,
user downloads oops-report application and he/she might sign-up the
server with his mail via the application(optional). And at step2,
run the app to scan the QR code. The app decodes it and reports to
server via user's account (anonymous is ok). :)
Thus, they don't need to fill the additional forms.

Thank you,

-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com