Oracle Promises to Open MySQL Governance, but Community Demands Binding Guarantees

What happened?

Oracle has promised a new era in its stewardship of MySQL, the popular open source database management system whose intellectual property rights it owns. According to an official announcement on June 3, 2026, the company will establish a new governance model, a technical steering committee, and greater community support. However, the co-founders of the OurSQL Foundation — an independent organization representing users and developers — point out that these promises lack binding force and could be reversed by future Oracle directives. This move comes after the creation of the OurSQL Foundation in May 2026, which arose in response to community fears about MySQL's future under Oracle's exclusive control.

Why is it important?

MySQL is one of the most widely used databases in the world, with a massive installed base in companies of all sizes. According to DB-Engines data, MySQL is the second most popular database management system after Oracle Database, with a market share of over 25% in the relational database segment. The lack of transparency and community control has generated distrust, especially after the mass layoffs in the MySQL core team in September 2025, which reportedly reduced the development team to less than half. Oracle's move aims to appease criticism, but the community demands legal guarantees to ensure the project's long-term independence, similar to what happened with the founding of MariaDB in 2009 after the acquisition of Sun Microsystems.

Details of the announcement

In a blog post dated June 3, 2026, Oracle claimed to be taking "the next step" in transparency and collaboration. Among the measures highlighted:

• A new governance model allowing community members to contribute code, tests, documentation, and technical reviews.
• The role of "committers" for experienced reviewers, who will help maintain code quality.
• A technical steering committee with initial representation from AWS, Google Cloud, and Oracle, plus as-yet-unnamed users. Microsoft, provider of Azure Database for MySQL, is notably absent, which analysts say reflects commercial tensions between Oracle and Microsoft in the cloud market.
• Greater engagement through public roadmaps, contributor summits, GitHub collaboration, and early access to releases.

Jason Wilcox, senior vice president of Oracle Cloud Infrastructure, stated: "Stronger governance gives the MySQL community clearer ways to participate and accelerate innovation, while preserving the quality, security, and compatibility that users expect." However, the announcement does not specify how community members will be chosen or what real decision-making power they will have.

Community reaction

Peter Zaitsev, co-founder of Percona and part of the OurSQL Foundation, called the announcement "a step in the right direction" but warned that the promises are only advisory. "There is nothing binding," he said in a statement to The Register. "If the community wants changes that Oracle considers detrimental to its interests, the current management could undo what was agreed." The litmus test will come when disagreements arise between the community and Oracle. Zaitsev compared the situation to the PostgreSQL model, where the community has real control over development, and noted that "this is better than nothing, but it's not the kind of PostgreSQL-style community commitment where the community can truly chart the path forward for users."

Michael "Monty" Widenius, creator of MySQL and co-founder of MariaDB, also spoke out via his blog, calling the announcement "cosmetic" and recalling that Oracle had made similar promises in 2010 after the Sun acquisition that never materialized. The OurSQL Foundation, created in May 2026, aims precisely to force real change, but so far Oracle has not ceded on intellectual property or governance structure.

Context and background

MySQL was created by Michael "Monty" Widenius in the 1990s and became the world's most popular open source database, especially in web applications. Oracle acquired MySQL when it bought Sun Microsystems in 2010 for $7.4 billion. Since then, the community has feared that Oracle would neglect open source development in favor of its own commercial product, Oracle Database. These fears were confirmed in September 2025, when Oracle laid off much of the MySQL core team, including key developers. Widenius called those layoffs "heartbreaking" and warned they could "kill" MySQL. In response, the community mobilized and created the OurSQL Foundation in May 2026, aiming to push for independent governance. Oracle's June 2026 announcement is seen as a direct reaction to this pressure.

Historically, similar situations have led to successful forks. In 2009, after Oracle's acquisition of Sun, Widenius created MariaDB, a fork of MySQL that has gained significant market share, especially in Linux environments. MariaDB has its own foundation and a community governance model. Another example is LibreOffice, which emerged as a fork of OpenOffice after Oracle acquired Sun and showed little interest in community development. These precedents suggest that if Oracle does not offer binding guarantees, the fragmentation of MySQL could accelerate.

What consequences will it have?

If Oracle does not offer binding guarantees, the fragmentation of MySQL could accelerate. Projects like MariaDB (a fork led by Widenius) could gain followers, especially among companies that value vendor independence. Additionally, Microsoft's absence from the committee suggests commercial tensions; Microsoft is a major player in the MySQL ecosystem through Azure Database for MySQL, and its exclusion could be interpreted as an attempt by Oracle to sideline a cloud competitor. For users, uncertainty about MySQL's direction may delay adoption or migration decisions. According to a 2025 Percona survey, 40% of MySQL users were considering migrating to alternatives like PostgreSQL or MariaDB due to concerns about Oracle's control. If promises are not fulfilled, that figure could rise.

In the market, the impact could be significant. MySQL is the default database in many web applications (WordPress, Drupal, etc.) and shared hosting environments. Fragmentation could lead to compatibility issues and increase migration costs for businesses. On the other hand, PostgreSQL, which has already gained popularity in recent years (according to Stack Overflow, it was the most loved database by developers in 2025), could directly benefit from MySQL's uncertainty.

What should readers know?

• Oracle's promises are not legally binding; the community demands a formal commitment, possibly through an independent foundation similar to MariaDB or PostgreSQL.
• MySQL remains Oracle's intellectual property, limiting community control; any governance changes can be unilaterally reversed.
• The creation of the OurSQL Foundation is a counterbalance seeking greater independence, but its real power will depend on the pressure it can exert on Oracle.
• Alternatives like MariaDB or PostgreSQL offer more community-driven governance models and could be safer long-term options for those prioritizing vendor independence.
• Oracle's announcement is a step forward, but insufficient to guarantee MySQL's future as a truly community-governed open source project.