Kernel Developers Summit

Kernel Developers Summit
Name	Kernel Developers Summit
Genre	Technical conference
Frequency	Annual (historically)
Location	Varies (primarily Ottawa, San Diego, Dresden)
First	2001
Participants	Kernel developers, maintainers, vendors, academics

Kernel Developers Summit

The Kernel Developers Summit is a recurring developers' meeting that gathered core Linux kernel contributors, subsystem maintainers, company engineers from Intel Corporation, IBM, Red Hat, and representatives from projects such as GNU Project and X.Org Foundation to discuss kernel development, release management, and technical coordination. Initiated in the early 2000s alongside events like the Linux Plumbers Conference and the Linux Kernel Summit, the Summit provided a venue for maintainers including those associated with Linus Torvalds, Andrew Morton, Greg Kroah-Hartman, and companies such as Google and Microsoft to negotiate interface changes, stable APIs, and merge-window policies. The meeting often took place adjacent to larger gatherings such as LinuxCon and the Open Source Summit, enabling cross-pollination with contributors from Canonical Ltd., SUSE, and academic partners from institutions like Massachusetts Institute of Technology and University of Cambridge.

History

The event originated after discussions at early Linux Kernel Summit meetings and community summits involving figures from O'Reilly Media and organizers of LinuxCon; it first assembled maintainers drawn from the Linux Foundation and corporate engineering groups including Novell and Oracle Corporation. Early editions saw participation from developers tied to major subsystems such as ext3, Xen Project, KVM, IPv6, and udev; these meetings influenced decisions later formalized in mailing lists like linux-kernel and collaborative platforms used by contributors from Red Hat and Intel Corporation. Over time, the Summit adapted to changes in the ecosystem, interacting with emergent efforts such as the Open Source Initiative and standards bodies including IEEE. The history includes shifts in location from North America to Europe, with editions held near events like DebConf and Kernel Recipes.

Purpose and Format

The Summit's purpose was to provide a focused, invitation-driven forum where lead developers and stakeholders from vendor organizations and projects such as Fedora Project, Debian, Gentoo could meet face-to-face to resolve contentious issues such as merge-window timing, stable tree policy, and scheduler design. Formats typically included roundtable discussions, short position talks by maintainers like those responsible for scheduler and memory management subsystems, and ad hoc working groups that produced actionable proposals for the linux-kernel mailing list. Sessions bridged interests from companies such as Amazon Web Services and research labs at Lawrence Berkeley National Laboratory to coordinate on topics like power management (involving ACPI) and filesystems (involving Btrfs and ext4). The Summit served as a practical complement to broader conferences such as FOSDEM and SC Conference.

Organization and Governance

Organization was informal but stewarded by community figures and companies with vested interests, with logistical support sometimes provided by the Linux Foundation or conference hosts like The Linux Foundation events staff and local organizers from universities and corporations. Participation was curated by invite lists drawn from maintainers of key subsystems—examples include maintainers for networking stack, block layer, device drivers, and virtualization subsystems like KVM—and representatives from vendors such as Broadcom, Qualcomm, and NVIDIA. Decisions on agenda and chairing were typically made by conveners with reputations similar to those of Greg Kroah-Hartman or Linus Torvalds in the broader community; minutes and follow-ups were often published on collaborative channels used by projects such as Kernel Newbies.

Notable Events and Decisions

Notable outcomes linked to the Summit include coordinated approaches to stable release management echoed in policies advocated by maintainers associated with stable kernel efforts, discussions that shaped features like preemption models and contributions to scheduler improvements championed by developers from Red Hat and academic collaborators at University of California, Berkeley. The meeting also hosted negotiations over contentious interfaces such as those around io_uring and introduced cross-vendor agreements on device driver submission practices involving companies like Intel Corporation, AMD, and Samsung. At various editions, participants debated security models influenced by proposals from projects including SELinux and AppArmor, and coordinated responses to vulnerabilities similar in profile to those tracked by organizations such as CERT.

Participation and Attendance

Attendance typically comprised 30–100 invited attendees drawn from leading contributors to subsystems such as file systems, networking, virtualization, and security and from corporations including Amazon, Google, Microsoft, IBM, and distributions like Ubuntu. Participants included lead maintainers, kernel developers, technical managers, and academic researchers from institutions such as Stanford University and ETH Zurich, as well as engineers from vendors like Marvell Technology and Arm Holdings. The curated nature of the Summit encouraged focused dialogue, enabling attendees from projects including systemd and Wayland to coordinate kernel-facing integration points.

Relationship with Linux Kernel Summit and Conferences

The Summit operated alongside events such as the Linux Kernel Summit, Linux Plumbers Conference, LinuxCon, and community gatherings like FOSDEM, often sharing dates or venues to facilitate cross-attendance by contributors from projects such as X.Org Foundation, Mesa 3D, and Wayland Project. While the Linux Kernel Summit emphasized broader policy and plenary sessions, the Summit maintained a narrower, technical remit similar to working groups at the Linux Plumbers Conference and collaborated with distribution-focused events like DebConf to surface integration issues.

Impact on Kernel Development and Community

The Summit's impact included accelerating consensus on technical disputes, improving coordination among vendors such as Intel Corporation, AMD, and NVIDIA and open-source projects like GNU Project and KDE, and influencing upstream practices regarding stable releases and maintainer responsibilities echoed in workflows used by projects like Git and infrastructures like GitLab and Gerrit. By enabling face-to-face negotiation among maintainers tied to major subsystems and employers including Red Hat and Google, the Summit contributed to pragmatic solutions that reduced fragmentation and informed roadmaps affecting deployments at cloud providers like AWS and enterprise environments managed by Oracle Corporation.

Category:Computer conferences