Oracle's New MySQL Governance Model
Oracle announced a new governance model for MySQL on June 26, 2026 — a technical steering committee, a committer program for experienced contributors, and a whole lot of language about "accelerating innovation" and growing the MySQL ecosystem. Jason Wilcox, senior vice president of Data and AI Platform Services at Oracle Cloud Infrastructure, put it this way: "Stronger governance gives the MySQL community clearer ways to participate and accelerate innovation while preserving the quality, security, and compatibility users expect."
Translation: Oracle is letting community members review code changes, contribute to documentation, and sit on a committee that offers strategic guidance. The steering committee's initial membership reads like a who's-who of cloud providers — AWS, Google Cloud, and Oracle itself. Microsoft, which runs Azure Database for MySQL as a competing managed service, is conspicuously absent.
It's the kind of announcement that looks good on a blog post. The question, as always with corporate open-source promises, is whether it actually means anything when the rubber meets the road.
The Pressure That Forced Oracle's Hand
This didn't come from a place of generous self-reflection. The OurSQL Foundation formed in May 2026 — an independent organization claiming to represent MySQL users and developers, co-founded by Percona's Peter Zaitsev. It was a direct response to mounting community frustration over Oracle's stewardship of the database it acquired back in 2010.
The breaking point came in September 2025, when Oracle made "widespread layoffs" across its core MySQL development team. Michael "Monty" Widenius, who co-authored the original MySQL in the 1990s, said the job cuts left him "heartbroken, but not surprised." That's Monty speaking — a man who watched his creation get swallowed by a corporation that has never been shy about its priorities.
The OurSQL Foundation's creation was the community saying: if Oracle won't open up on its own, we'll organize anyway. And that's what prompted this week's announcement. Oracle didn't want a lobby group with teeth — it wanted to co-opt the conversation before it got louder.
Who Gets a Seat at the Table
The steering committee's initial membership tells you everything about Oracle's calculus. AWS, Google Cloud, and Oracle. Three cloud providers who all run MySQL-compatible managed services and benefit from keeping the open-source project alive as a reference implementation.
Microsoft's absence is deliberate. Azure Database for MySQL competes directly with AWS RDS for MySQL and Google Cloud SQL for MySQL. Having Microsoft on the steering committee would mean giving a direct competitor influence over the project's direction — including decisions about features, compatibility, and roadmap priorities. Oracle isn't stupid enough to invite that.
The committee will also include "as-yet-unnamed users of MySQL" — which is corporate speak for: we'll add more people when we figure out who's safe to bring in. The committer program, meanwhile, opens the door for individual contributors who've proven themselves through sustained code contributions. It's a meaningful mechanism, but it's also entirely within Oracle's control who gets promoted to committer status and who doesn't.
Advisory, Not Binding — The Core Problem
Peter Zaitsev welcomed Oracle's new tone. "This is a step and in the right direction," he said. "We welcome Oracle engaging the MySQL ecosystem as a whole." He acknowledged that for the last nine months, Oracle had shown "a desire to show more openness to the community in terms of sharing and including the wider community in the decision-making process."
Then he got to the part that matters.
"If you read all those announcements they say, 'we will involve the community in an advisory capacity,' which is of course better than nothing, but it's not really PostgreSQL-type community engagement, where community is really able to plot a path forward for users," Zaitsev said.
The distinction between advisory and binding is everything. Advisory means Oracle listens. Binding means Oracle has to follow through. Right now, the steering committee advises and Oracle decides. The committer program reviews code but doesn't merge it without Oracle's approval.
Zaitsev put it bluntly: "There's nothing binding in this regard." A new Oracle management team could come in tomorrow and scrap the entire governance model. No vote, no process, no recourse. The direction set for MySQL today could be reversed by whoever's in charge next quarter.
The Tests That Will Define This Deal
Zaitsev identified two tests that will reveal whether Oracle's governance commitments are real or just PR.
The first: would the community be willing to contribute changes that Oracle considers commercially detrimental? If a committer proposes a feature that undermines AWS's managed MySQL offering — say, better tooling for self-hosted deployments that makes it easier to run MySQL outside the cloud — will Oracle accept it? Or will they block it on grounds of "compatibility" or "quality"?
The second test is even harder: would the community contribute at all to a system whose future Oracle controls entirely? Trust is fragile. Once you've seen a core team laid off without warning, once you've watched governance promises evaporate under new management, the calculus changes. Contributors start asking: why am I giving my best work to a project where the custodian can change the rules whenever it wants?
These aren't hypothetical concerns. They're the exact questions that killed CentOS, that fragmented the PHP community, and that drove thousands of developers away from projects where corporate stewardship turned extractive.
What This Means for MySQL Users
For organizations running MySQL in production, the announcement is worth paying attention to but not celebrating. The steering committee gives you a channel — AWS and Google Cloud now have formal seats at the table, which means your cloud provider's interests are being represented in MySQL's strategic direction. That's real, even if it's advisory.
The committer program is a genuine mechanism for experienced contributors to gain influence. If you've been submitting patches and documentation improvements, this is your path to having a louder voice in the project.
But here's what Oracle isn't telling you: none of this changes the underlying power structure. Oracle still owns the MySQL intellectual property. Oracle still controls the release schedule. Oracle still decides which contributions get merged and which don't. The governance model is a layer on top of that — useful, but not transformative.
The PostgreSQL comparison Zaitsev invoked is instructive. In PostgreSQL's model, the community genuinely sets direction. The project doesn't belong to a single corporation. Decisions about roadmap, compatibility, and governance are made by contributors who answer to the community, not to a board of directors.
MySQL isn't PostgreSQL. And Oracle's governance model won't make it one.
The Engagement Mechanisms Oracle Listed
Oracle outlined several channels for community participation: public roadmap discussions, Contributor Summits, GitHub-based collaboration, Early Access releases, technical design conversations, and enhanced developer resources. These are all real mechanisms — they're also the standard toolkit every major open-source project uses.
What makes Oracle's version different isn't the mechanisms themselves but the context in which they operate. Contributor Summits are valuable, but they're also performative if the decisions made there aren't binding. Early Access releases give contributors a head start on testing, which is useful — but they also let Oracle gauge community reaction to features before committing to them.
The GitHub-based collaboration piece is where the committer program actually lives. That's where code reviews happen, where patches get discussed, where the day-to-day governance of MySQL takes place. If Oracle follows through on its committer program promises, this is where real influence will be distributed.
But distribution isn't the same as delegation. Oracle can distribute review responsibilities without delegating final authority. And until that changes, the governance model remains what Zaitsev called it: advisory.