The place We Are
We will all agree that the MySQL ecosystem isn’t in nice form proper now. Check out Julia’s weblog put up [Analyzing the Heartbeat of the MySQL Server: A Look at Repository Statistics], which confirms what many people have felt: Oracle isn’t as dedicated to MySQL and its ecosystem because it as soon as was. However right here’s the factor—everybody has a special concept about what to do subsequent. Some of us suppose we must always wait and see what Oracle does, and never rock the boat. Others are able to onerous fork the entire thing and begin contemporary with a brand new identify.
Right here’s what we’re pondering: let’s begin with the stuff we truly agree on. Get folks working collectively on the issues that matter, after which we will deal with the extra advanced points down the street.
What We’re Proposing
We need to create a Group of MySQL Fans – a non-profit the place corporations and people can soar in and contribute nonetheless they need.
Our mission: To develop the MySQL neighborhood as a vendor-neutral group. We run conferences, help builders, fund initiatives, and construct instruments—holding MySQL sturdy, safe, and open supply for everybody who is dependent upon it.
Which means serving to the neighborhood thrive AND serving to all of the business gamers on this house construct their companies.
To assemble everybody’s suggestions, we’re organizing two summits:
As a lot as we’d love to ask all customers, house is restricted, so these are invite-only occasions. Please submit your registration in the event you’d prefer to attend.
Inquiries to Resolve
At these summits, we’d like to carry a collective brainstorming session to reply a set of key questions:
How can we allow the neighborhood and business ecosystem round MySQL? Let’s assist everybody succeed—from particular person contributors to companies constructing on MySQL.
How about organizing a vendor-neutral convention? We’re pondering of “The Convention for MySQL Group”—not a single vendor’s present, however a spot for everybody to come back collectively.
What if we supported native meetups and conferences? Just like how the PostgreSQL neighborhood operates, we might assist native teams get organized and keep related.
Ought to we promote instruments and builders? We might help the instruments that make MySQL higher and simpler to make use of, together with MySQL connectors and help in programming languages and improvement environments.
Do we’d like higher neighborhood assets? We might arrange areas for folks to coordinate and talk—Slack channels, boards, no matter works.
May we construct a neighborhood portal? Assume postgresql.org, however for MySQL. A spot the place yow will discover every part: service suppliers, instruments, extensions, cloud companies and different assets.
What’s our code upkeep technique? That is the large one, and truthfully, we will determine it out as we go. Perhaps Oracle lets us assist contribute. Perhaps we keep a monitoring fork. Or possibly we find yourself doing a tough fork with a brand new identify. We’ll cross that bridge after we get there.
How can we deal with bugs and safety considerations? Can we allow a public bug database (the place content material isn’t restricted by Oracle) and set up a safety course of the place all stakeholders are knowledgeable and might guarantee safety for his or her prospects?
When you have extra questions, submit them within the feedback, or you may attain me at https://www.linkedin.com/in/vadimtk/
Let’s join and focus on how we must always transfer ahead!
