From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Mailing list moderation and community openness
Date: Thu, 22 Mar 2018 00:56:27 +0100 [thread overview]
Message-ID: <0b40188c-bda8-e355-9ca1-1ab9cecd4615@gentoo.org> (raw)
In-Reply-To: <4aab96fa-0edb-6a28-791e-28e2103f2a30@gentoo.org>
Michael Palimaka schrieb:
> I see that in bug #650964[1] Council is pushing forward again with
> implementing user whitelisting on this mailing list (ie. anyone that is
> not "approved" will have their mail rejected).
>
> Could someone please explain how this doesn't directly contradict the
> core tenets of an open and inclusive community?
(I do not intend to single out your post, just replying to the thread in
general here)
I would like to ask people to stay respectful in their disagreement towards
the Council and their decision here. You might not agree with the decision,
but the Council is an elected body and was given these powers by the
developer community which they represent. Also I have no doubt that Council
members who voted for -dev moderation are aware of the counter arguments and
honestly expect a net positive effect from this.
If you dislike mailing list moderation, campaign and/or vote in the next
period for candidates who want to reverse this decision.
Best regards,
Chí-Thanh Christopher Nguyễn
next prev parent reply other threads:[~2018-03-21 23:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 12:17 [gentoo-dev] Mailing list moderation and community openness Michael Palimaka
2018-03-20 12:22 ` Kristian Fiskerstrand
2018-03-20 12:26 ` Lars Wendler
2018-03-20 13:41 ` Gregory Woodbury
2018-03-20 16:09 ` [gentoo-project] " Rich Freeman
2018-03-20 15:28 ` Matthew Thode
2018-03-20 18:17 ` Kristian Fiskerstrand
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22 0:24 ` Kristian Fiskerstrand
2018-03-21 5:36 ` Eray Aslan
2018-03-21 11:07 ` Rich Freeman
2018-03-21 14:44 ` Alec Warner
2018-03-21 16:31 ` Eray Aslan
2018-03-21 16:46 ` Alec Warner
2018-03-21 16:55 ` R0b0t1
2018-03-21 17:19 ` Rich Freeman
2018-03-21 23:44 ` Gregory Woodbury
2018-03-22 5:24 ` [gentoo-dev] " Duncan
2018-03-20 15:44 ` [gentoo-dev] " Alexander Berntsen
2018-03-20 16:03 ` William Hubbs
2018-03-20 23:54 ` Benda Xu
2018-03-21 0:08 ` Rich Freeman
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22 0:33 ` Kristian Fiskerstrand
2018-03-22 0:37 ` M. J. Everitt
2018-03-22 6:31 ` Benda Xu
2018-03-22 8:30 ` Alexander Berntsen
2018-03-22 11:38 ` Rich Freeman
2018-03-22 12:07 ` Kristian Fiskerstrand
2018-03-27 1:19 ` kuzetsa
2018-03-27 1:26 ` Rich Freeman
2018-03-27 2:38 ` kuzetsa
2018-03-27 7:35 ` Rich Freeman
2018-03-27 7:34 ` [gentoo-dev] " Martin Vaeth
2018-03-27 12:55 ` Rich Freeman
2018-03-27 16:12 ` Martin Vaeth
2018-03-27 16:39 ` Rich Freeman
2018-03-28 2:21 ` M. J. Everitt
2018-03-28 2:55 ` R0b0t1
2018-03-28 4:41 ` Stephen Christie
2018-03-28 13:48 ` Michael Orlitzky
2018-03-28 11:03 ` Rich Freeman
2018-03-28 6:11 ` Dawid Weglinski
2018-03-28 6:33 ` Martin Vaeth
2018-03-28 11:21 ` Rich Freeman
2018-03-29 7:13 ` Martin Vaeth
2018-06-11 1:55 ` R0b0t1
2018-03-20 15:53 ` [gentoo-dev] " Pengcheng Xu
2018-03-21 2:22 ` Paweł Hajdan, Jr.
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn [this message]
2018-03-22 0:27 ` Kristian Fiskerstrand
2018-06-10 18:29 ` Tom Wijsman
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=0b40188c-bda8-e355-9ca1-1ab9cecd4615@gentoo.org \
--to=chithanh@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