[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181113231537.GR2089@sirena.org.uk>
Date: Tue, 13 Nov 2018 15:15:37 -0800
From: Mark Brown <broonie@...nel.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Theodore Ts'o <tytso@....edu>,
Peter Zijlstra <peterz@...radead.org>,
Jonathan Corbet <corbet@....net>,
Thomas Gleixner <tglx@...utronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
John Stultz <john.stultz@...aro.org>, acme@...hat.com,
frederic@...nel.org, Andy Lutomirski <luto@...nel.org>,
Marc Zyngier <marc.zyngier@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Will Deacon <will.deacon@....com>
Subject: Re: [patch 0/2] Documentation/process: Add subsystem/tree handbook
On Thu, Nov 08, 2018 at 09:32:18AM -0800, Dan Williams wrote:
> On Thu, Nov 8, 2018 at 8:32 AM Mark Brown <broonie@...nel.org> wrote:
> > I'm not 100% sure that people will pick up that the topic is about a
> > handbook for working with maintainers rather than a handbook for being a
> > maintainer from that title...
> The intent is a handbook for being a maintainer. However, in the
> process of describing how a given sub-system is maintained one also
> needs to describe the local rules. So contributors should be able to
> glean what matters to a sub-system from a description of how that
> sub-system is maintained. In other words the direct audience is
> maintainers, but it also hopefully makes the process more transparent
> for contributors.
To me that sounds like a document aimed at contributors rather than
maintainers.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists