Kernel space: Merging drivers early
,----[ Quote ]
| Kernel developers debate the standards for including new driver source code
| in the kernel. As long as a new driver doesn't break things for people who
| aren't using the affected hardware, getting it into the kernel in an
| unfinished state may do more good than harm.
`----
http://www.linuxworld.com/news/2008/030408-kernel.html?fsrc=rss-linux-news
Good essay here about open source not hiding flaw behind some binaries and PR
department:
Are Open-Source Developers Too Critical?
,----[ Quote ]
| That is, when you pay someone else to supply a box of shrink-wrapped
| software, you're emotionally distant from it. You may rant about its
| inadequacies, but you're essentially powerless to change them, and you have
| no expectation that your personal opinion will affect the product's
| evolution.
|
| With open-source software, on the other hand, a developer who sees a missing
| feature or an unfixed bug has her own skin in the game—or is connected to
| those who do. There's a sense of personal responsibility.
`----
http://advice.cio.com/esther_schindler/critical_os
"One person in Helsinki can quickly write the core of a sophisticated operating
system."
--John Warden, lead attorney at Microsoft
Related:
[Linux kernel 2.6.24 released]
,----[ Quote ]
| The release is out there (both git trees and as tarballs/patches), and for
| the next week many kernel developers will be at (or flying into/out of)
| LCA in Melbourne, so let's hope it's a good one.
|
| Nothing earth-shattering happened since -rc8, although the new set of ACPI
| blacklist entries and some network driver updates makes the diffstat show
| that there was more than the random sprinkling of one-liners all over the
| tree.
`----
http://lkml.org/lkml/2008/1/24/407
|
|
