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=-5.2 required=3.0 tests=BAYES_00, 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 C4BC5C63697 for ; Thu, 19 Nov 2020 12:30:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 705AA246F1 for ; Thu, 19 Nov 2020 12:30:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727194AbgKSM37 (ORCPT ); Thu, 19 Nov 2020 07:29:59 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45316 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725783AbgKSM35 (ORCPT ); Thu, 19 Nov 2020 07:29:57 -0500 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 43288C0613CF; Thu, 19 Nov 2020 04:29:57 -0800 (PST) Received: from ip4d149f6e.dynamic.kabel-deutschland.de ([77.20.159.110] helo=[192.168.66.101]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1kfj4S-0001JF-0u; Thu, 19 Nov 2020 13:29:52 +0100 To: Jonathan Corbet Cc: Randy Dunlap , 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: Thorsten Leemhuis Subject: Re: [RFC PATCH v2 00/26] Make reporting-bugs easier to grasp and yet more detailed & helpful Message-ID: Date: Thu, 19 Nov 2020 13:29:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20201118172958.5b014a44@lwn.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;linux@leemhuis.info;1605788997;cd067995; X-HE-SMSGID: 1kfj4S-0001JF-0u Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > - 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. Will do. > - Dual licensed CC-SA-4.0 is fine with me. CC-BY is OK if you really > want to do it that way. I'm unsure and would appreciate options from others here. Here are some of my thoughts about this: What do we loose by dual-licensing it under a liberal license like CC-BY? It afaics makes it a lot more attractive for websites or books authors to use this text as a base, as they don't need to fear that "share alike" or the GPL might have consequences on the surroundings. I'd say that's a good thing for the kernel, as it increases the chances the texts built upon ours remain close to what we expect on this topic. That's why I currently think using CC-BY is a good idea. > Either way, though, you'll need to add the > license itself under LICENSES/preferred before it can go into the SPDX > tag. Agh, yes, of course, will keep it in mind when above point is settled. Ciao, Thorsten