From: Andrew Morton <akpm@linux-foundation.org>
Date: Wed, 21 May 2008 12:31:27 -0700

quoted text
> The #1 project for all kernel beginners should surely be "make sure
> that the kernel runs perfectly at all times on all machines which you
> can lay your hands on".  Usually the way to do this is to work with
> others on getting things fixed up (this can require persistence!) but
> that's fine - it's a part of kernel development.

Indeed.  A lot of the time I see new people, or people making
suggestions to them, so fixated on wanting to implement new features.

To me that is absolutely the wrong way to go about this.

It's so much more useful, for both the community and the individual,
to fix bugs.  Fixing a bug forces you to learn how the kernel works at
least on some level, and fixing a bug always makes Linux better.

Implementing a new feature does not necessarily have either of those
two important qualities, so it is never the place for new people to
start.

Fixing bugs will give someone a real identity and place in the
community.

You want real Linux kernel "street cred"?  Fix a lot of bugs, then you
can implement a thousand new features and people will take you
seriously because you've shown that you can and will fix things.
--
unsubscribe notice
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/