Gentoo Archives: gentoo-dev

From: Daniel Barkalow <barkalow@××××××××.org>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] gentoo-dev vs lkml?
Date: Fri, 16 Mar 2007 06:02:45
Message-Id: Pine.LNX.4.64.0703160014130.6485@iabervon.org
In Reply to: [gentoo-dev] gentoo-dev vs lkml? by Grant Goodyear
1 On Wed, 14 Mar 2007, Grant Goodyear wrote:
2
3 > Underlying the draft code of conduct is an assumption that aggressive
4 > and less-than-nice behavior on gentoo-dev is seriously harming Gentoo.
5 > On the other hand, LKML is famous for its flamewars, and nobody claims
6 > that Linux is in serious trouble. Does anybody have a good feeling for
7 > where the difference lies? Are we sure that we're solving the right
8 > problem? (That's not a rhetorical question; I really don't know the
9 > answer.)
10
11 One thing that matters a lot is that development mostly goes through the
12 list, or is at least reported on it. Even if there's a huge flamewar going
13 on, the infiniband patch dump is still more messages. Sure, most people
14 don't actually read the infiniband patch sets, but there's this constant
15 sense that work is getting done.
16
17 Tied into that is the sense that you can win flamewars by posting code
18 that's just so good that people can't help but accept it. Or benchmarks
19 showing that your version is significantly faster on important things. Or
20 that you can eliminate a common class of bugs. Or that you can make a lot
21 of code simpler. But, in any case, that flamewars are ultimately decided
22 on the technical merit of the code, as judged sort of objectively by
23 people widely accepted to have good taste.
24
25 Conversely, if somebody's getting work done and posting the results, and
26 lots of people are flaming that person, it ultimately doesn't matter, if
27 nobody else produces an alternative. If nobody can say how the code should
28 be instead of how it's been written, it eventually wins. And people are
29 therefore forced to be productive instead of just flaming.
30
31 With all the development, it's so high traffic that someone being really
32 annoying can be ignored with no more difficulty than the piles of messages
33 that just aren't interesting to a particular subscriber. People fight
34 about the issues as long as the conversation stays on the issues, but
35 personal attacks are generally mostly ignored, because they're low-value
36 in how flamewars are scored.
37
38 People are willing to be at odds on one issue while working together on
39 another issue. Adrian Bunk is maintaining 2.6.16.x, and there have been
40 ongoing flamewars over his patch acceptance policy for that series; at the
41 same time, he maintains the list of regressions in the latest development
42 kernel, and the same people are really grateful for his work in following
43 up on bug reports and getting the right issues to the right people's
44 attention.
45
46 It comes down to this: everybody sees what you post. If you post mostly
47 useful stuff, you're taken seriously. If you post mostly flames, you're
48 not. If you're taken seriously, your critiques of other people's code
49 matter more. If you want to be taken really seriously, you have to make
50 constructive comments on other people's code. If your comments are
51 sufficiently technically correct, you can flame people and not be ignored.
52
53 -Daniel
54 *This .sig left intentionally blank*
55 --
56 gentoo-dev@g.o mailing list