From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Mailing list moderation and community openness
Date: Tue, 27 Mar 2018 07:34:10 +0000 (UTC) [thread overview]
Message-ID: <p9cs5i$co7$1@blaine.gmane.org> (raw)
In-Reply-To: CAGfcS_nfVWtaq6cJz2m_-OB2+poVmxeYWi3sgUY9qHoxoKQWrg@mail.gmail.com
Rich Freeman <rich0@gentoo.org> wrote:
> On Tue, Mar 20, 2018 at 7:54 PM, Benda Xu <heroxbd@gentoo.org> wrote:
>>
>> It boils down to an attitude of assuming outsiders are good (blacklist
>> to ML) or bad (whitelist to ML) by default.
++
This is the most crucial point.
It is the general attitude: Does Gentoo welcome contributions
or want to make their developers live in an ivory tower?
It is about openness vs. isolation.
> It is
> basically impossible to blacklist somebody on a mailing list, since
> all they need to do is roll up a new email address.
That may be technically true but it is not a problem the mailing list
is currently facing. If it should eventually happen to be the case
that the mailing list is filled by tons of spam of anonymous posters
or faked identities causing serious problems, one can still think about
changing the modus operandi.
But without such an absolute need, it is very bad to restrict freedom.
next prev parent reply other threads:[~2018-03-27 7:36 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 ` Martin Vaeth [this message]
2018-03-27 12:55 ` [gentoo-dev] " 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
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='p9cs5i$co7$1@blaine.gmane.org' \
--to=martin@mvath.de \
--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