Sponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
ELC: Morton and Saxena on working with the kernel communityELC: Morton and Saxena on working with the kernel communityPosted Apr 24, 2008 23:31 UTC (Thu) by aegl (subscriber, #37581)In reply to: ELC: Morton and Saxena on working with the kernel community by Frej Parent article: ELC: Morton and Saxena on working with the kernel community I think that Andrew's comments about a democracy that doesn't vote relates to the high rate of abstentions when a patch is posted. Everyone CAN vote by posting a reply to any patch submission with either a YES ("Acked-by:") or a NO (reason for not merging). But hardly anybody does. There are currently 4816 subscribers to the linux-kernel mailing list. Most "votes" are carried with 2 YES (proposer of the patch and 1 Ack) and 4814 abstentions. This is a good thing. A well thought out and obviously correct patch should get merged with minimal discussion. If everybody did start voting, the mailing list would grind to a halt (If every one of the 12,000+ commits that got us from 2.6.24 to 2.6.25 was discussed by all 4816 readers of LKML, then vger.kernel.org would melt under the load).
(Log in to post comments)
Linux kernel: democracy that doesn't vote Posted Apr 25, 2008 3:25 UTC (Fri) by giraffedata (subscriber, #1954) [Link] Are you claiming that every LKML subscriber has equal weight? I've never seen any rules for how the decision to merge works, but I'm pretty sure there's nobody counting up votes on the mailing list and accepting a patch if there are more yesses than noes.
Linux kernel: democracy that doesn't vote Posted Apr 25, 2008 4:14 UTC (Fri) by aegl (subscriber, #37581) [Link] No ... every vote doesn't have equal weight. People who have demonstrated expertise in a particular area will generally have far more influence on a merge decision than people without a track record, who in turn may have more weight than people who have publically demonstrated their lack of knowledge.But even Linus gets "outvoted" from time to time (he just merged kgdb even though he really doesn't like the idea of kernel debuggers). So the process is rather vague, and sometimes surprising ... but there is a general philosophy behind it. Maybe a merge decision can be summed up by answering the question: "Will this patch make the kernel better?" ... but this is still poorly specified unless you have the same opinion about what "better" means in the context of Linus' (and many of the other maintainers and key developers) goals. Some of the people who find it "hard to understand" the process are under the mistaken impression that the goal is commercial success. It isn't. The goal is to be the best kernel for its users. Commercial success might follow as a result of being good. But if you ask Linus how much he cares about the "market segment share" that Linux has, I bet his answer will be something like "not at all".
Linux kernel: democracy that doesn't vote Posted Apr 25, 2008 15:46 UTC (Fri) by giraffedata (subscriber, #1954) [Link] OK, that's not voting. Voting is a mathematical process; there are lots of other words for that: consensus, giving opinion, giving advice, etc.If merely stating your position on LKML could be called voting, then citizens that go before a city council meeting to argue against a new zoning ordinance would be said to be voting on the ordinance. Voting is the simplest way to implement democracy, and I think many people assume it's the only way, which is why Andrew feels the need to call it "democracy that doesn't vote."
|
|||||||||||