If you think that Linux can move to GitHub or GitLab and still be productive at scale, I want you to read through the MAINTAINERS file in the root of the Linux source tree.


Every one of those entries has a dedicated maintainer in charge of it, applying to a subset of the source tree. All 3,000 of them. Many of these have dedicated external trees, mailing lists, and policies. Almost all of this development happens away from the LKML. Each of those trees has a path upwards towards Linus's tree, often via other trees and other maintainers, or towards the -lts trees. These trees are not necessarily authoritative either, and the kernel you're running might be its own upstream maintained by your Linux distro, unique from any of the releases on kernel.org.

All of it is based on email. And it *works* to drive the most efficient and largest-scale open-source project in history.

You should study the Linux development model if you truly want to grasp the profound ways in which git is a *distributed* version control system.

Show thread

@sir is there somewhere you’d point someone to start their study of the Linux development model?

@chip read MAINTAINERS, find some subsystems which interest you, and read through their mailing lists. Read some LKML and whatever Linus & Greg & <insert your favorite maintainer> are doing.

Great, thanks for the info @sir!

Sign in to participate in the conversation

A Mastodon instance for developers of all shapes, disciplines and skill levels. By us, for us.