linux-kernel - Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52f7937e-5a83-7783-83c9-820b24c2dca6@infradead.org>
Date:   Fri, 13 Nov 2020 14:47:10 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Jonathan Corbet <corbet@....net>,
        Thorsten Leemhuis <linux@...mhuis.info>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet
 more detailed & helpful

On 11/13/20 2:33 PM, Jonathan Corbet wrote:
> On Thu, 12 Nov 2020 18:58:37 +0100
> Thorsten Leemhuis <linux@...mhuis.info> wrote:
> 
>> This series rewrites the "how to report bugs to the Linux kernel
>> maintainers" document to make it more straight forward and its essence
>> easier to grasp. At the same time make the text provide a lot more details
>> about the process in form of a reference section, so users that want or
>> need to know them have them at hand.
>>
>> The goal of this rewrite: improve the quality of the bug reports and
>> reduce the number of reports that get ignored. This was motivated by many
>> reports of poor quality the submitter noticed while looking after Linux
>> kernel regression tracking many moons ago.
> 
> So I've not had a chance to try to read through the whole thing again,
> will try to do so in the near future.
> 
> As for how to proceed...getting others to review this is going to be a bit
> of a challenge.  Perhaps the right approach is to just merge the new
> document under a new name - reporting-bugs-the-novel.txt or something -
> then try to get a few people to look at specific parts of it?  Once all
> seems well we can rename it over the old document and call it done.
> 
> Make sense?

I like that idea.

I don't plan to review the series in detail like I did with v1.

-- 
~Randy