On November 4–5, the MySQL community gathered online for the third MySQL Contributor Summit of 2026. Across two days, contributors shared proposals, demonstrated progress, and discussed how to make MySQL easier to extend, operate, and contribute to. 

The summit marked another step in the community engagement plan announced in January. Progress since then includes new features integrated into Community Edition, expanded use of GitHub for public discussions and contribution workflows, and the introduction of the MySQL Governance Model and Steering Committee. Together, these efforts support the plan’s goals of accelerating innovation, growing the ecosystem, and making community participation easier and more transparent. 

The first MySQL Steering Committee meeting happened the week prior, on October 27. The meeting focused on progress to date of our published plans including MySQL Community Edition innovation and features, ecosystem unification and growth, and increasing transparency and community participation. We reviewed features delivered and planned in the community-driven roadmap, and the planned move toward GitHub-first development. We reviewed community metrics and messaging. Follow-up priorities include expanding review capacity, clarifying GitHub practices, improving roadmap status updates, and continuing metrics reporting and community outreach programs.  

Building on the May and August summits, the November event showed how ongoing community engagement is helping ideas develop into shared engineering work. Presentations brought together perspectives from Oracle, Google, AWS, Alibaba, Tencent, Booking.com, Percona, Intel, Readyset, the MariaDB Foundation, and others across the ecosystem. 

The discussions followed the four community roadmap categories: AI & Cloud, Developer / DBA Experience, Performance & Observability, and Extensibility / Ecosystem. For individual sessions, speakers, and proposal links, see the summit agenda. Recordings are also available on the MySQL YouTube Channel.  

From Proposals to Shared Development 

A recurring theme was the value of bringing ideas into public discussion early. Contributors presented work at different stages, from initial proposals and prototypes to implementation updates and delivered functionality. 

Returning topics demonstrated the continuity between summits. Vector indexing, health monitoring, and extension development had progressed since earlier discussions, giving participants an opportunity to review evolving designs and contribute additional requirements. 

The conversations also showed what contributors can bring beyond a new implementation. Participants offered production experience, existing code, test scenarios, design reviews, and operational feedback. During the change-data capture discussion, for example, AWS offered existing schema-metadata work for consideration. Other exchanges identified opportunities to test shared interfaces against different implementations. 

These contributions help teams build on experience across the ecosystem while identifying compatibility, correctness, and performance questions earlier in development. 

AI and Cloud: Connecting Capabilities to User Needs 

AI and vector discussions explored how MySQL can support emerging workloads through contributions from multiple organizations. 

Presentations covered vector indexing, similarity calculations, graph-based search, and invoking AI models through SQL. Together, they highlighted the importance of considering the complete developer experience—from preparing data and generating embeddings to selecting an index and running a search. 

A shared theme was flexibility. Different workloads have different requirements for memory, performance, scale, and accuracy. Contributors discussed interfaces that could accommodate multiple approaches as the field evolves. 

Participants also examined the operational implications of these capabilities, including credential management, network access, and the behavior of external model calls. Those questions helped connect proposed functionality to the expectations of people building and operating applications. 

Developer and DBA Experience: Learning from Real Deployments 

Contributions in the Developer / DBA Experience category drew directly from the challenges of operating MySQL at scale. 

Topics included query-plan management, replication availability, automation, maintenance, and read scaling. Across these proposals, contributors shared a common goal: reducing operational complexity while preserving predictable behavior. 

The discussions emphasized the importance of gathering requirements from the people who will use and integrate these capabilities. Database administrators, application developers, and operator maintainers bring different perspectives on how a feature should behave during upgrades, failures, or routine maintenance. 

Presenters invited that feedback as part of the design process. Questions about integration, lifecycle management, and failure handling helped clarify where additional collaboration would be valuable. 

Performance and Observability: Evidence, Correctness, and Review 

Performance and observability remained active areas of contribution, with presentations addressing monitoring, replication lag, crash recovery, contention, and consistent snapshots. 

A strong theme was the relationship between measurable improvement and careful validation. Contributors explained how they investigated bottlenecks, evaluated changes, and considered the conditions under which an optimization would help. 

Community questions examined ordering, rollback, recovery, memory use, and compatibility. These exchanges helped identify what supporting evidence and documentation would be needed as proposals move forward. 

Participants also discussed the contribution process itself, including access to performance testing and the challenges of evaluating regressions. Making those workflows clearer remains an important opportunity to support contributors and reviewers. 

The closing discussion highlighted AWS’s large-transaction binary-log optimization, BOLT, as an example of substantial collaboration between community contributors and MySQL engineers. 

Extensibility: Creating More Opportunities to Contribute 

Extensibility connected discussions across both days. Contributors explored how developers could build and distribute capabilities independently, including new data types, table functions, components, and storage engines. 

The broader goal was to make it easier for more people to innovate around MySQL. That requires useful interfaces, development tools, documentation, and ways for users to discover and install extensions. 

Several presentations approached related problems from different perspectives. Participants recognized opportunities to bring that work together while discussing security, version compatibility, packaging, and the responsibilities of catalog maintainers. The summit identified shared requirements and a clear need to continue the design conversation collectively. 

Making It Easier to Contribute and Participate 

Alongside the technical sessions, the summit explored how clearer processes, better tools, and community outreach can help more people participate in MySQL’s development. 

The team demonstrated work toward moving more of the integration process onto GitHub, building on existing automated checks, testing, and code-review workflows. At the time of the summit, the demonstrated merge automation was still being tested and prepared for rollout. Updated contributor guidance also aims to make proposals, design reviews, implementation, and testing easier to navigate. 

The closing community and governance discussion connected these improvements with broader opportunities to get involved. Updates covered governance, contributor participation, Planet MySQL’s Ecosystem Showcase, the Community Spotlight series, recognition programs, user groups, and education outreach. 

Together, these efforts support contributions across the ecosystem—from code, testing, and design reviews to tutorials, mentoring, and sharing operational experience. Community team members are available to help contributors navigate the process, while public discussions make it easier to connect with others working on related ideas. 

Thank you to everyone who shared their work, contributed feedback, and helped move these discussions forward. The collaboration continues on GitHub, where you can follow the proposals linked from the summit agenda, share your experience, and help shape what comes next for MySQL. 

We also invite you to nominate a MySQL Rockstar, someone whose contributions, knowledge sharing, or community support deserve recognition. This year’s Rockstars will be announced at MySQL Belgian Days. Please share your nominations with the MySQL Community team. 

Join us in Brussels for MySQL Belgian Days on January 28–29, 2027. Registration  is open, and the Call for Papers welcomes proposals through November 30. Continue the conversation at FOSDEM on January 30–31, including the M-Ecosystem devroom, where you can also submit a talk proposal. 

For more on the contributor summits and ways to get involved, explore these community resources: