1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
All- |
5 |
|
6 |
The flamewars on public communication channels is out of hand. it's |
7 |
having an negative effect in many parts of gentoo, even those that are |
8 |
not directly affected by the said war. This is something that urgently |
9 |
needs to be addressed. |
10 |
|
11 |
So, here is my proposal. I hope it's not the only one. |
12 |
|
13 |
creation of a etiquette enforcement group. This group should be a |
14 |
subproject of devrel, but should not be made up of devrel members. I |
15 |
say this because the actions and powers of this group need to be |
16 |
separated from devrel. |
17 |
|
18 |
This group should be composed of well respected members of our dev |
19 |
community that have demonstrated the ability to diffuse situations that |
20 |
would have otherwise became a flamewar. The new group would act like |
21 |
our current ombudsman group, except that the target is different. I'll |
22 |
try to give some examples. |
23 |
|
24 |
IRC: |
25 |
<clueless> Hi, I'm writing an ebuild and I want to install stuff to |
26 |
/usr/local |
27 |
<informed> Well, that's a bad idea. ebuilds should never install to |
28 |
/usr/local |
29 |
<troll> clueless: you moron! ebuilds can't install to /usr/local, go |
30 |
jump off a bridge! |
31 |
<enforcer> troll: if you can't say something constructive, then please |
32 |
don't say anything. |
33 |
.... |
34 |
<clueless> I still want to install to /usr/local. my ebuild isn't meant |
35 |
for the tree, only my private use, and I feel that I should be able to |
36 |
do it. |
37 |
<informed> Well, then you want to check out http://foo.bar/blah as it |
38 |
explains how to use insinto and doins. |
39 |
<troll> You fucking moron, you can't do that! |
40 |
<enforcer> troll: you were warned, and now you're banned for the next |
41 |
hour. please go do something else and cool off. |
42 |
- - enforcer sets modes +q troll for #foobar |
43 |
|
44 |
Mailing list enforcement is the same concept. One warning and then a |
45 |
short term ban.(yes, we have possibly found a way to enforce short term |
46 |
bans on MLs) |
47 |
|
48 |
Why does this work? |
49 |
I believe that most people who get caught up in trolling do it |
50 |
unintentionally. Usually a "hey, you're being an asshat" will be enough |
51 |
to stop the flamefest. |
52 |
|
53 |
Sometimes people need a bigger kick in the ass though, which is where a |
54 |
short term ban helps. When I say a short term ban, I mean 30-90 |
55 |
minutes. it allows everyone to cool off without them using bad judgment |
56 |
and popping back in. I do similar enforcement in #-amd64 and it works |
57 |
very well. |
58 |
|
59 |
This still doesn't address repeat offenders and people who troll for |
60 |
sport. It's possible that the short term bans will work, but that is |
61 |
something that we will only find out with experience. |
62 |
|
63 |
Preventing abuse of short term ban powers: |
64 |
one of the first things that everyone will(and should) be worried about |
65 |
is this group abusing their powers. To prevent the enforcement group |
66 |
from abusing their powers, the following safety checks would be put into |
67 |
place. |
68 |
|
69 |
1. any and every action that the enforcer uses to enforce etiquette |
70 |
needs to be immediately and publicly documented. as a start I recommend |
71 |
sending a email to gentoo-devrel ML. This includes full logs/archive |
72 |
pointers. |
73 |
|
74 |
2. enforcers are not allowed to use their power more than twice |
75 |
consecutively on the same person/group. |
76 |
|
77 |
3. every action that an enforcer takes will be reviewed by at least 2 |
78 |
devrel members. |
79 |
|
80 |
4. if an enforcer has effected a ban on a person/group and the subject |
81 |
was a time sensitive topic, then the enforcer is obligated to relay |
82 |
messages verbatim from the person/group for the duration of the ban. |
83 |
|
84 |
5. any group/person affected by the ban may request a devrel hearing |
85 |
about the ban in question. These need to be handled as fast as |
86 |
possible. At devrel's discretion, devrel may immediately remove the |
87 |
enforcer from the enforcement group or issue a warning to the enforcer. |
88 |
|
89 |
6. no enforcer shall have more than 2 warnings in a 6 month period and |
90 |
never more than 3 in a year. |
91 |
|
92 |
|
93 |
So, these are my thoughts. there is still a lot to be worked out if we |
94 |
decide that this is the best approach. |
95 |
|
96 |
All comments are welcome, and if you want to troll, direct it to your |
97 |
nearest brick wall. |
98 |
|
99 |
- -- |
100 |
======================================================= |
101 |
Mike Doty kingtaco@g.o |
102 |
Gentoo/AMD64 Strategic Lead PGP Key: 0xA797C7A7 |
103 |
Gentoo Developer Relations |
104 |
===GPG Fingerprint=== |
105 |
0094 7F06 913E 78D6 F1BB 06BA D0AD D125 A797 C7A7 |
106 |
======================================================= |
107 |
-----BEGIN PGP SIGNATURE----- |
108 |
Version: GnuPG v1.4.3 (GNU/Linux) |
109 |
|
110 |
iD8DBQFEbM3P0K3RJaeXx6cRAgskAKDITJIYHgKshXPir3CTHi1HtpnPSgCg4Pot |
111 |
6v1cACeqj6/2njYZsUG/+uU= |
112 |
=apF6 |
113 |
-----END PGP SIGNATURE----- |
114 |
-- |
115 |
gentoo-devrel@g.o mailing list |