public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list
Date: Thu, 11 Jan 2018 02:03:33 +0100	[thread overview]
Message-ID: <5975969.qpFnRmUSA1@pinacolada> (raw)
In-Reply-To: <rhf9V1P1yINFO3wJhpB6cC@0TvigF5UhqkqegzqTWpxw>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

> Does being 'struck off' the list in this way apply to devs, including
> Council and comrel members?

So far noone has even considered "striking" devs off the list. If this even 
were to happen ever, it would have to be backed by a full comrel team decision 
/ vote. And these don't happen often, don't happen quickly, and don't happen 
lightly. (I much prefer fixing the glibc ebuilds, horrible as these may be.)

We have now an imperfect solution to an unneccessary problem. If anyone can 
come up with a better solution (that is still an improvement over doing 
nothing), I'm all ears. List moderation is not one, since a) it still hasn't 
been implemented technically, b) even if that were done, we would still 
require an active moderation team, and c) then we start bikeshedding about the 
moderation rules.


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2018-01-11  1:03 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 21:20 [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list Andreas K. Huettel
2018-01-09 22:20 ` Francesco Riosa
2018-01-09 22:27   ` Alec Warner
2018-01-10  0:37 ` Philip Webb
2018-01-10  1:24   ` Michael Orlitzky
2018-01-10  1:08 ` Matt Turner
2018-01-10  9:55   ` Michał Górny
2018-01-10 17:11     ` Matt Turner
2018-01-10 19:06       ` Michał Górny
2018-01-10 19:31         ` Alec Warner
2018-01-10 19:45           ` Michał Górny
2018-01-10 20:48           ` M. J. Everitt
2018-01-10 21:13             ` Alec Warner
2018-01-10  5:48 ` Eray Aslan
2018-01-10  7:55   ` Lars Wendler
2018-01-10 10:57     ` David Seifert
2018-01-10 13:49       ` kuzetsa
2018-01-10 14:50         ` M. J. Everitt
2018-01-15 13:26       ` Tom H
2018-01-15 15:09         ` Rich Freeman
2018-01-15 22:49           ` Gordon Pettey
2018-01-10 14:55     ` Alexander Berntsen
2018-01-10 15:09       ` M. J. Everitt
2018-01-10 15:52       ` kuzetsa
2018-01-11  7:03     ` Eray Aslan
2018-01-11  8:30       ` Lars Wendler
2018-01-10  9:53   ` Michał Górny
2018-01-10 11:14     ` Andreas K. Huettel
2018-01-10 17:16     ` Vincent-Xavier JUMEL
2018-01-10 19:44       ` Michał Górny
2018-01-11  1:12       ` Andreas K. Huettel
2018-01-11  4:22         ` [gentoo-dev] " Duncan
2018-01-11  5:37           ` Gordon Pettey
2018-01-11  8:21             ` Lars Wendler
2018-01-11 17:07         ` [gentoo-dev] " Peter Stuge
2018-01-11 17:34           ` Rich Freeman
2018-01-11 17:59             ` Matthias Maier
2018-01-13  0:02           ` Paul B. Henson
2018-01-11 14:48     ` R0b0t1
2018-01-11 17:03     ` Chí-Thanh Christopher Nguyễn
2018-01-10 19:56 ` Fabian Groffen
2018-01-10 22:28 ` Roy Bamford
2018-01-10 23:20   ` Rich Freeman
2018-01-10 23:27     ` M. J. Everitt
2018-01-10 23:35       ` Rich Freeman
2018-01-10 23:39         ` M. J. Everitt
2018-01-11  1:03   ` Andreas K. Huettel [this message]
2018-01-11 11:44     ` Roy Bamford
2018-01-11  3:22 ` [gentoo-dev] Re: [gentoo-dev-announce] " Benda Xu
2018-01-11 19:54   ` William Hubbs
2018-01-12 23:58 ` [gentoo-dev] " Paul B. Henson
2018-03-20  8:52 ` Kristian Fiskerstrand
2018-03-24  3:11   ` Francisco Blas Izquierdo Riera (klondike)
2018-03-24  3:34     ` Aaron Bauman
2018-03-25  4:07       ` Francisco Blas Izquierdo Riera (klondike)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5975969.qpFnRmUSA1@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox