From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A2FBBC9D for ; Thu, 15 Nov 2018 07:59:56 +0000 (UTC) Received: from mail-vs1-f66.google.com (mail-vs1-f66.google.com [209.85.217.66]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2C0C8196 for ; Thu, 15 Nov 2018 07:59:56 +0000 (UTC) Received: by mail-vs1-f66.google.com with SMTP id v10so3769502vsv.12 for ; Wed, 14 Nov 2018 23:59:56 -0800 (PST) MIME-Version: 1.0 References: <154225759358.2499188.15268218778137905050.stgit@dwillia2-desk3.amr.corp.intel.com> <154225760492.2499188.14152986544451112930.stgit@dwillia2-desk3.amr.corp.intel.com> In-Reply-To: From: Geert Uytterhoeven Date: Thu, 15 Nov 2018 08:59:43 +0100 Message-ID: To: Julia Lawall Content-Type: text/plain; charset="UTF-8" Cc: ksummit-discuss@lists.linuxfoundation.org, "linux-nvdimm@lists.01.org" , vishal.l.verma@intel.com, Linux Kernel Mailing List , Dmitry Vyukov , Greg KH , Mauro Carvalho Chehab , stfrench@microsoft.com, "Tobin C. Harding" Subject: Re: [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: Subsystem Profile List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Julia, On Thu, Nov 15, 2018 at 6:48 AM Julia Lawall wrote: > On Wed, 14 Nov 2018, Dan Williams wrote: > > As presented at the 2018 Linux Plumbers conference [1], the Subsystem > > Profile is proposed as a way to reduce friction between committers and > > maintainers and perhaps encourage conversations amongst maintainers > > about best practice policies. > > > > The profile contains short answers to some of the common policy > > questions a contributor might have, or that a maintainer might consider > > formalizing. The current list of maintenance policies is: > > > > Overview: General introduction to maintaining the subsystem > > Core: List of source files considered core > > Leaf: List of source files that consume core functionality > > Patches or Pull requests: Simple statement of expected submission format > > Last -rc for new feature submissions: Expected lead time for submissions > > Last -rc to merge features: Deadline for merge decisions > > Non-author Ack / Review Tags Required: Patch review economics > > Test Suite: Pass this suite before requesting inclusion > > Resubmit Cadence: When to ping the maintainer > > Trusted Reviewers: Help for triaging patches > > Time Zone / Office Hours: When might a maintainer be available > > Checkpatch / Style Cleanups: Policy on pure cleanup patches > > Off-list review: Request for review gates > > TODO: Potential development tasks up for grabs, or active focus areas > > How about patch subject lines? What is the formula that should be used to > transform the name(s) of the affected file(s) into an appropriate suject > line? Automating that may be difficult. I always use "git log --oneline", and try to derive something sane from its output. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vs1-f67.google.com (mail-vs1-f67.google.com [209.85.217.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 685AF21191725 for ; Wed, 14 Nov 2018 23:59:56 -0800 (PST) Received: by mail-vs1-f67.google.com with SMTP id t17so11154500vsc.8 for ; Wed, 14 Nov 2018 23:59:56 -0800 (PST) MIME-Version: 1.0 References: <154225759358.2499188.15268218778137905050.stgit@dwillia2-desk3.amr.corp.intel.com> <154225760492.2499188.14152986544451112930.stgit@dwillia2-desk3.amr.corp.intel.com> In-Reply-To: From: Geert Uytterhoeven Date: Thu, 15 Nov 2018 08:59:43 +0100 Message-ID: Subject: Re: [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: Subsystem Profile List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Julia Lawall Cc: ksummit-discuss@lists.linuxfoundation.org, "linux-nvdimm@lists.01.org" , Linux Kernel Mailing List , Dmitry Vyukov , Greg KH , Mauro Carvalho Chehab , stfrench@microsoft.com, "Tobin C. Harding" List-ID: Hi Julia, On Thu, Nov 15, 2018 at 6:48 AM Julia Lawall wrote: > On Wed, 14 Nov 2018, Dan Williams wrote: > > As presented at the 2018 Linux Plumbers conference [1], the Subsystem > > Profile is proposed as a way to reduce friction between committers and > > maintainers and perhaps encourage conversations amongst maintainers > > about best practice policies. > > > > The profile contains short answers to some of the common policy > > questions a contributor might have, or that a maintainer might consider > > formalizing. The current list of maintenance policies is: > > > > Overview: General introduction to maintaining the subsystem > > Core: List of source files considered core > > Leaf: List of source files that consume core functionality > > Patches or Pull requests: Simple statement of expected submission format > > Last -rc for new feature submissions: Expected lead time for submissions > > Last -rc to merge features: Deadline for merge decisions > > Non-author Ack / Review Tags Required: Patch review economics > > Test Suite: Pass this suite before requesting inclusion > > Resubmit Cadence: When to ping the maintainer > > Trusted Reviewers: Help for triaging patches > > Time Zone / Office Hours: When might a maintainer be available > > Checkpatch / Style Cleanups: Policy on pure cleanup patches > > Off-list review: Request for review gates > > TODO: Potential development tasks up for grabs, or active focus areas > > How about patch subject lines? What is the formula that should be used to > transform the name(s) of the affected file(s) into an appropriate suject > line? Automating that may be difficult. I always use "git log --oneline", and try to derive something sane from its output. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm 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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 7B2FFC43441 for ; Thu, 15 Nov 2018 07:59:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 45A8422419 for ; Thu, 15 Nov 2018 07:59:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 45A8422419 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728831AbeKOSGl (ORCPT ); Thu, 15 Nov 2018 13:06:41 -0500 Received: from mail-vs1-f66.google.com ([209.85.217.66]:34369 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726574AbeKOSGl (ORCPT ); Thu, 15 Nov 2018 13:06:41 -0500 Received: by mail-vs1-f66.google.com with SMTP id y27so11201497vsi.1 for ; Wed, 14 Nov 2018 23:59:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i20C0xmyPMlO06G+9sXE07nm8g7Bo2ErRitswHLva/8=; b=CJaw9lccSSkb6VPS7+Zw0O3gM7kPayD48i7mewVO0v+7G8hqUJ/53HMXf+VAUaMwv0 1y5LW21O0hhIfnRIrNDqIBd35omjThOoJylY8nkNpoR955fZvq0mFKMWas2/s03y4OOr dRFCyWM+eXzxUqxf4n+S0OkzyV+P/dJgILS8R0vFjEzjm4MMC8madwWOVPKUokBNvHMi B/XABpAFqczisGcJWond1UGAR0M4dIpBYt60Y5HmYMZMfpA+K2QQoTQoPgykw7WSxP/x Uj9FIyV1YmqOekmsiHyYYDJ5qJUARcudtnLegDukB7JYorxDzCfw/ft5ZSUyURdMqHHG pVqg== X-Gm-Message-State: AGRZ1gL7MvRgPUQsZINlJGX1L3AJS3Z87fO3C5CKLiARKiuD+6LSFOpv XiX5XY3/xx+tUZyckHDp5niPS3O9CSy+qkmZUxM= X-Google-Smtp-Source: AJdET5fyLLi5gq+en8eiYHuGrOlKz+bVlarp9/QdEKlIMT8lG1lIuAH7hlhTGTYWarBTbryNqgIkaFMvOSWvJAXJpy0= X-Received: by 2002:a67:c202:: with SMTP id i2mr2040011vsj.11.1542268795132; Wed, 14 Nov 2018 23:59:55 -0800 (PST) MIME-Version: 1.0 References: <154225759358.2499188.15268218778137905050.stgit@dwillia2-desk3.amr.corp.intel.com> <154225760492.2499188.14152986544451112930.stgit@dwillia2-desk3.amr.corp.intel.com> In-Reply-To: From: Geert Uytterhoeven Date: Thu, 15 Nov 2018 08:59:43 +0100 Message-ID: Subject: Re: [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: Subsystem Profile To: Julia Lawall Cc: Dan Williams , ksummit-discuss@lists.linuxfoundation.org, "linux-nvdimm@lists.01.org" , vishal.l.verma@intel.com, Linux Kernel Mailing List , stfrench@microsoft.com, Greg KH , Mauro Carvalho Chehab , Dmitry Vyukov , "Tobin C. Harding" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Julia, On Thu, Nov 15, 2018 at 6:48 AM Julia Lawall wrote: > On Wed, 14 Nov 2018, Dan Williams wrote: > > As presented at the 2018 Linux Plumbers conference [1], the Subsystem > > Profile is proposed as a way to reduce friction between committers and > > maintainers and perhaps encourage conversations amongst maintainers > > about best practice policies. > > > > The profile contains short answers to some of the common policy > > questions a contributor might have, or that a maintainer might consider > > formalizing. The current list of maintenance policies is: > > > > Overview: General introduction to maintaining the subsystem > > Core: List of source files considered core > > Leaf: List of source files that consume core functionality > > Patches or Pull requests: Simple statement of expected submission format > > Last -rc for new feature submissions: Expected lead time for submissions > > Last -rc to merge features: Deadline for merge decisions > > Non-author Ack / Review Tags Required: Patch review economics > > Test Suite: Pass this suite before requesting inclusion > > Resubmit Cadence: When to ping the maintainer > > Trusted Reviewers: Help for triaging patches > > Time Zone / Office Hours: When might a maintainer be available > > Checkpatch / Style Cleanups: Policy on pure cleanup patches > > Off-list review: Request for review gates > > TODO: Potential development tasks up for grabs, or active focus areas > > How about patch subject lines? What is the formula that should be used to > transform the name(s) of the affected file(s) into an appropriate suject > line? Automating that may be difficult. I always use "git log --oneline", and try to derive something sane from its output. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds