You, too, can be a kernel hacker!

[zridling]

Glyn Moody points to a Linux Foundation/Linux Developer Network guide. "If you've ever wondered how the kernel development process works – and how you might join in – wonder no more, with this new guide to the kernel development process from the Linux Foundation."



The purpose of this document is to help developers (and their managers) work with the development community with a minimum of frustration. It is an attempt to document how this community works in a way which is accessible to those who are not intimately familiar with Linux kernel development (or, indeed, free software development in general). While there is some technical material here, this is very much a process-oriented discussion which does not require a deep knowledge of kernel programming to understand.
____________________________________________
Lots of fundamental coding advice throughout, no matter the platform.

[zridling]

Tom Espiner had a nice follow-up interview on this idea. Start small and work your way up.

Torvalds wrote that nobody should expect to start sending "big and complex" patches early, as it takes time for new contributors and established coders to learn how to interact effectively.

"The worst thing anybody can do is to study the kernel alone and try to learn things in private, and then, however many months later, present all the established kernel developers with a big patch that just comes out of the blue," wrote Torvalds. "That's just going to be frustrating for everybody."

Torvalds advised new contributors to "start small" by sending "trivial patches."

"It may not sound exciting but, quite frankly, I don't think anybody who starts out believing that they want to rewrite some big piece of the kernel should even bother. Reality isn't that simple."

[Edvard]

I'd probably start by grammar-checking the comments