Keynote: The Maintainer's Paradox
summary
Argument: open projects gain value from diversity but maintainers get overwhelmed by incoming patches. Uses the Fuego test framework as a real example, notes a self-imposed 24-hour response goal that proves unrealistic, and frames contributions as "puppies" that require indefinite care. Recommends concrete fixes: call out snark, form maintainer groups, use Andrew Morton as an ombudsman for stray patches, triage and documentation work to reduce load, and recruit new maintainers rather than only proposing risky kernel changes.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:03Light bulb metaphor
- 2:31Becoming a maintainer
- 3:02The Maintainer Paradox
- 4:40Patch contributions
- 5:26Social element
- 6:08Negative behaviors
- 7:36Tips
- 12:30Last plea
related talks
47mTrying to Explain the 'Incomprehensible' Decision Making Process of a Subsystem Maintainer
41mChallenges Around Long-Term Kernel Maintenance
40mKeynote: Kernel Developer Roundtable
49mCode Review Training for Kernel Patch Reviewers
25mLinux: Where Are We Going
26mGetting Started With Kernel Programming: The Linux Kernel Mentorship Program
32mKeynote: Dirk Hohndel in conversation with Linux Creator Linus Torvalds
08mKeynote: Kevin Hilman in conversation with Greg Kroah-Hartman
