1 |
Jason Stubbs wrote: |
2 |
> 1) There is a fairly clear chain of command. |
3 |
|
4 |
I've seen a few people make this kind of comment recently, and I'm never |
5 |
sure whether they mean it as it sounds or not. |
6 |
|
7 |
There isn't really a chain of command, since there isn't really anything |
8 |
being commanded. There is no developer community membership like we |
9 |
have, there are no policies set out, etc. There is no silencing of |
10 |
people, or controlling of others actions, or forced unsubscriptions |
11 |
(apart from for problems with the email system). |
12 |
|
13 |
What I think people mean to say is that for the major subsystems, there |
14 |
is a fairly clear structure to the technical contribution flow and the |
15 |
review process. But there is also a huge amount of code which is not |
16 |
'maintained' in this way, where the only realistic patch-target is |
17 |
Andrew Morton, the lead maintainer of the whole kernel. |
18 |
|
19 |
But in my opinion this structure doesn't really relate to the flaming. |
20 |
|
21 |
> 2) Each technical area usually has a clear authority - ie. a spokesman whom is |
22 |
> listened to and usually has one's posts challenged with clear respect. |
23 |
|
24 |
I don't really understand how this relates to the question why linux |
25 |
kernel flamewars don't appear to harm the kernel community in the way |
26 |
that gentoo-dev flamewars appear to harm the Gentoo community. |
27 |
|
28 |
|
29 |
Here are my thoughts, and I think there are several answers here: |
30 |
|
31 |
Firstly, in some ways, flaming there does harm the kernel community in |
32 |
the way that flame wars harm Gentoo. For example, the media frequently |
33 |
misinterpret those discussions and misreport on them. Users with little |
34 |
or no technical background suddenly decide they are qualified to make |
35 |
judgement on technical decisions and blog about stuff, write angry |
36 |
emails to LKML or the developers directly, etc. One example that springs |
37 |
to mind was from one of the udev/devfs wars, and Rusty Russell's amusing |
38 |
response which really highlights the way that some people make judgement |
39 |
without having justifiable involvement. |
40 |
http://lkml.org/lkml/2003/12/23/307 |
41 |
|
42 |
Another answer: the flamewars don't matter because a lot of the time, |
43 |
the people involved do not really fit into the community anyway. For |
44 |
example, Hans Reiser and reiser4. The development community is heavily |
45 |
built around technical excellence, but Hans repeatedly argued that |
46 |
despite breaking half the rules in the book, his code should be included |
47 |
REGARDLESS since it's obviously absolutely necessary in order to take |
48 |
Linux to the next level. Hans also managed to start some heated |
49 |
discussions by aggressively responding to mails which were purely fair |
50 |
technical review of reiser4. It took a long long time for reiser4 to |
51 |
reach anywhere near mainline and it's still a fair distance away. |
52 |
|
53 |
I also feel that the community is more mature, in that people truly with |
54 |
a grasp on the community generally do not get involved with the heated |
55 |
discussions when they go beyond the point of technical review. By this I |
56 |
mean simply: people don't have the apparent urge to respond to mails in |
57 |
the way that people do here -- kernel developers don't seem to take bait |
58 |
from trolls. |
59 |
|
60 |
In general threads also seem to stay on topic more than they do here as |
61 |
well. Steve Long's initial reply to the thread here didn't add anything |
62 |
to the discussion Grant was trying to start, and he even admitted so! |
63 |
I'd say on the LKML replies like this generally don't happen, or if they |
64 |
do, they get 0 responses. |
65 |
|
66 |
Another factor: think about the level of ratio of developers to users on |
67 |
both lists. Even if most posts here are by developers, there are a |
68 |
comparatively large number of non-developer readers, plus the |
69 |
discussions make good reading material linked from the GWN and forums etc. |
70 |
|
71 |
Now look at the LKML. It's often hard to find general discussion behind |
72 |
the truckloads of patches and river of technical review emails. A large |
73 |
proportion of the content is not "understandable" unless you have a good |
74 |
knowledge of C, operating systems, and the technical area in question. |
75 |
This isn't a place that users hang out, users dont really read it |
76 |
either, and you need to be a decent developer to get involved in the |
77 |
first place. |
78 |
|
79 |
Daniel |
80 |
-- |
81 |
gentoo-dev@g.o mailing list |