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 9D097138330 for ; Wed, 10 Jan 2018 23:27:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D4DF6E0C4B; Wed, 10 Jan 2018 23:27:46 +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 55FCEE0BCF for ; Wed, 10 Jan 2018 23:27:46 +0000 (UTC) Received: from [192.168.6.147] ([212.159.46.162]) by smtp with ESMTP id ZPmZeElMUe5nXZPmaenKck; Wed, 10 Jan 2018 23:27:44 +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=7mOBRU54AAAA:8 a=EQjEw30YNIg8Zu6Vo-sA:9 a=QEXdDO2ut3YA:10 a=I6Fi_KmIbDrYd9HSposA: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> From: "M. J. Everitt" Openpgp: id=BA266E0525CFAB101523351B4C30334F93C22371 Message-ID: <449e4c39-2a78-2699-b4af-679b1e1458f7@iee.org> Date: Wed, 10 Jan 2018 23:27:39 +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="E39P4n8D8l18OQeX5R67vWb5dRe2K707j" X-CMAE-Envelope: MS4wfErXH2EqGOF07zbGhwDB3Kpb4q5rFBfdE2eqVOnG1BNoiWBVmAyCFNxRn8H3qw9mvJpZyTiTtFQlBBadKhALrLtIRutvSXUDxadw4O1UWWzLyyO4BlFj etWgCV/GVYkpSlmD2BPPY0gyAXiKUqB7mmapEPvNleAZCj/TxmR72iSS0/0Qw3IlQdYhD8NCO8lXjA== X-Archives-Salt: 166211f7-17b7-4b4c-bfb1-008a5c7ea61d X-Archives-Hash: 684698bbcb9b71abeb4c88d8e7febb0a This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --E39P4n8D8l18OQeX5R67vWb5dRe2K707j Content-Type: multipart/mixed; boundary="VDoIhSd3avvteGM816oexjqLgO0fGFVal"; protected-headers="v1" From: "M. J. Everitt" To: gentoo-dev@lists.gentoo.org Message-ID: <449e4c39-2a78-2699-b4af-679b1e1458f7@iee.org> Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list References: <1685019.DAF74n7IXa@pinacolada> In-Reply-To: --VDoIhSd3avvteGM816oexjqLgO0fGFVal Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/01/18 23:20, Rich Freeman wrote: > On Wed, Jan 10, 2018 at 5:28 PM, Roy Bamford = wrote: >> Being somwhat old and cynical, I'm seeing signs of history >> repeating itself. >> >> Does being 'struck off' the list in this way apply to devs, including >> Council and comrel members? >> > It would seem that this question is already answered: > https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct#Consequenc= es > > Being banned from lists or removal of dev status (which would also > remove posting privs unless whitelisted) are already listed as > potential consequences for refusal to comply with the CoC. > I have to ask a stupid question here .. how do devs apply to return to the list? Via other devs, council, Comrel, the Foundation, Infra, or what? (the "select few"/clique/club/etc?) I think Roy's point is quite valid .. if you want to cut out users from contribution why are you even posting on -dev ML in the first place? Use -core and/or #-dev IRC .. or is this simply an attempt to replicate #-dev IRC as a ML .. and you simply move the "problem" elsewhere .. and then apply sanctions to that system also .. you create a rod for your own back ... I'm tending towards the idea that this is a technical "solution" to a non-technical problem, and as such, nobody is capable of "fixing" that ..= --VDoIhSd3avvteGM816oexjqLgO0fGFVal-- --E39P4n8D8l18OQeX5R67vWb5dRe2K707j 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 iQIcBAEBCAAGBQJaVqFvAAoJEGPnxnn01DHdpf0P/iT1uTyCXKmYzAUc+UygnuTG pKURLFkJ0sYqwVsflZdv00jwZ0cYJMdAqUG/3S9yrKLilxqTS4pfmUharRuWsvzO rOLSpK236HHkwPqy53h9YnvexkNIIdtt4j1LVww3y6X9GiH0u9fEwswEh2OFNPIP +o0tyc8/GyNITQ7CIMpG00XV2t9kiXwP+bg+VUtOsD2hx4n1Com36J9EhsCVkoCq M4UCWIGlY9beW5jd8onvHVEpnq35PqgXHiEZVYgxZcCYdkVxqkwnrdBxqYeDXBju ugkz0HPbZqsVi8LSPeZB0nHc/yYamnitYZsMCQi5jw7cjVhdqvAmpgXG56KujKNe vQWyQoKg3hIS8zJ/sWUwMzQyzfGNKLgNmTrrLoywormFEIzgCCwBNKxBZrxzaLXZ v9Lx6hlN9UzRc7B/Udt24TSbKrX2AGZitmySq1jBJe2SwZVBjgA4AX5UBP7wHJkV yVzKMYY2q2eQvmvax7T+VwwfEs9WKpo16QvKJJYzczrB+jzBgk2BDdoZZ0b5TBRo g0vVuGHR+3v2sGOXDB7gVIsepybYnmJIEpbMmqMWRR0N3zZfgkrE1SfcN0UVvjOW mNzngfY+++kkfF0to0mEve8GYCiExTQZ8edMhxiitj2uXDCBarNUjtAqzO476YOr ug864lAYs4Ca7gMkR54P =9HFf -----END PGP SIGNATURE----- --E39P4n8D8l18OQeX5R67vWb5dRe2K707j--