Re: [Ksummit-discuss] [RFC PATCH 2/3] MAINTAINERS, Handbook: Subsystem Profile

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 <dan.j.williams(a)intel.com&gt;

--- /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

+concluded by this point the expectation the contributor should wait and

+resubmit for the following merge window. The answer may be different for +'Core:' files, include a second entry prefixed with 'Core:' if so.