Tuesday Apr 28, 2009

The pursuit of openness

When I joined MySQL in 2006, after several profitable years as a consultant, I had a dream. I wanted to improve the product that had contributed to my professional success.

The first thing that I learned when I started the uphill task is that it was far more difficult than expected. MySQL called itself open source, but the development practices were for all practical purposes closed source. At the same time, I found that MySQL, below the surface, is an organization with complex and well oiled engineering practices.

Indeed, opening up the cathedral, as Lenz put it, was a hard nut to crack. We had a closed source revision control system, and our developers loved it so much, that any proposal to change it was met with strong opposition. We discussed technical matters behind the firewall. Our code review process, although technically demanding and very thorough, was kept in our internal mailing lists.

Sakila closed 2

Contributions were scarce, with no good signs for the future. The binary split between community and enterprise servers made bug fixes contributions very unlikely. The impossible roadmap, with contributions going theoretically to version 6.1, in the distant features, practically discouraged any new proposal of code contribution, except for a few brave souls. On top of it, the Contributor License Agreement (CLA) had only recently been set up, yet formed a formidable obstacle for many people.

Sakila closed 1

Faced with such challenges, several people left. Either to new jobs inside the company or to new shores. The challenge is that you can't fix such a problem in one sweep. Changing practices in a company, especially from a position in which you can't take decisions, is really hard.

But not everyone left. The ones who stayed, in spite of the adverse circumstances, share a strong belief in the values of open source, and were determined to succeed, no matter what it takes.

With a little help of my team mates, Colin, Lenz, and Dups, I continued to support Kaj's internal action to spearhead the changes. While my younger colleagues were busy managing the community, Kaj and I were gently wrestling the rest of the company, to steer its direction towards a more open course.

The results arrived. Slowly, but surely.

  • In 2007, many developers opened the IRC gates, and started using freenode.net;
  • June 2008 - The open source Bazaar replaced the previous lock-in proprietary software Bitkeeper, which didn't allowed handling of the source from the outside;
  • In October 2008, we got rid of the CLA, in favor of the more open Sun Contributor Agreement.
Sakila open 1

The major obstacles were still the binary split and the long release cycle. There were much discussion internally, pleading and cajoling, to convince people that we were on the wrong path, and that our business model required a more open approach. Our team was under pressure. We were between the hammer of the community, shouting at us for not being open, and the anvil of the sales and marketing teams, unwilling to accept the assumption that a happy community generates future customers.

We kept going, and we kept pushing, until we got the announcement at the MySQL Conference 2009, stating the end of the binary split. Now the community server binaries will be published as often as the enterprise ones. The rationale of this request is that the strength of MySQl is in its wide community. We claim that the MySQL server is tested by millions of users, and yet we were giving the GA (mature) binaries only to a handful of customers.

This looked like a privilege, but it was in fact, from an engineering standpoint, a disadvantage. As a customer, I would gladly adopt a software that has been installed by a few million people, rather than being the privileged first one to try it in production.

With this announcement, we are back to the position that has made MySQL so popular and trusted. A database with a large user community.

The last barrier to fall will be the roadmap. So far, we have been tied to an impossible roadmap, with a wish list of features that had little chance of being released. The experience of MySQL 5.1, which took 37 months to release, has taught us a hard lesson. The next version, 6.0, has been in alpha for 25 months, with no near end in sight. Now we took the hard decision to replace the previous roadmap, where we piled features over features in an impossible attempt of pleasing future customers, with a milestone model, where we release features as they are mature, without waiting for all the features in the list to be ready. It means that we renounce the goal to release Falcon and Maria and the Online Backup as one single big bundle released at the same time in 6.0, and we put them aside. The MySQL engineers will schedule features for release as soon as they reach beta status, without waiting for the trailing ones.

Furthermore, we have now a process in place to accept contributions and to review them, with active participation from core developers. Yet, we have still work to do, to smooth the rough edges both internally and externally.

Sakila open 2

To our developers, who have not succumbed to the pressure, and have delivered top class software, while accepting our team's (not always) gentle suggestions to more openness, a hearty thank you!

To the many who have believed in MySQL and in our single and team efforts, thank you! To the many, who have suggested improvements, and contributed actively to our changes, thank you! To the ones who have not joined the flame war when unjustified rumors spread across the net, thank you!

To the ones who spread FUD, and twist every tiny piece of news in the shape of a conspiracy, I say wake up. Have you considered the possibility that we actually strive for the best for our community?

To the naysayers, who shout at us and abuse our goodwill from their self appointed righteousness, which often hides a secret business agenda, I say that we have always be working with the community in mind, and we will continue to improve. The path is still uphill, but the community team, the guardians of MySQL ubiquity, is happy with the progress so far, and will continue on this course!

Wednesday Jan 28, 2009

Speaking at FOSDEM

I am getting ready to FOSDEM, the biggest European gathering of free and open source software enthusiasts. The event is held in Brussels, Belgium, on February 7-8, 2009.

FOSDEM, the Free and Open Source Software Developers' European Meeting

MySQL has a developers room on Sunday, with a schedule rich of well known names and juicy topics.

I will present a talk about partitions in MySQL 5.1.

Lenz will have a talk in the main conference, on MySQL high availability.

There is a wiki page on MySQL Forge where we will provide last minute information.

See you all in Brussels!

Monday Sep 15, 2008

250 Sun/MySQL engineers at Software Freedom Day in Riga

The Software Freedom Day 2008 is approaching. The event will take place wherever you want. If you are interested, just register a team, gather a few friends, and start organizing that in your street, at a local pub, in your university, or wherever you see fit.

MySQL people are very conscious about open source, and we decided to participate to the event somehow. For starters, Sun is a sponsor, and that is a good sign that we care. But we need also to make our presence known. So the initial plan was that every Sun community would encourage its members to create a local Software Freedom Day team and participate.

However, on September 20, the designated day, 250 Sun/MySQL engineers will be in Riga, Latvia, in the middle of our annual developers meeting.

Not a problem. Since we're there, we can celebrate abroad. We have a culture of working from home and while traveling, so an event away from home does not scare us. We got in contact with the local communities, and organized a team in cooperation with

And probably more people who may have joined the effort since we started.

It's a Latvian event, with a distinct international flavor. We will gladly provide the speakers necessary to the event, and the locals will inject their enthusiasm. In the evening, a buffet will combine free software and free beer in a well tested combination.

A special thanks to Leo Trukšāns and Michael Dexter for showing us the way through Latvian open source paths. To Georg Richter for scouting the paths in Riga, and to Lenz Grimmer, for gluing all the above together.


Giuseppe Maxia


« June 2016