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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 84CD2C352AA for ; Tue, 1 Oct 2019 13:56:17 +0000 (UTC) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5D6EF21855 for ; Tue, 1 Oct 2019 13:56:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5D6EF21855 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lwn.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=ksummit-discuss-bounces@lists.linuxfoundation.org Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id C2EA8136B; Tue, 1 Oct 2019 13:56:16 +0000 (UTC) Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id BE9821368 for ; Tue, 1 Oct 2019 13:56:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 634608AF for ; Tue, 1 Oct 2019 13:56:01 +0000 (UTC) Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 32FD6491; Tue, 1 Oct 2019 13:56:00 +0000 (UTC) Date: Tue, 1 Oct 2019 07:55:59 -0600 From: Jonathan Corbet To: Dan Williams Message-ID: <20191001075559.629eb059@lwn.net> In-Reply-To: <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> Organization: LWN.net MIME-Version: 1.0 Cc: vishal.l.verma@intel.com, ksummit-discuss@lists.linuxfoundation.org, linux-nvdimm@lists.01.org, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Dmitry Vyukov , Mauro Carvalho Chehab , Steve French , "Tobin C. Harding" Subject: Re: [Ksummit-discuss] [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile X-BeenThere: ksummit-discuss@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ksummit-discuss-bounces@lists.linuxfoundation.org Errors-To: ksummit-discuss-bounces@lists.linuxfoundation.org On Wed, 11 Sep 2019 08:48:54 -0700 Dan Williams wrote: > As presented at the 2018 Linux Plumbers conference [1], the Maintainer > Entry Profile (formerly Subsystem Profile) is proposed as a way to reduce > friction between committers and maintainers and encourage conversations > amongst maintainers about common best practices. While coding-style, > submit-checklist, and submitting-drivers lay out some common expectations > there remain local customs and maintainer preferences that vary by > subsystem. > > The profile contains short answers to some of the common policy questions a > contributor might have that are local to the subsystem / device-driver, or > otherwise not covered by the top-level process documents. > > Overview: General introduction to how the subsystem operates > Submit Checklist Addendum: Mechanical items that gate submission staging > Key Cycle Dates: > - Last -rc for new feature submissions: Expected lead time for submissions > - Last -rc to merge features: Deadline for merge decisions > Coding Style Addendum: Clarifications of local style preferences > Resubmit Cadence: When to ping the maintainer > Checkpatch / Style Cleanups: Policy on pure cleanup patches So I'm finally back home after my European tour, and I have it on good authority that my bag might even get here eventually too. That means I'm digging through a pile of docs stuff I've been neglecting badly... My intention is to apply these patches. But as I was reading through them, one little nagging thing came to mind... > See Documentation/maintainer/maintainer-entry-profile.rst for more details, > and a follow-on example profile for the libnvdimm subsystem. Thus far, the maintainer guide is focused on how to *be* a maintainer. This document, instead, is more about how to deal with specific maintainers. So I suspect that Documentation/maintainer might be the wrong place for it. Should we maybe place it instead under Documentation/process, or even create a new top-level "book" for this information? Thanks, jon _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss 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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 1094CECE58A for ; Tue, 1 Oct 2019 13:56:04 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D3E752190F for ; Tue, 1 Oct 2019 13:56:03 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D3E752190F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lwn.net Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from new-ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id A5A8E10FC71F3; Tue, 1 Oct 2019 06:57:31 -0700 (PDT) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=45.79.88.28; helo=ms.lwn.net; envelope-from=corbet@lwn.net; receiver= Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 059EC10096C9B for ; Tue, 1 Oct 2019 06:57:29 -0700 (PDT) Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 32FD6491; Tue, 1 Oct 2019 13:56:00 +0000 (UTC) Date: Tue, 1 Oct 2019 07:55:59 -0600 From: Jonathan Corbet To: Dan Williams Subject: Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile Message-ID: <20191001075559.629eb059@lwn.net> In-Reply-To: <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> Organization: LWN.net MIME-Version: 1.0 Message-ID-Hash: GP3CEOHGQ5PGGZVNK7M2ZYZTUP5EYQRT X-Message-ID-Hash: GP3CEOHGQ5PGGZVNK7M2ZYZTUP5EYQRT X-MailFrom: corbet@lwn.net X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation CC: linux-kernel@vger.kernel.org, Thomas Gleixner , Mauro Carvalho Chehab , Steve French , Greg Kroah-Hartman , Linus Torvalds , "Tobin C. Harding" , Olof Johansson , Daniel Vetter , Joe Perches , Dmitry Vyukov , Alexandre Belloni , linux-nvdimm@lists.01.org, ksummit-discuss@lists.linuxfoundation.org X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: <> List-Archive: <> List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, 11 Sep 2019 08:48:54 -0700 Dan Williams wrote: > As presented at the 2018 Linux Plumbers conference [1], the Maintainer > Entry Profile (formerly Subsystem Profile) is proposed as a way to reduce > friction between committers and maintainers and encourage conversations > amongst maintainers about common best practices. While coding-style, > submit-checklist, and submitting-drivers lay out some common expectations > there remain local customs and maintainer preferences that vary by > subsystem. > > The profile contains short answers to some of the common policy questions a > contributor might have that are local to the subsystem / device-driver, or > otherwise not covered by the top-level process documents. > > Overview: General introduction to how the subsystem operates > Submit Checklist Addendum: Mechanical items that gate submission staging > Key Cycle Dates: > - Last -rc for new feature submissions: Expected lead time for submissions > - Last -rc to merge features: Deadline for merge decisions > Coding Style Addendum: Clarifications of local style preferences > Resubmit Cadence: When to ping the maintainer > Checkpatch / Style Cleanups: Policy on pure cleanup patches So I'm finally back home after my European tour, and I have it on good authority that my bag might even get here eventually too. That means I'm digging through a pile of docs stuff I've been neglecting badly... My intention is to apply these patches. But as I was reading through them, one little nagging thing came to mind... > See Documentation/maintainer/maintainer-entry-profile.rst for more details, > and a follow-on example profile for the libnvdimm subsystem. Thus far, the maintainer guide is focused on how to *be* a maintainer. This document, instead, is more about how to deal with specific maintainers. So I suspect that Documentation/maintainer might be the wrong place for it. Should we maybe place it instead under Documentation/process, or even create a new top-level "book" for this information? Thanks, jon _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org 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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 CDF85ECE587 for ; Tue, 1 Oct 2019 13:56:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AA7D221855 for ; Tue, 1 Oct 2019 13:56:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388862AbfJAN4B (ORCPT ); Tue, 1 Oct 2019 09:56:01 -0400 Received: from ms.lwn.net ([45.79.88.28]:36920 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726710AbfJAN4B (ORCPT ); Tue, 1 Oct 2019 09:56:01 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 32FD6491; Tue, 1 Oct 2019 13:56:00 +0000 (UTC) Date: Tue, 1 Oct 2019 07:55:59 -0600 From: Jonathan Corbet To: Dan Williams Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , Mauro Carvalho Chehab , Steve French , Greg Kroah-Hartman , Linus Torvalds , "Tobin C. Harding" , Olof Johansson , "Martin K. Petersen" , Daniel Vetter , Joe Perches , Dmitry Vyukov , Alexandre Belloni , vishal.l.verma@intel.com, linux-nvdimm@lists.01.org, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile Message-ID: <20191001075559.629eb059@lwn.net> In-Reply-To: <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693396.2951081.7340292149329436920.stgit@dwillia2-desk3.amr.corp.intel.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 11 Sep 2019 08:48:54 -0700 Dan Williams wrote: > As presented at the 2018 Linux Plumbers conference [1], the Maintainer > Entry Profile (formerly Subsystem Profile) is proposed as a way to reduce > friction between committers and maintainers and encourage conversations > amongst maintainers about common best practices. While coding-style, > submit-checklist, and submitting-drivers lay out some common expectations > there remain local customs and maintainer preferences that vary by > subsystem. > > The profile contains short answers to some of the common policy questions a > contributor might have that are local to the subsystem / device-driver, or > otherwise not covered by the top-level process documents. > > Overview: General introduction to how the subsystem operates > Submit Checklist Addendum: Mechanical items that gate submission staging > Key Cycle Dates: > - Last -rc for new feature submissions: Expected lead time for submissions > - Last -rc to merge features: Deadline for merge decisions > Coding Style Addendum: Clarifications of local style preferences > Resubmit Cadence: When to ping the maintainer > Checkpatch / Style Cleanups: Policy on pure cleanup patches So I'm finally back home after my European tour, and I have it on good authority that my bag might even get here eventually too. That means I'm digging through a pile of docs stuff I've been neglecting badly... My intention is to apply these patches. But as I was reading through them, one little nagging thing came to mind... > See Documentation/maintainer/maintainer-entry-profile.rst for more details, > and a follow-on example profile for the libnvdimm subsystem. Thus far, the maintainer guide is focused on how to *be* a maintainer. This document, instead, is more about how to deal with specific maintainers. So I suspect that Documentation/maintainer might be the wrong place for it. Should we maybe place it instead under Documentation/process, or even create a new top-level "book" for this information? Thanks, jon