From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-83369-garchives=archives.gentoo.org@lists.gentoo.org>
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 CB71C138330
for <garchives@archives.gentoo.org>; Wed, 10 Jan 2018 17:12:11 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id CA611E091E;
Wed, 10 Jan 2018 17:12:05 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(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 79049E0907
for <gentoo-dev@lists.gentoo.org>; Wed, 10 Jan 2018 17:12:05 +0000 (UTC)
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
(Authenticated sender: mattst88)
by smtp.gentoo.org (Postfix) with ESMTPSA id 5099B335C3E
for <gentoo-dev@lists.gentoo.org>; Wed, 10 Jan 2018 17:12:03 +0000 (UTC)
Received: by mail-io0-f178.google.com with SMTP id v30so184745iov.7
for <gentoo-dev@lists.gentoo.org>; Wed, 10 Jan 2018 09:12:03 -0800 (PST)
X-Gm-Message-State: AKwxyteRuhC7TovSmCdK4BqOoy8q+YayXu6rHhFFfZa0yT6+MY0YyzwT
oTLttD/vBarPdtSaPZrkPTs48mG5zUX55oWck5w=
X-Google-Smtp-Source: ACJfBotH3ZAKBJ3IwmDGf4mdBoWMLxLXxjbRFS9/XIrZhxBhOCgaD50O9ZiLaxGdJHOIQk/BcoQJlZsfH83ehbjMeH0=
X-Received: by 10.107.88.7 with SMTP id m7mr17553498iob.180.1515604321524;
Wed, 10 Jan 2018 09:12:01 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.2.180.80 with HTTP; Wed, 10 Jan 2018 09:11:40 -0800 (PST)
In-Reply-To: <1515578120.1284.5.camel@gentoo.org>
References: <1685019.DAF74n7IXa@pinacolada> <CAEdQ38FHD2F0AMULNUcBhtGhO-sD+zWffEsw3MJDJZOou4E_fQ@mail.gmail.com>
<1515578120.1284.5.camel@gentoo.org>
From: Matt Turner <mattst88@gentoo.org>
Date: Wed, 10 Jan 2018 09:11:40 -0800
X-Gmail-Original-Message-ID: <CAEdQ38F7bn3sOLdcPVxv+md_kmVoKLMhwzYofB2b73xuPUHLMQ@mail.gmail.com>
Message-ID: <CAEdQ38F7bn3sOLdcPVxv+md_kmVoKLMhwzYofB2b73xuPUHLMQ@mail.gmail.com>
Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev
mailing list
To: gentoo development <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 2d8e7a9b-731b-4aa8-9a81-f2d35daca729
X-Archives-Hash: b79c4a300f896cb31557110ce646ebde
On Wed, Jan 10, 2018 at 1:55 AM, Micha=C5=82 G=C3=B3rny <mgorny@gentoo.org>=
wrote:
> W dniu wto, 09.01.2018 o godzinie 17=E2=88=B608=E2=80=89-0800, u=C5=BCytk=
ownik Matt Turner
> napisa=C5=82:
>> On Tue, Jan 9, 2018 at 1:20 PM, Andreas K. Huettel <dilfridge@gentoo.org=
> wrote:
>> > During the last Gentoo council meeting, the decision was made to imple=
ment
>> > changes to the gentoo-dev mailing list [1].
>> >
>> > These changes affect only the gentoo-dev mailing list, and will come i=
nto
>> > effect on 23 January 2018.
>> >
>> > * 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.
>> > * Whitelisting requires that one developer vouches for you. We intend =
this
>> > to be as unbureaucratic as possible.
>> > * Obviously, repeated off-topic posting as well as behaviour against t=
he
>> > Code of Conduct [2] will lead to revocation of the posting permissio=
n.
>> >
>> > If, as a non-developer, you want to participate in a discussion on
>> > gentoo-dev,
>> > - either reply directly to the author of a list mail and ask him/her t=
o
>> > forward your message,
>> > - or ask any Gentoo developer of your choice to get you whitelisted.
>> >
>> > If, as a developer, you want to have someone whitelisted, please comme=
nt on
>> > bug 644070 [3]. Similar to Bugzilla editbugs permission, if you are vo=
uching
>> > for a contributor you are expected to keep an eye on their activity.
>>
>> It seems like the obvious way this fails is some Gentoo developer acks
>> one of the problem people. I don't think that's particularly unlikely.
>> Then what do we do?
>>
>
> Then it becomes comrel business.
If that was an effective solution, wouldn't the problem already be solved?