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: <yq1y2y4tjng.fsf@oracle.com>
Date:   Tue, 01 Oct 2019 14:17:39 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Dan Williams <dan.j.williams@...el.com>,
        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@...el.com, linux-nvdimm@...ts.01.org,
        ksummit-discuss@...ts.linuxfoundation.org
Subject: Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile


Jonathan,

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

I think Documentation/process is the right place for all the common
practices and guidelines for code submission. Documentation is already
pretty big. And based on the discussions in this thread, I think we're
better off enhancing the existing process documents instead of
introducing more places for people to look.

-- 
Martin K. Petersen	Oracle Linux Engineering