This year was the first year the public could nominate candidates for these awards. We got in many nominations and this really helped the panel to get an overview of everything that is noteworthy in the MySQL ecosystem right now. Thank you to everyone who participated by sending in nominations.
In the first category the panel received and debated over a dozen suggestions. There are so many great people in this community, it is easy to think of people who truly deserve to be awarded. There were however two persons who clearly stood out with a track record of years and years of broad and really key contributions to the MySQL community. These two persons also clearly stood out both in number of nominations and number of votes. Therefore, the...
It's now 2 hours until I depart for San Francisco and then Santa Clara for this year's MySQL Conference. Can't wait to meet everyone and to learn about cool new things (2 solutions for parallelizing replication, Drizzle, Xtrabackup...)
This year I am involved in two BoF sessions: Severalnines ClusterControl with Johan Anderson and Xtrabackup Manager with Lachlan Mulcahy. Both of these are about brand new topics, this being the first time they are presented, so I'm excited to be working with these guys.
This is just a friendly reminder that you can nominate your favorite MySQL community member, application and company for the traditional awards. The nominations must be in by the end of this week, after which the panel votes on them:
I've seen at least a few people on IRC that were thinking of sending in nominations, now is a good time to do it!
The address is email@example.com
The headline above could fit in a tweet, but Drizzle making its first release almost 3 years after the project started deserves a blog post.
Brian Aker has a long blog post looking back at these 3 years (and even longer into MySQL history). Stewart Smith has an entertaining personal perspective. .frm files, I will not miss you (if I were to start using Drizzle, that is). Planet Drizzle has an avalanche of posts from most Drizzle devs celebrating this event.
An annual tradition of the upcoming O'Reilly MySQL conference is the awards ceremony. Originally the winners of these prestigious awards were nominated and selected by various MySQL AB personnel. 2010 was the first year when the winners were selected by a community panel. This year we are building and expanding on that: This is an invitation for everyone in the community to send in nominations for the awards in the 3 categories named below.
Please send in your suggestions for deserving winners
no later than: 23:59 Sunday March 27th (Pacific time)
Some time ago Stephen O'Grady and Brian Aker had an interesting Blogo-dialogue about what they call the "Cambrian Explosion" of open source development. The Cambrian Explosion means that we increasingly see forks of projects being developed in different directions, where traditionally we are used to open source development happening in relatively hierarchical and easy to follow upstream and downstream relationships. This is exactly what happens in the MySQL community currently, where in total there is more progress than ever before, but that progress is divided among several competing forks, none of which is strictly in an upstream-downstream hierarchy with each other.
I used to be a bit frustrated about this state of affairs, believing that if at least most of the forks could co-operate on a common tree, we would see even faster progress. But when I left MariaDB some months ago, I realized that the situation is what it is and since all existing MySQL variants are associated with a commercial vendor, there wasn't an obvious choice for me to continue contributing, which I still want to do. So I thought I might as well embrace this Cambrian Explosion thing and just publish my own fork as a contribution to the community.
Giuseppe "The Data Charmer" Maxia recently posted his take on the MySQL forks. I had been pondering whether to do the same, and seeing that what I planned to write will nicely complement Giuseppe's article, I was inspired to follow him into the same topic. Note that last Spring I created a Map of MySQL forks in preparation for Monty's keynote at the MySQL user conference. So let's see how things have evolved. I'll look into MySQL ecosystem as a whole and the forks separately.
The post is long, but the key takeaway is that despite the challenges, the combined development seen in the MySQL ecosystem is probably stronger than ever, the current situation is hard for an outsider to grasp but manageable, and if a few more obstacles can be overcome, we are looking into a very bright future indeed. There are more than 100 engineers (how much more?) working full time on the mysql code base (including both developers, QA, build engineers...). This development effort is an order of magnitude higher than other open source databases I'm aware of, in particular PostgreSQL and Drizzle. Often the open source project with most momentum and mass will come out as the winner, no matter what challenges it may seemingly be facing, and this is the case with MySQL too.
Some time ago I was asked to do a study of our most popular open source projects to assess 1) what governance models are out there and 2) if the governance model has any effect on the project's success (such as size of developer community) on the one hand and on the other hand on the business of the related vendor(s). Some of the results are quite remarkable and have general applicability, so I wanted to share them here:
(Small updates done on 2011-07-14. OpenJDK size clarified on 2012-05-21.)