Gentoo Archives: gentoo-dev

From: Martin Vaeth <martin@×××××.de>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Mailing list moderation and community openness
Date: Wed, 28 Mar 2018 06:36:21
Message-Id: slrnpbmdul.j1l.martin@lounge.imp.fu-berlin.de
In Reply to: Re: [gentoo-dev] Re: Mailing list moderation and community openness by Rich Freeman
1 Rich Freeman <rich0@g.o> wrote:
2 >
3 > Fred is a community member. Fred consistently harasses and trolls new
4 > contributors in private.
5
6 Sure, it's a problem. But not a problem which can be solved by
7 closing the mailing list, in no step of the issue.
8
9 First of all, this happens in private, so you cannot prevent it
10 by closing a mailing list.
11
12 > No mention is made of why Fred as booted out, because everything
13 > happened in private.
14
15 That's the mistake which is made in this example. Be open in the
16 decisions. If you cannot be open in order to protect other people's
17 privacy, be open at least by saying exactly this.
18
19 > Now a bunch of community members get upset about Fred being booted out
20 > without reason. Fred claims it is because he disagrees with the
21 > leadership on something. People start arguing endlessly about
22 > openness.
23
24 Yes, this might happen due to the non-openness. This might happen even
25 if you are open. And nothing will prevent it. Closing a mailing list
26 will not close such a debate; it will then just happen elsewhere.
27 Anyway, such a debate does not belong to dev-ml. The correct solution
28 is to continue to point people to have this debate on the appropriate place,
29 not on the mainly technically oriented dev-ml. Making the posters silent
30 by blacklisting even more is contra-productive and will give the
31 impression that they are actually right. As it is a commonplace:
32 You cannot solve social problems by technical measurements.
33
34 > Ultimately the leaders just want Fred gone so that new contributors
35 > aren't getting driven away. They can't explain that because then they
36 > create potential civil liability for the project.
37
38 Why not? Is it against a law to exclude somebody who is hurting a
39 project? If it is (or if there is a danger that it is), then the
40 problem is not that they cannot explain it but that they must not
41 do it in the first place.
42 In any case, this is a different problem and cannot be solved by
43 closing a mailing list.
44
45 > The problem is that
46 > the debate goes on for over a year despite intervening elections and
47 > now this becomes the issue that is driving new contributors away.
48 > What solution would you propose for this problem?
49
50 How would closing the mailing list solve the problem? It will give
51 the impression that you want to close the debate by taking away the
52 medium where people can argue. And the impression is correct, because
53 this actually *is* the intention if you are honest.
54 Of course, it will not close said debate. The debate will just happen
55 on another channel. (Which in this example might be appropriate, but
56 pointing to the proper channel is what should have happened and not
57 closing a mailing list and thus excluding random people from posting
58 things about clompletely different topics which *are* on-topic on dev-ml).
59
60 > Sure, but we can at least force the negative advertising of Gentoo to
61 > go elsewhere, rather than basically paying to run a negative PR
62 > campaign against ourselves.
63
64 Closing dev-ml will not help here. If people have a strong
65 disagreement with a decision, this will happen on gentoo channels.
66 If you want to prevent it technically, you have to close all channels.
67
68 > And what about the freedom to endlessly troll and harass you and
69 > others? [...]
70
71 Closing a mailing list will not prevent this.
72 Somebody who behaves this way (or feels being treated wrong) will not
73 stop this only because one channel is closed for him.
74 What is really happening by closing the mailing list is that you stop
75 innocent contributors.
76
77 In any case, that's the discussion blacklisting vs. whitelisting:
78 To stop one specific single poster, blacklisting is enough,
79 at least for the beginning. Sure, technically it can be circumvented,
80 but you will not stop this social problem anyway by technical means.
81
82 > Surely Gentoo's mission isn't to run completely unrestricated forums
83 > for discussion of anything and everything. Our main purpose here is
84 > to maintain a Linux distro, not provide a platform for anybody who has
85 > an opinion on anything.
86
87 Sure, pointing to the right channel is appropriate. This is something
88 completely else than to prevent posting *by default*.
89
90 > without being endlessly trolled and harassed.
91
92 This is unrelated about closing the mailing list. Especially if this
93 happened in private, anyway.
94
95 BTW, I do not think that contributors are that blue-eyed that they
96 will stop contributing only because one person does not know how to
97 behave. Especially if it is made clear somewhere that this happens
98 in disagreement with gentoo as a whole. *This* might be a way how
99 one might react to such a problem. Anyway, this discussion now is
100 getting off-topic: All these problems have nothing to do with
101 closing a ml and cannot be solved by this.

Replies