Joining The Linux Kernel Community: For Dummies

Summary

This video discusses the role of companies like Meta in contributing to open-source projects, particularly the Linux kernel. It highlights insights from Paul McKenney, a kernel developer, about joining the Linux community and its decentralized, merit-based structure. The Linux kernel community values good code over titles or experience, and each subsystem is maintained with varying levels of leniency. The video emphasizes the importance of doing one's homework, understanding Git, and contributing good-quality code, as well as building trust with maintainers to get patches accepted.

Takeaways

• 🔧 Meta is one of the significant contributors to open-source software, including the Linux kernel, through developers like Paul McKenney.
• 👨‍💻 The Linux kernel community operates without a strict hierarchy, where developers are free to contribute but aren't explicitly told what to work on.
• 💼 Linus Torvalds, while a central figure, mostly limits his role to reviewing and rejecting patches rather than managing people or tasks.
• 🚫 The Linux kernel community does not prioritize educating aspiring contributors, meaning new developers need substantial experience, particularly in C and Git.
• 🔄 Trust and competence are key in the Linux community; the quality of your work, not your background or experience, determines your success.
• 📜 Subsystem maintainers have full responsibility for their sections, which can lead to variability in how code reviews and contributions are handled.
• 🔍 Developers must do thorough homework before submitting patches, including following formatting guides and understanding the project goals.
• 🤔 Contributors should avoid assuming that rejection of their work is a misunderstanding—maintainers may have valid reasons based on their broader expertise.
• 📚 To get involved, developers should leverage related experience, attend conferences, read mailing lists, and ensure they understand what’s being worked on.
• 👥 Contributions are judged solely on merit, and becoming a valuable community member involves producing high-quality, reliable code that solves problems.

Q & A

Who is Paul McKenney, and what role has he played in Linux kernel development?

Paul McKenney is a Linux kernel developer who previously worked at IBM and later moved to Meta. He has been involved in Linux kernel development for over 20 years, contributing significantly to various projects.

What is the structure of the Linux kernel community?

The Linux kernel community is not a strict hierarchy. While there are respected maintainers like Linus Torvalds and Greg Kroah-Hartman, they do not manage the community in a top-down manner. Instead, it's a loosely organized group where maintainers are responsible for their subsystems.

How does Linus Torvalds interact with kernel contributions?

Linus Torvalds usually limits himself to reviewing and rejecting submissions rather than asking people to contribute or assigning tasks. He relies on subsystem maintainers to handle most of the work and rarely tells people what to do directly.

What should aspiring contributors know about the Linux kernel community's approach to education and mentorship?

The Linux kernel community does not prioritize educating aspiring contributors. While individual developers may offer guidance, contributors are expected to be experienced developers with strong knowledge of C, Git, and open-source practices before getting involved.

What is the role of a subsystem maintainer in the Linux kernel community?

A subsystem maintainer is responsible for overseeing code contributions within their subsystem. They are accountable for quality control and must ensure that the code they merge meets the standards before it's passed on to Linus Torvalds for final integration.

How should contributors approach submitting patches to the Linux kernel?

Contributors should do their homework by reading mailing lists, watching conferences, and understanding the current work being done. They should follow the submission guidelines closely and be prepared to justify any deviations from the formatting or coding standards.

How does the Linux kernel community handle new technologies, such as Rust, being proposed for inclusion?

When Rust was first proposed for Linux kernel development, it faced significant resistance, including criticism from Linus Torvalds. However, after improvements were made, Rust was eventually merged into the kernel. This demonstrates that new technologies must reach a certain level of quality before being accepted.

What should developers assume when contributing to the Linux kernel?

Developers should assume that getting involved in the Linux kernel will be difficult. They should not expect their skills to be appreciated or that the community will invest time in their education. They must earn trust by providing high-quality code and demonstrating competence.

How does the Linux kernel community assess contributions based on the contributor’s background?

The Linux kernel community does not give priority to contributors based on their background or experience. Whether you're a senior software engineer or a junior developer, the quality of your contribution is what matters. Good work will be recognized, while bad work will be rejected.

What advice is given to developers to improve their chances of success in the Linux kernel community?

To succeed, developers should leverage any related experience, stay informed about ongoing projects, follow the submission guidelines, and be valuable members of the community. They should also assume maintainers understand the project better than they do and approach rejections with an open mind.