___Kerneltraffic and LWN have vastly different writing styles. I actually preferred KT over
LWN.
___KT picked up the interesting threads on LKML, and made an interesting read solely based on
developer's citations, mostly direct speech. It was an art of taking snippets from everywhere,
and pasting it together again in a coherent fashion. This gave it a feel like you were
listening to a parliament discussion -- judgement: "raw material".
The last KT#335 issue covered 14 threads.
___LWN on the other hand uses the usual "newspaper" style. (This week: mem_notify and the blk
rq api.) The Editor makes himself familiar with the topic and then writes down his findings
from his viewpoint. Standard (e.g. "cups slow on linux-2.6.24") and philosophical
(hypothethical "libata does not power up my usb coffee pad, who broke it?") matters don't get
much attention, while really technical things are explained in a way so that people who are
not a master of the particular subsystem still get to understand what it's about -- judgement:
"pre-chewed".
___Sometimes, there are only two [longer] stories, sometimes there are four stories in the
Kernel section of the Weekly Edition (e.g. 2006-01-17) - it kinda fluctuates. (Probably
related to LKML I guess, everyone's busy with merging for 2.6.25 right now.)
___I dunno if LWN has the necessary manpower for it, but getting to read something KT-style
would be great. Does not need to be a dozen of threads, but maybe two, three threads that did
not make it into a "newspaper" article. Spot on: the ext3 feature freeze, er, ext3 freeze
feature thread, softpanic v2, and perhaps the ext4 list could have been showcased KT-style for
this week.
Ten-year timeline part 4: the end and the beginning
Posted Feb 1, 2008 2:38 UTC (Fri) by jengelh (subscriber, #33263)
[Link]
s/this week/week of 2008-01-24/
s/2006-01-17/2008-01-17/
And pre-chewed was meant to be positive. There are a few areas in the kernel I do not want to
tamper with, so reading about it in this form is welcome