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 579FBB75 for ; Thu, 15 Nov 2018 07:58:29 +0000 (UTC) Received: from mail-vk1-f193.google.com (mail-vk1-f193.google.com [209.85.221.193]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 90FDB196 for ; Thu, 15 Nov 2018 07:58:28 +0000 (UTC) Received: by mail-vk1-f193.google.com with SMTP id o130so4267229vke.10 for ; Wed, 14 Nov 2018 23:58:28 -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: <154225760492.2499188.14152986544451112930.stgit@dwillia2-desk3.amr.corp.intel.com> From: Geert Uytterhoeven Date: Thu, 15 Nov 2018 08:58:15 +0100 Message-ID: To: Dan Williams 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 , stfrench@microsoft.com, Greg KH , Mauro Carvalho Chehab , Dmitry Vyukov , "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 Dan, On Thu, Nov 15, 2018 at 6:05 AM 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 > > The goal of the Subsystem Profile is to set expectations for > contributors and interim or replacement maintainers for a subsystem. > > See Documentation/maintainer/subsystem-profile.rst for more details, and > a follow-on example profile for the libnvdimm subsystem. > Signed-off-by: Dan Williams Thanks for your patch! > --- /dev/null > +++ b/Documentation/maintainer/subsystem-profile.rst > +Last -rc to merge features > +-------------------------- > +Indicate to contributors the point at which an as yet un-applied patch > +set will need to wait for the NEXT+1 merge window. Of course there is no > +obligation to ever except any given patchset, but if the review has not s/except/accept/ > +concluded by this point the expectation the contributor should wait and expectation is (that) > +resubmit for the following merge window. The answer may be different for > +'Core:' files, include a second entry prefixed with 'Core:' if so. 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