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]

Date:   Wed, 18 Nov 2020 17:29:58 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Thorsten Leemhuis <linux@...mhuis.info>
Cc:     Randy Dunlap <rdunlap@...radead.org>, 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 Sun, 15 Nov 2020 11:13:52 +0100
Thorsten Leemhuis <linux@...mhuis.info> wrote:

> > 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.  
> 
> Great, thx, looking forward to it.

OK, I have made a *quick* pass through the whole thing and sent a small
number of comments separately. There are things that could be tweaked
(there always will be) but I'm not sure we should worry about those yet.
I would suggest doing this:

 - Collapse the whole thing down to a patch adding reporting-bugs-v2.rst
   (or some suitable name).  I do wonder if it should also move to the
   process manual as part of this; not only admins will report bugs.

 - Add a comment at the top saying it's a proposed replacement and
   soliciting comments.  You could also put some of your other questions
   into the text for now and see if anybody reacts.  

 - In a separate patch you could add a comment to the existing document
   pointing to the new one as the true source of wisdom.

 - Dual licensed CC-SA-4.0 is fine with me.  CC-BY is OK if you really
   want to do it that way.  Either way, though, you'll need to add the
   license itself under LICENSES/preferred before it can go into the SPDX
   tag.

With that, I'd say let's just merge it and bash on it from there.

Thanks,

jon