From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9C0C3C433F5 for ; Tue, 9 Nov 2021 00:38:00 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3EAEA6113A for ; Tue, 9 Nov 2021 00:38:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 3EAEA6113A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=perches.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id E18984016A; Tue, 9 Nov 2021 00:37:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fonwiB_oTiOt; Tue, 9 Nov 2021 00:37:58 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [IPv6:2605:bc80:3010:104::8cd3:938]) by smtp2.osuosl.org (Postfix) with ESMTPS id 18CC3400E4; Tue, 9 Nov 2021 00:37:58 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id E6EACC0019; Tue, 9 Nov 2021 00:37:57 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2D691C000E for ; Tue, 9 Nov 2021 00:37:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 19D2D40125 for ; Tue, 9 Nov 2021 00:37:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrJ0QxV4WqZW for ; Tue, 9 Nov 2021 00:37:56 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from smtprelay.hostedemail.com (smtprelay0079.hostedemail.com [216.40.44.79]) by smtp2.osuosl.org (Postfix) with ESMTPS id 00854400E4 for ; Tue, 9 Nov 2021 00:37:55 +0000 (UTC) Received: from omf14.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay07.hostedemail.com (Postfix) with ESMTP id B17CE18499AA5; Tue, 9 Nov 2021 00:37:53 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: joe@perches.com) by omf14.hostedemail.com (Postfix) with ESMTPA id 280E4268E45; Tue, 9 Nov 2021 00:37:48 +0000 (UTC) Message-ID: Subject: Re: [PATCH 2/2] MAINTAINERS: Mark VMware mailing list entries as private From: Joe Perches To: "Srivatsa S. Bhat" , jgross@suse.com, x86@kernel.org, pv-drivers@vmware.com Date: Mon, 08 Nov 2021 16:37:46 -0800 In-Reply-To: References: <163640336232.62866.489924062999332446.stgit@srivatsa-dev> <163640339370.62866.3435211389009241865.stgit@srivatsa-dev> <5179a7c097e0bb88f95642a394f53c53e64b66b1.camel@perches.com> User-Agent: Evolution 3.40.4-1 MIME-Version: 1.0 X-Rspamd-Server: rspamout04 X-Rspamd-Queue-Id: 280E4268E45 X-Stat-Signature: nb9hoi3t69ayygs8x58pxmai5y393qhi X-Session-Marker: 6A6F6540706572636865732E636F6D X-Session-ID: U2FsdGVkX1+/yA5i3mf5Qcbygfb34RS/hVZ8PmXw7yU= X-HE-Tag: 1636418268-383849 Cc: amakhalov@vmware.com, Ronak Doshi , linux-scsi@vger.kernel.org, anishs@vmware.com, Vishal Bhakta , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, virtualization@lists.linux-foundation.org, keerthanak@vmware.com, linux-rdma@vger.kernel.org, gregkh@linuxfoundation.org, linux-graphics-maintainer@vmware.com, linux-input@vger.kernel.org, Nadav Amit , Thomas Gleixner , Zack Rusin X-BeenThere: virtualization@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Linux virtualization List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" On Mon, 2021-11-08 at 16:22 -0800, Srivatsa S. Bhat wrote: > +Greg, Thomas > > Hi Joe, > > On 11/8/21 3:37 PM, Joe Perches wrote: > > On Mon, 2021-11-08 at 12:30 -0800, Srivatsa S. Bhat wrote: > > > From: Srivatsa S. Bhat (VMware) > > > > > > VMware mailing lists in the MAINTAINERS file are private lists meant > > > for VMware-internal review/notification for patches to the respective > > > subsystems. So, in an earlier discussion [1][2], it was recommended to > > > mark them as such. Update all the remaining VMware mailing list > > > references to use that format -- "L: list@address (private)". > > [] > > > diff --git a/MAINTAINERS b/MAINTAINERS > > [] > > > @@ -6134,8 +6134,8 @@ T: git git://anongit.freedesktop.org/drm/drm-misc > > > F: drivers/gpu/drm/vboxvideo/ > > > > > > DRM DRIVER FOR VMWARE VIRTUAL GPU > > > -M: "VMware Graphics" > > > M: Zack Rusin > > > +L: linux-graphics-maintainer@vmware.com (private) > > > > This MAINTAINERS file is for _public_ use, marking something > > non-public isn't useful. > > > > private makes no sense and likely these L: entries shouldn't exist. > > Well, the public can send messages to this list, but membership is > restricted. Ah, new information. That's not quite what the commit message describes. > In many ways, I believe this is similar to x86@kernel.org, which is an > email alias that anyone can post to in order to reach the x86 > maintainer community for patch review. I see x86@kernel.org listed as > both L: and M: in the MAINTAINERS file, among different entries. > > Although the @vmware list ids refer to VMware-internal mailing lists > as opposed to email aliases, they serve a very similar purpose -- to > inform VMware folks about patches to the relevant subsystems. > > Is there a consensus on how such lists should be specified? Not so far as I know. > One > suggestion (from Greg in the email thread referenced above) was to > mark it as private, which is what this patch does. Maybe we can find a > better alternative? > > How about specifying such lists using M: (indicating that this address > can be used to reach maintainers), as long as that is not the only M: > entry for a given subsystem (i.e., it includes real people's email id > as well)? I think that would address Greg's primary objection too from > that other thread (related to personal responsibility as maintainers). 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 M: VMware maintainers -maintainers@vmlinux.com> Maybe something like a comment mechanism should be added to the MAINTAINERS file. Maybe # so this entry could be something like: M: VMware maintainers -maintainers@vmlinux.com> # VMware's ever changing internal maintainers list _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization