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 654B1138330 for ; Wed, 10 Jan 2018 19:31:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B871E0A6D; Wed, 10 Jan 2018 19:31:42 +0000 (UTC) Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 F1BACE0A4A for ; Wed, 10 Jan 2018 19:31:41 +0000 (UTC) Received: by mail-ua0-x22b.google.com with SMTP id x10so69719ual.8 for ; Wed, 10 Jan 2018 11:31:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scriptkitty-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=TU12wcjtp4RILFpjXES+3oc44BB4+Jt91YbtDplTMs8=; b=0eFauwHHSN+mKBtEng1BKbtgD/xjuc2buqazmhXMyepX/LmlP4dZV+tN7pzrCKBqzi 7JOp7MtciWLkTouHYFKkvtK2GJXplebCMq4slEl4pWoObhR9ZiKhZX3ZIQvTl9Vad9g5 1Mu4AUc0V41ZxyoJmFIxOoxwWmXUoTmh+FbBIlPHin4H5lDOi8VxpBlwAyYm7DOioAN5 7nD5VIeECazHlgpZq9mhO70VDlbyzu1bmRCj30nJqmDpyilQOFwb10D+JoUAK6xkrZI5 ogMb3qmMx0UDVVo5jYukQTAFhRss3cOuuxJMEHonsvWfWbKc1Xetxws995H6bRQfDDFM yhUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=TU12wcjtp4RILFpjXES+3oc44BB4+Jt91YbtDplTMs8=; b=SOHSymr0ALIKNpeBo1dTwR4Y08dxm0gZTrbHlLUDlbDzrv5enCbO4GuXYEUo0jgA5/ ae9rcY/vqZK7uSOXUi1vpHG8jHqm44eFMwd1c9H1Q7DMzVt0z61m7BTMhsTxVLGZacN9 hLvt+fS2KdJIx+lygNPF+QgKuPi0wQy5kMFq1bAoushYEefjgthD7iWJNwXk0nBvagTB IBJPDxsr6LUAl6ZCmYySiCsXkuZM/ogoHWrK7/DxgFwON7HGfd2pOo/S+mwXZrhS5j5K 3V2Tl6RaCpvtSgSiRmkwEepu4YHxf36dDSsreJrSwQITG9NDARsepo+ov9srm0zfa6i5 RUog== X-Gm-Message-State: AKwxyte0B0bAuewwdZg52Q9mOcLqvpPRaArQXVsMolwbB5K9mzoNrj/N eCVLcD283g6J7cQE3/h3BFN+90tjP/3n4PDlV7Hysu3n X-Google-Smtp-Source: ACJfBovo29ZE5s3/hUR9iVlryCXeiHGI8jp9b6jbXmG9yhd8+48PzLuoE5zvq9tD5L4rMMGViVepfe0gYN0DkUSeZ14= X-Received: by 10.176.13.131 with SMTP id i3mr19288740uak.107.1515612700530; Wed, 10 Jan 2018 11:31:40 -0800 (PST) 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 Sender: antarus@scriptkitty.com Received: by 10.159.54.141 with HTTP; Wed, 10 Jan 2018 11:31:40 -0800 (PST) X-Originating-IP: [2620:0:1003:410:70fb:b96d:b61a:b6c5] In-Reply-To: <1515611196.1284.15.camel@gentoo.org> References: <1685019.DAF74n7IXa@pinacolada> <1515578120.1284.5.camel@gentoo.org> <1515611196.1284.15.camel@gentoo.org> From: Alec Warner Date: Wed, 10 Jan 2018 14:31:40 -0500 X-Google-Sender-Auth: fexrdVc9ct8MPa1dobveSCZqPqM Message-ID: Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list To: Gentoo Dev Content-Type: multipart/alternative; boundary="089e0825a544a1fa4f05627114fe" X-Archives-Salt: 37baa6db-0697-4922-af97-e93193b95a3f X-Archives-Hash: 1f1d6904514e470a6bf9ab33c95bc4af --089e0825a544a1fa4f05627114fe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jan 10, 2018 at 2:06 PM, Micha=C5=82 G=C3=B3rny = wrote: > W dniu =C5=9Bro, 10.01.2018 o godzinie 09=E2=88=B611 -0800, u=C5=BCytkown= ik Matt Turner > napisa=C5=82: > > On Wed, Jan 10, 2018 at 1:55 AM, Micha=C5=82 G=C3=B3rny wrote: > > > W dniu wto, 09.01.2018 o godzinie 17=E2=88=B608 -0800, u=C5=BCytkowni= k 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 > implement > > > > > changes to the gentoo-dev mailing list [1]. > > > > > > > > > > These changes affect only the gentoo-dev mailing list, and will > come into > > > > > effect on 23 January 2018. > > > > > > > > > > * Subscribing to the list and receiving list mail remains as it i= s > 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 the > > > > > Code of Conduct [2] will lead to revocation of the posting > permission. > > > > > > > > > > If, as a non-developer, you want to participate in a discussion o= n > > > > > gentoo-dev, > > > > > - either reply directly to the author of a list mail and ask > him/her to > > > > > 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 > comment on > > > > > bug 644070 [3]. Similar to Bugzilla editbugs permission, if you > are vouching > > > > > 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? > > One of the problems mentioned before was that a person could easily > evade the ban via subscribing from another e-mail address. In this case > it's no longer possible, as he would need to obtain the vouching for his > new e-mail address, and for that he would first have to have something > positive to post. > > Of course this relies on developers not vouching for new people out of > the blue but expecting them to have something to contribute first. > This sounds like an amazing fundraising opportunity. https://www.gentoo.org/donate/ Get membership posting privs. -A > > -- > Best regards, > Micha=C5=82 G=C3=B3rny > > > --089e0825a544a1fa4f05627114fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On W= ed, Jan 10, 2018 at 2:06 PM, Micha=C5=82 G=C3=B3rny <<= a href=3D"mailto:mgorny@gentoo.org" target=3D"_blank">mgorny@gentoo.org= > wrote:
W d= niu =C5=9Bro, 10.01.2018 o godzinie 09=E2=88=B611=E2=80=89-0800, u=C5=BCytk= ownik Matt Turner
napisa=C5=82:
> 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=BCytkownik 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 wa= s made to implement
> > > > changes to the gentoo-dev mailing list [1].
> > > >
> > > > These changes affect only the gentoo-dev mailing list, = and will come into
> > > > effect on 23 January 2018.
> > > >
> > > > * Subscribing to the list and receiving list mail remai= ns as it is now.
> > > > * Posting to the list will only be possible to Gentoo d= evelopers and
> > > >=C2=A0 =C2=A0whitelisted additional participants.
> > > > * Whitelisting requires that one developer vouches for = you. We intend this
> > > >=C2=A0 =C2=A0to be as unbureaucratic as possible.
> > > > * Obviously, repeated off-topic posting as well as beha= viour against the
> > > >=C2=A0 =C2=A0Code of Conduct [2] will lead to revocation= of the posting permission.
> > > >
> > > > If, as a non-developer, you want to participate in a di= scussion on
> > > > gentoo-dev,
> > > > - either reply directly to the author of a list mail an= d ask him/her to
> > > > forward your message,
> > > > - or ask any Gentoo developer of your choice to get you= whitelisted.
> > > >
> > > > If, as a developer, you want to have someone whiteliste= d, please comment on
> > > > bug 644070 [3]. Similar to Bugzilla editbugs permission= , if you are vouching
> > > > for a contributor you are expected to keep an eye on th= eir activity.
> > >
> > > It seems like the obvious way this fails is some Gentoo deve= loper acks
> > > one of the problem people. I don't think that's part= icularly unlikely.
> > > Then what do we do?
> > >
> >
> > Then it becomes comrel business.
>
> If that was an effective solution, wouldn't the problem already be= solved?

One of the problems mentioned before was that a person could ea= sily
evade the ban via subscribing from another e-mail address. In this case
it's no longer possible, as he would need to obtain the vouching for hi= s
new e-mail address, and for that he would first have to have something
positive to post.

Of course this relies on developers not vouching for new people out of
the blue but expecting them to have something to contribute first.

This sounds like an amazing fundraising opportu= nity.


Get membersh= ip posting privs.

-A
=C2=A0

--
Best regards,
Micha=C5=82 G=C3=B3rny



--089e0825a544a1fa4f05627114fe--