1 |
On 12:26 Thu 10 Jul , Ferris McCormick wrote: |
2 |
> On Wed, 2008-07-09 at 22:49 -0700, Donnie Berkholz wrote: |
3 |
> 2. But for both devrel and userrel, the Code of Conduct loses almost |
4 |
> all its impact unless response is immediate --- CoC's intent, I think, |
5 |
> is to help keep the mailing lists and #gentoo-dev channel on track |
6 |
> pretty much in real time. I know this was the original idea behind it, |
7 |
> and this was one reason we felt we needed people outside devrel to help |
8 |
> enforce it (devrel is not set up for immediate responses); |
9 |
|
10 |
The concepts of poisonous people and repeat offenders are explicitly |
11 |
mentioned numerous times in the 20070308 council meeting. Here are some |
12 |
examples: |
13 |
|
14 |
<wolf31o2|mobile> kloeri: banning people from the lists, not |
15 |
necessarily... but reducing the requirements on devrel to suspend |
16 |
"repeat offenders" might just make them think about their actions before |
17 |
doing them, and that could decrease the flames a bit |
18 |
|
19 |
<kloeri> there's some devs that are persistently poisoning the project |
20 |
that I want to deal with but that's not just related to mailinglists |
21 |
|
22 |
<wolf31o2|mobile> christel: agreed... I think we need to be a bit more |
23 |
strict on our developers... after all, in the flames involving users, |
24 |
developers are just as much at fault as the users... perhaps if the devs |
25 |
didn't respond in kind, the flames would subside much quicker, etc |
26 |
|
27 |
<kloeri> I don't want to ban anybody but I do want to be much harder on |
28 |
devs poisoning things consistently and I'm going to file at least one |
29 |
devrel bug in that regard |
30 |
|
31 |
<kloeri> I don't think we can force people to follow netiquette in |
32 |
general but we can do more to smack devs up when they're constantly |
33 |
being a pain in the ass |
34 |
|
35 |
|
36 |
On the topic of userrel's power to ban people from lists, which is a |
37 |
long-term action: |
38 |
|
39 |
<robbat2> on the side of devrel not having 'teeth' - kloeri mentioned |
40 |
before that infra previously wasn't very responsive to requests to do |
41 |
things (he cited a userrel request to remove user from the ML) |
42 |
|
43 |
<christel> i have a question, if we are to start enforcing etiquette |
44 |
policy, i think we may want to ensure we have one which also cover users |
45 |
|
46 |
> 4. That is, we (devrel, userrel, averyone else perhaps) should use Code |
47 |
> of Conduct to stop elaborate flame wars before they can burn out of |
48 |
> control. Whether a flame war ever merits a bug will vary from situation |
49 |
> to situation, but generally if we have a flame war and wish to impose |
50 |
> some sort of sanctions because of it, we really need to be hitting |
51 |
> several people or none with warnings or brief "vacations." |
52 |
|
53 |
I agree that we should attempt to take short-term actions in response to |
54 |
immediate offenses. |
55 |
|
56 |
> 5. I am not sure where the current Code of Conduct document is, but |
57 |
> I'll volunteer to help update it to bring it into line with how we wish |
58 |
> to use it and to help clarify who has what authority under it, and that |
59 |
> sort of thing. I have come to support it, and I'd like to help make it |
60 |
> more effectively used in the rather narrow context for which it was |
61 |
> designed before we consider extending its reach. |
62 |
|
63 |
On the topic of trying to write down every possible way to go about |
64 |
this, I also agree with them: |
65 |
|
66 |
<g2boojum> christel: I actually think you want it to be more vague than |
67 |
specific. "Don't be a jerk." Please don't define "jerk", or you get a |
68 |
five-page treatise on why the bahavior doesn't really fit the |
69 |
definition. |
70 |
|
71 |
<seemant> we really need to be careful in adopting document upon |
72 |
document upon document |
73 |
|
74 |
-- |
75 |
Thanks, |
76 |
Donnie |
77 |
|
78 |
Donnie Berkholz |
79 |
Developer, Gentoo Linux |
80 |
Blog: http://dberkholz.wordpress.com |