[...]
> I'm a professional developer in my "real" life, and quite comfortable with
> complex systems and concepts. However, kernel-level hacking brings me to
[...]
> I almost guarantee that 10% more effort put into documentation and
> commenting would reap great rewards in terms of contributed input from the
> community at large. Then, you CAN go off and design and implement the
> "latest and greatest" - AFTER having paved the way for others to maintain
> and fine-tune the previous "latest and greatest".
IMHO, it takes more effort to document the code than to write it. That's my
experience with kernel hacking (and I touched a lot of the Linux/m68k kernel
code). So your 10% rule is not correct (and as a professional developer,
shouldn't you know that documentation is the hardest part? :-)
And the `real' kernel hackers have so much to do, and so many new ideas, that
they'd rather do what they like most: i.e. turning ideas into new code...
Greetings,
Geert
-- Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be Wavelets, Linux/m68k on Amiga http://www.cs.kuleuven.ac.be/~geert/ Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium