linux-kernel - Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPcyv4ihn9kgO-VDOK=Jyj8RrG2RVXUvu8Y66zR7JYZm9-rWPA@mail.gmail.com>
Date:   Thu, 7 Nov 2019 18:41:46 -0800
From:   Dan Williams <dan.j.williams@...el.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Steve French <stfrench@...rosoft.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Tobin C. Harding" <me@...in.cc>, Olof Johansson <olof@...om.net>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Joe Perches <joe@...ches.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Vishal L Verma <vishal.l.verma@...el.com>,
        linux-nvdimm <linux-nvdimm@...ts.01.org>,
        ksummit <ksummit-discuss@...ts.linuxfoundation.org>
Subject: Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile

On Thu, Nov 7, 2019 at 12:13 PM Jonathan Corbet <corbet@....net> wrote:
>
> Hi, Dan,
>
> A month or so ago I wrote...
>
> > > 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?
>
> Unless I missed it, I've not heard back from you on this.  I'd like to get
> this stuff pulled in for 5.5 if possible...  would you object if I were to
> apply your patches, then tack on a move over to the process guide?

Sorry for the delay.

Yes, the process book is a better location now that this information
is focused on being supplemental guidelines for submitters rather than
a "how to maintain X subsystem" guide.

I do want to respin this without the Coding Style addendum to address
the specific feedback there, but other than that I'm happy to see this
move forward.