From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 605C7C6369E for ; Thu, 19 Nov 2020 16:20:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D8E6424698 for ; Thu, 19 Nov 2020 16:20:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="UtO+zfQT" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728412AbgKSQUo (ORCPT ); Thu, 19 Nov 2020 11:20:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52962 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727734AbgKSQUn (ORCPT ); Thu, 19 Nov 2020 11:20:43 -0500 Received: from merlin.infradead.org (merlin.infradead.org [IPv6:2001:8b0:10b:1231::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8EC7EC0613CF; Thu, 19 Nov 2020 08:20:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description; bh=BaLzUQ3GKRTm+Bsx275rLFBfY2cJqM7f3zzkxOvpr50=; b=UtO+zfQTHQ5c21g7eN9pefLDaU 0UFlVxqM5t1oU9JlvnD0Cy0iKbsJPYC3spWy7ezdIKvgJgxQAQYdvLgeWa/ul1jSKmiaHHmMLx7gs lyqMRGynqnGGvz0EDr7dhcRU/khFp4awDT6L0/7XCsA2Fvd2L4GqYhPZHHB131psDfN1aN5JTqA83 Jd8XtwT1vkegCroEPdGESfgGhZCGi+dgkGiQX7zh67xbqOMzF0I8v9qLut92JcHzNNTqYlNtaYmmr tyfZJr+TOztdwBUasO1Kt3mTLyU5fOVgg7srbpQ/+meEE46aZ5M/9wTIPvwdFCStAsndtsm4hn9ZS byhaK4qA==; Received: from [2601:1c0:6280:3f0::bcc4] by merlin.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfmfo-0003cE-PV; Thu, 19 Nov 2020 16:20:41 +0000 Subject: Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful To: Thorsten Leemhuis , Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org References: <20201113153313.68ff210c@lwn.net> <458eb542-ff4d-e734-67fd-01e8378d4864@leemhuis.info> <20201118172958.5b014a44@lwn.net> From: Randy Dunlap Message-ID: Date: Thu, 19 Nov 2020 08:20:36 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/19/20 4:29 AM, Thorsten Leemhuis wrote: > Am 19.11.20 um 01:29 schrieb Jonathan Corbet: >> On Sun, 15 Nov 2020 11:13:52 +0100 >> Thorsten Leemhuis 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. > > Great, thx, much appreciated. > >> 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). > > Maybe just "reporting-issues.rst" or "reporting-issues-wip.rst". The text talks about issues anyway and rarely uses the word "bug". > >>  I do wonder if it should also move to the >>     process manual as part of this; not only admins will report bugs. > > > I had wondered about this myself a few weeks ago, but I assumed someone had good reasons to put it in the admin section. > > /me looks closer > > Hmmm, now I'm unsure myself where to place it: > >  * Documentation/admin/ is introduced as "The Linux kernel user’s and administrator’s guide" (https://www.kernel.org/doc/html/latest/admin-guide/). So maybe it's the right place that just uses a directory name that's easily misunderstood :-/ > >  * the process section starts with the words "So you want to be a Linux kernel developer? Welcome!" (https://www.kernel.org/doc/html/latest/process/). That might be a bit intimidating for people that just want to report a bug. > > I guess it's best if you decide. I prefer to leave it in /admin-guide/. -- ~Randy