From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 75232385829C for ; Fri, 2 Sep 2022 10:32:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 75232385829C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 4BA4E302AB2C for ; Fri, 2 Sep 2022 12:32:13 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 021D4403DCA4; Fri, 2 Sep 2022 12:32:12 +0200 (CEST) Message-ID: <5c9b5cd2c4207bf049727e90578a265762a08935.camel@klomp.org> Subject: Re: move bugzilla account request email to another list? From: Mark Wielaard To: Overseers mailing list Date: Fri, 02 Sep 2022 12:32:12 +0200 In-Reply-To: <20220901163010.4v2i6qi5jwhjfib4@cgf.cx> References: <20220901163010.4v2i6qi5jwhjfib4@cgf.cx> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Chris, On Thu, 2022-09-01 at 12:30 -0400, Christopher Faylor via Overseers wrote: > I think we've reached the point where the bugzilla account request email > should be moved to another list. As it stands now, I have a tendency > to ignore this list because most of the traffic does not really pertain > to overseeing sourceware.org. Right. Thanks for creating the admin-requests@ mailinglist and for updating the bugzilla template/maintainer parameter (I git committed it because the data dir changes are not automatically snapshotted). Now that overseers@ is more public/advertised it is also a good idea to keep the admin-requests list non-public so people's addresses and ssh pubkeys aren't unnecessarily advertised. Thanks, Mark