Actually, I haven't written a paper. A paper is something which lays out
goals
architecture
milestones
design details
and should be sufficient to make the project happen should I be hit by a
bus. That's my main complaint with IRC, it requires me to keep coming
back and explaining the same thing over and over again.
Here's an idea: you go try and get some traction on the OS cluster idea.
I'll give you 6 months and we'll see what happens. If nothing has
happened, I'll produce a decent paper describing it and then we wait
another 6 months to see what happens. I'll bet you 10:1 odds I get a
lot more action from a lot more people than you do. Nope, wait, make
that 100:1 odds.
I've seen how little I manage to get done by talking. Talk is cheap.
I've also seen how much I get done when I write a paper which other
people can pass around, think about, discuss, and implement. A senior
guy at Morgan Stanley (hi marc) once told me "if you want to get things
done, write them down". And in my case, since people tend to like to
argue with me rather than listen to me (yup, it's my fault, my "style"
leaves "room for improvement" translation: sucks rocks), a paper is
far more effective. My style is pretty much removed from the equation.
I can just see me on IRC, all I'd be getting is style complaints while
people successfully avoid the real points. Look at the last 8 years
of LKML. I'd say most of the effect was from the LMbench paper and
maybe a few threads on performance which would have been more effective
if I'd written a detailed paper explaining my point of view.
----- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/