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 C8757138330 for ; Wed, 10 Jan 2018 20:49:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8BA96E0B0E; Wed, 10 Jan 2018 20:49:02 +0000 (UTC) Received: from avasout06.plus.net (avasout06.plus.net [212.159.14.18]) (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 F14C4E0833 for ; Wed, 10 Jan 2018 20:49:01 +0000 (UTC) Received: from [192.168.6.147] ([212.159.46.162]) by smtp with ESMTP id ZNIxeENgBe5nXZNIyenHKM; Wed, 10 Jan 2018 20:49:00 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.3 cv=TsHIegfh c=1 sm=1 tr=0 a=RuViaDnnNG9rfPLW4VJocg==:117 a=RuViaDnnNG9rfPLW4VJocg==:17 a=13zjGPudsaEWiJwPRgMA:9 a=r77TgQKjGQsHNAKrUKIA:9 a=7mOBRU54AAAA:8 a=T5MHzVyo8J7J-Gn0UVwA:9 a=A4mKhlwHUBc58mQ7:21 a=tAyzWnvMfA5TGn2c:21 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=9qR5i0uzvRi3fm3eUVkA:9 a=7OzpKEp-gE3DtQmB:21 a=tmHQhcULyaoinIBc:21 a=d8bg2F7-PsmH-ycP:21 a=_W_S_7VecoQA:10 a=4bwnPMfsP7eTq9pWnMoA:9 a=ONNS8QRKHyMA:10 a=wa9RWnbW_A1YIeRBVszw:22 Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list To: gentoo-dev@lists.gentoo.org References: <1685019.DAF74n7IXa@pinacolada> <1515578120.1284.5.camel@gentoo.org> <1515611196.1284.15.camel@gentoo.org> From: "M. J. Everitt" Openpgp: id=BA266E0525CFAB101523351B4C30334F93C22371 Message-ID: <5f92dd6c-a051-26f7-744a-a3810deb207f@iee.org> Date: Wed, 10 Jan 2018 20:48:55 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 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 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2dtcpLHBPJdvWpeDfoRENk781tknKjrms" X-CMAE-Envelope: MS4wfEppj1AzfltF5jBumrAxC5aJb86Ja8c0F7Z9si53kKvpRfzdXeV2zzGPAgKFw+RbiD1Os0oyI+P/meoX/8cJab8MY1EWcOqJl6QSFJe4rm9TTDeEleLj kuNkcgL9pF859I7468YHaSZW5t3Phrnrh2TObOQ9YAi/Yw1T3hSKwF/P7z1xQp3GAJD9mshPrnlpNg== X-Archives-Salt: 4be16241-c972-4bae-b0a8-876c192e5385 X-Archives-Hash: 5633a52c922428a42eabe3fbc35c6b5d This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2dtcpLHBPJdvWpeDfoRENk781tknKjrms Content-Type: multipart/mixed; boundary="mtfJ179C7mjKsGnofIpsKnb1pBvBI79F6"; protected-headers="v1" From: "M. J. Everitt" To: gentoo-dev@lists.gentoo.org Message-ID: <5f92dd6c-a051-26f7-744a-a3810deb207f@iee.org> Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list References: <1685019.DAF74n7IXa@pinacolada> <1515578120.1284.5.camel@gentoo.org> <1515611196.1284.15.camel@gentoo.org> In-Reply-To: --mtfJ179C7mjKsGnofIpsKnb1pBvBI79F6 Content-Type: multipart/alternative; boundary="------------FB7C7D349976DB3E69904BA5" This is a multi-part message in MIME format. --------------FB7C7D349976DB3E69904BA5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/01/18 19:31, Alec Warner wrote: > 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=E2=80=89-0800,= u=C5=BCytkownik 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=E2=80=89-0800, = u=C5=BCytkownik Matt > Turner > > > napisa=C5=82: > > > > On Tue, Jan 9, 2018 at 1:20 PM, Andreas K. Huettel > > 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 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 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 on > > > > > 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 someth= ing > 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 > =20 > > > -- > Best regards, > Micha=C5=82 G=C3=B3rny > > > Do I read a hint of sarcasm there too Alec?! :] --------------FB7C7D349976DB3E69904BA5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/01/18 19:31, Alec Warner wrote:
On Wed, Jan 10, 2018 at 2:06 PM, Micha=C5=82 G=C3=B3rny <mgorn= y@gentoo.org> wrote:
W dniu =C5=9Bro, 10.01.2= 018 o godzinie 09=E2=88=B611=E2=80=89-0800, u=C5=BCytkownik Mat= t Turner
napisa=C5=82:
> On Wed, Jan 10, 2018 at 1:55 AM, Micha=C5=82 G=C3=B3= rny <mgorny@gentoo.org> wrote:
> > W dniu wto, 09.01.2018 o godzinie 17=E2=88=B608=E2=80=89-0800, u=C5=BCytkownik Matt Turne= r
> > napisa=C5=82:
> > > On Tue, Jan 9, 2018 at 1:20 PM, Andreas K. Huettel <dilfridge@gentoo= =2Eorg> 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 is now.
> > > > * Posting to the list will only be possible to Gentoo developers 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 behaviour against the
> > > >=C2=A0 =C2=A0Code of Conduct [2] wil= l lead to revocation of the posting permission.
> > > >
> > > > 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 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.


Get membership posting privs.

-A
=C2=A0

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



Do I read a hint of sarcasm there too Alec?! :]
--------------FB7C7D349976DB3E69904BA5-- --mtfJ179C7mjKsGnofIpsKnb1pBvBI79F6-- --2dtcpLHBPJdvWpeDfoRENk781tknKjrms Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJaVnw7AAoJEGPnxnn01DHdusYQAJ/YL3K75GvJszCpsCbluhRE Bb6LsQgb1avErwQQJHB9zXdzLMcOr1iuSVkVsmUYLci9t+hI7ibfmF+HQLJ8Ni8L Twt37sOZ5wsFqk3wXjG5xk3tSZvJdVt5Zg060mFN93GXCGDEvDUgD8cdbovjRa0w glF6dwH0TnB6vWBSwPGHRDpjU+md0z70SjJM1m70wpwVS9NMvDoVvBM1yZ4OapAY O0+9idiljtPn2yzrYSGOv5zE2zZUdMHPmkuSLo0arhe13aa9Pe2q5qf3SIyWZBk6 kDN1ngiYJbAG05mCKiAUQjkTprp77bEYa1MYKWmz0FHX7ifzZr37hQLNi8cFl2zg fVMxoVeyzifVu+0+REIH6harlgAZmNDgxyF2V+dSinplNC7gGl2877mL6jCnyxjZ EBEL3mX5z9bkvQYDpEdH+MmrSMaS8dsHcUFbCop/dUBLw9omlirNlhXRFhTjzMhl aD8LiVt3PCiQur71a5vi8jvd5k4UicRKv1mqraOPQelPF9tSW/ERpXnXwOSpbVMC dHraIaIwGqvbnMoIKUMiZSLpy7UzdTU0ux82piQW8UDiM6Psp441k9KJ4SQbLHMo vkXMIze4hnsK0Wkxl8zD+0K/Geyu3FKfWhQtx3VGKboVA8bpLODqAK7NDqqj6t5X RBkUxA8QZGfTa0yCz3bN =+u4E -----END PGP SIGNATURE----- --2dtcpLHBPJdvWpeDfoRENk781tknKjrms--