It is a new year and it's time again to start thinking of all the great people and companies that make the MySQL ecosystem so great. It is time to start thinking of this year's MySQL Community Awards.
Last year we had a record number of winners, eleven goblets were handed out! But behind the scenes things were even more exciting, there were several ties that forced the panel to do extra tie-breaking voting rounds. In one category we even had a 6-way tie! All of this just testifies to how much is happening in the MySQL world nowadays.
There are a few interesting learning resources recently created by activists in the MySQL community. I just wanted to link to them to spread the word. They are free and if you've been looking for a way to learn more about MySQL, you should have a look at these.
This is something I haven't really seen done before (for MySQL): a virtual self study group. It is based on the idea of everyone reading the same book, and I assume Sheeri will then facilitate some commentary on what your read. Sheeri mentioned this in a blog post earlier, but yesterday I went to check the signup page and wow - there are already 117 (or 76, depending on whether you look to the left or to the right) students registered!
The Winter season for conferences is catching up speed.
As I write this the DOAG conference in Germany is happening. It is one of the biggest (or the biggest?) Oracle user group conferences outside of USA. Many of my European friends in the MySQL space are talking there. As you know I have been a big fan of Galera Cluster for MySQL for over a year now, but I was perhaps a bit of an early adopter. Lo-and-behold, I was surprised to see the DOAG related press-release from SkySQL puts the creators of Galera first in their headline: Codership, SkySQL und weitere Top-Experten rund um das Thema ‘MySQL Datenbanken” in Nürnberg versammelt. Talk about crossing the chasm! Ralf Gebhardt, my other mentor from MySQL AB times, is speaking on MySQL HA solutions. Seppo, Erkan and Oli and people from Oracle are talking too.
Percona Live UK, Dec 2-3
It's the time of the year again: You have 2 more weeks to submit a great proposal to the biggest and baddest MySQL Conference: Percona Live MySQL Conference and Expo 2013 (Santa Clara). Like many things in the MySQL community, this conference has also gone through a transformation over the past 3 years. But last year the growing pains and uncertainty ended with Percona putting up a great show. Attendance was up again (over 1000) and there was a sense of energy and excitement for the future of MySQL. If you are like me and like to dwell in nostalgia (so that you can get into the right mood for submitting great proposals) my coverage of last year's conference is found here: part 1, part 2. (If you don't care about the nostalgia, remember that speakers get into the conference for free!)
Simon Phipps, who's Computer World UK blog isn't aggregated on Planet MySQL, has a blog post which reveals the truth behind the missing MySQL test cases that many of us commented on some time ago (including myself). You can read Simon's blog post here.
As you remember, there were various things that happened (or rather ceased to happen) during the Summer which led to people complaining that Oracle's MySQL is closing down. As a result of the uproar, source code trees at Launchpad were immediately refreshed. Otoh, there was never any public explanation why test cases for new bug fixes are withheld.
Here are the slides of the talk I just gave at Froscon. (Video should be available soon.)
I promised to still post some general comments about the MySQL ecosystem, to conclude my outlook of State of the MySQL forks and Drizzle. I will do this now in the form of answering questions I got in the comments, twitter and some that I make up just myself.
I got several comments and questions on my previous blog "The State of the MySQL forks". One question was "Why didn't you mention Drizzle?" So I will say something about Drizzle here before concluding with other remarks.
So why didn't you mention Drizzle?
Mainly because the post was already long and also I had to wrap up and call into a meeting.