From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B994C1381F1 for ; Fri, 12 Jan 2018 23:59:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7F716E08D9; Fri, 12 Jan 2018 23:58:57 +0000 (UTC) Received: from lisa.pbhware.com (lisa.pbhware.com [96.251.22.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 087F1E08CE for ; Fri, 12 Jan 2018 23:58:56 +0000 (UTC) Received: from bender.it-sys.cpp.edu (bender.it-sys.cpp.edu [134.71.250.134]) by smtp.pbhware.com (OpenSMTPD) with ESMTPSA id 0b25e0f1 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Fri, 12 Jan 2018 15:58:53 -0800 (PST) Date: Fri, 12 Jan 2018 15:58:52 -0800 From: "Paul B. Henson" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list Message-ID: <20180112235850.GE4494@bender.it-sys.cpp.edu> References: <1685019.DAF74n7IXa@pinacolada> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1685019.DAF74n7IXa@pinacolada> User-Agent: Mutt/1.7.2 (2016-11-26) X-Archives-Salt: 9c64aac7-d431-422f-b1d6-79a905d4dc05 X-Archives-Hash: b16d04de23e6a76ed1316bbfc3157276 On Tue, Jan 09, 2018 at 10:20:56PM +0100, Andreas K. Huettel wrote: > * Subscribing to the list and receiving list mail remains as it is now. > * Posting to the list will only be possible to Gentoo developers and > whitelisted additional participants. Any chance you'd consider automatically white-listing all current proxy maintainers :)? > * Whitelisting requires that one developer vouches for you. We intend this > to be as unbureaucratic as possible. Or should I go harass the dev that usually commits my changes? Arguably, being a proxy maintainer already implies at least one dev thinks you're not a total idiot, as random users can't add themselves to the package metadata on their own. Thanks...