BazelCon Keynote

This keynote marks Bazel's transition from Google-led to community-led governance through the Linux Foundation, tracing the build system's evolution from approximately 2014 through 2024. The speakers highlight two major milestones: Bazel 1.0 (roughly five years after initial development), which introduced formal semantic versioning and long-term support for major versions enabling enterprise adoption, and Bazel 8's upcoming release completing the governance architecture transformation.

The presentation emphasizes the thriving, diverse contributor ecosystem. While Google contributions to Bazel's core are substantial, external contributions vastly outnumber them when viewed through the broader Bazel registry. The Bazel build GitHub organization attracted 625 contributors in the past 12 months alone, with the newly established Bazel contrib GitHub organization (under Linux Foundation stewardship) hosting community-owned projects. A concrete example illustrates the ecosystem's health: after a recent Bazel release, the Google team was debugging an issue when a community pull request arrived that solved the problem unprompted.

The keynote articulates mutual benefits of open governance. Google gains access to community-contributed fixes and features, smoother integration between open-source projects and its internal monorepo (Google 3/Blaze), and serves as a thought leader in build configuration management, creating a talent pool and reciprocal relationships. The organization of this BazelCon itself exemplifies the shift—the first conference not run by Google, organized through the Linux Foundation with three community leaders on stage: Alex Eagle (co-founder and CEO of Aspect Build Systems), Helen Alcher (co-founder and CEO of Enlow), and Chuck Grindle (senior software engineer at Revalue Technology).

BazelCon's own evolution reflects growing community involvement. The 2017 conference drew 200 attendees; by 2019, 300 attended. The 2023 Munich event had 200+ on the waitlist, prompting expanded venues and formalized community participation in program selection and office hours. The technical steering committee, meeting weekly for several years, now governs projects in Bazel contrib with neutral stewardship.

Google has donated repositories from Bazel build to Bazel contrib GitHub—technically community-maintained already, but the formal transfer under neutral governance removes the perception of Google backing and potentially unlocks additional organizational contributions. Looking forward, organizers propose a directed fund under the Linux Foundation allowing member companies to staff and fund community projects; approximately five founding member companies are needed. Potential funding areas include the module registry, IDE integrations, technical writing (currently lacking dedicated staffing), and Windows feature parity with Mac and Linux.

The next BazelCon is planned for New York City. Q&A discussion clarifies that large architectural changes to Bazel's core require prior discussion with the core team, which remains under Google stewardship. External developers can contribute through pull requests on GitHub, though external commit access is not planned. The technical steering committee serves as the mechanism for community involvement in ecosystem-level architectural decisions.