linux-kernel - Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private

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: <5C24FB2A-D2C0-4D95-A0C0-B48C4B8D5AF4@vmware.com>
Date:   Tue, 9 Nov 2021 00:58:48 +0000
From:   Nadav Amit <namit@...are.com>
To:     Joe Perches <joe@...ches.com>
CC:     "srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>,
        Juergen Gross <jgross@...e.com>, X86 ML <x86@...nel.org>,
        Pv-drivers <Pv-drivers@...are.com>,
        Vivek Thampi <vithampi@...are.com>,
        Vishal Bhakta <vbhakta@...are.com>,
        Ronak Doshi <doshir@...are.com>,
        Linux-graphics-maintainer <Linux-graphics-maintainer@...are.com>,
        "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
        Zack Rusin <zackr@...are.com>, Deep Shah <sdeep@...are.com>,
        Alexey Makhalov <amakhalov@...are.com>,
        Linux Virtualization <virtualization@...ts.linux-foundation.org>,
        Keerthana Kalyanasundaram <keerthanak@...are.com>,
        Srivatsa Bhat <srivatsab@...are.com>,
        Anish Swaminathan <anishs@...are.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as
 private



> On Nov 8, 2021, at 4:37 PM, Joe Perches <joe@...ches.com> wrote:
> 
> On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote:
> 
> So it's an exploder not an actual maintainer and it likely isn't
> publically archived with any normal list mechanism.
> 
> So IMO "private" isn't appropriate.  Neither is "L:"
> Perhaps just mark it as what it is as an "exploder".
> 
> Or maybe these blocks should be similar to:
> 
> M:	Name of Lead Developer <somebody@...are.com>
> M:	VMware <foo> maintainers <linux-<foo>-maintainers@...inux.com>
> 
> Maybe something like a comment mechanism should be added to the
> MAINTAINERS file.
> 
> Maybe #
> 
> so this entry could be something like:
> 
> M:	VMware <foo> maintainers <linux-<foo>-maintainers@...inux.com> # VMware's ever changing internal maintainers list

Admittedly, I do not care much about how it turns to be.

But if it is modified, it should be very clear who the maintainer
is, and not to entangle the mailing list and the maintainer.

I am personally not subscribed to the internal pv-drivers mailing
list, which is not just for memory ballooning, and is also listed
as a maintainer for vmmouse, pvscsi, vmxnet3 and others.

As I am the only maintainer of VMware balloon, if someone is
mistaken and sends an email only to the mailing list and not me,
he might be disappointed.