- Ã¢â‚¬Å“Am I doing the right things with my life?Ã¢â‚¬Â
- Ã¢â‚¬Å“Which habits could I change -- in order to be a better neighbour?Ã¢â‚¬ÂÃ‚Â
Since Karen Tegan Padir took over the MySQL product from MÃƒÂ¥rten Mickos, we at Sun have taken a thorough look in the mirror.Ã‚Â The result of this introspection allows us to publish our conclusions and new community commitments this week in conjunction with the MySQL Conference & Expo in Santa Clara.Ã‚Â
For those who don't yet know Karen, let me state a few facts:Ã‚Â
- Karen is VP of Sun's newly-founded MySQL & Software Infrastructure group
- She describes herself as a geek and a straight-shooter, and I can attest to bothÃ‚Â
- She was deeply involved in Sun's decision to acquire MySQL, as well as the subsequent integration work throughout 2008Ã‚Â
In my previous blog,Ã‚Â "MySQL Culture and Business Philosophy Goes Mainstream at Sun",Ã‚Â I stressed that the key point to remember is that Sun is completely committed to building a big open source-based business, and very much supportive of the various communities that Sun is engaged in. That may sound a bit abstract, so I have worked with my new boss, Karen, to spell out for the MySQL community what it actually means in practice:Ã‚Â
First: We shall now start releasing MySQL Community Server binaries as frequently as we release the MySQL Enterprise Server. We want everyone Ã¢â‚¬â€œ community and customers -- to get the best bits first from us. This is why future Monthly Rapid Updates of MySQL 5.1 will remain available for the community. Moreover, future MRUs of MySQL 5.0 will also become available for the community.Ã‚Â
Second: We shall focus even more on our traditional core product values of stability, Performance and Ease of Use. Like you, we hate bugs, we hate slow, we hate waiting for fixes, and we hate awkward usability -- even more than we love new functionality. The MySQL 5.4 performance release, which is considerably faster than MySQL 5.0 or 5.1 in most use cases, is a case in point.
Third: We shall allocate additional resources to the health and well-being of the MySQL Community. We focus both on users and developers. We shall now devote a greater portion of our internal MySQL Engineering Team resources to reviewing and eventually merging architecturally-compatible features written by external contributors, even if those features weren't on our own roadmap.
Finally, fourth: We shall do more to improve our internal software engineering practices. We will brush our teeth every morning and evening, exercise several times a week, and eat (mostly) healthy food.Ã‚Â Some of us may at times stillÃ‚Â take a vodka shot, but if so, then only to be social and to provide anÃ‚Â excuse for singing badly, but not while writing code.Ã‚Â
In the spirit of open-ness, please give us ideas on how we can implement these changes. Let the MySQL community team know what you think. For those at the show this week, stop Karen in the halls and introduce yourself. Above all, enjoy!