|
Marten Mickos, former MySQL CEO, now Senior SVP with Sun Microsystems, is expected in Rome, at the local University, called "La Sapienza" (= Wisdom or Knowledge). The event, on May 30, is a mix of private and public occurrences. Marten will meet local customers and Sun officials, before speaking in front of an audience at the University. More information at the other speakers' blogs. Ivan Zoratti and Giuseppe Maxia |
|
Marten Mickos, former MySQL CEO, now Senior SVP with Sun Microsystems, is expected in Rome, at the local University, called "La Sapienza" (= Wisdom or Knowledge). The event, on May 30, is a mix of private and public occurrences. Marten will meet local customers and Sun officials, before speaking in front of an audience at the University. More information at the other speakers' blogs. Ivan Zoratti and Giuseppe Maxia |
After all the fuss it appears that MySQL will be remaining open source after all. As Kaj Arno and Monty Widenius report, Marten Mickos announced at CommunityOne that the MySQL Server will stay open source, as well as the forthcoming encryption and compression backup features, which MySQL had considered making available only to paying customers.
“The change comes from MySQL now being part of Sun Microsystems. Our initial plans were made for a company considering an IPO, but made less sense in the context of Sun, a large company with a whole family of complementary open source software and hardware products,” writes Kaj.
“My hope is that the experiment when it comes to closed source extensions developed by Sun is now ended. As far as I know, there is no existing plans for any closed source extensions to the MySQL server,” adds Monty.
While that seems pretty clear cut, there is still room for a little confusion. Kaj writes: “To financially support MySQL?s free and open source platform, we have a business model which allows both community and commercial add-ons, and we remain committed to it.”
Monty clarifies: “I interpret this, in the context of Mårten’s and Jonathan’s announcements, that we will continue to support and make available commercial addons to the MySQL server from third party, like the Infobright storage engine. Things that we develop ourselves at Sun, at least on the server, will continue to be open source.”
UPDATE - The phrase “at least on the server” is revealing, however. Matt Asay points out that MySQL will continue to develop commercial add-ons above the server, which is the direction as I understand it, and - as I noted two weeks ago - has been the direction for some time. - UPDATE
While we’re on the subject of MySQL (again) it’s also worth taking a look at the slides (PDF) from Monty Widenius’s “Future Design Hurdles to Tackle in the MySQL Server” presentation at the recent MySQL Conference and Expo.
The slides provide a fascinating insight into the technical challenges Sun and MySQL face in positioning MySQL for wider adoption, as well as evidence of the intention to be more open, both about the nature of the challenges and in accepting more contributions from outside the company.
As slide 18 states, the fact that the MySQL community is not currently contributing to development means that the project is not benefiting from the experience of real-world users and that the user base is growing slowly.
The suggested solution is to open up the development process to give outside developers commit and decision rights and to learn from how PostgreSQL is developed. I previously wrote that “if MySQL does choose to develop closed source extensions to the GPL code it will probably have to find some way of balancing that with providing more value to the community.”
It would appear that the development of close source extensions is no longer an issue, but that providing more value to the user community remains a priority. Sun has gained a lot in acquiring MySQL, but one thing it hasn’t gained is an understanding of building a wider developer community. In fact, MySQL has a lot to learn from Sun in that regard - both its successes and its failures.
Zack Urlocker says MySQL 5.1 has zero bugs. He may have been misquoted, or quoted out of context, but there it is. I’ll quote enough of it that you can’t take it out of context twice:
Mickos also said MySQL 5.1 has upgraded its reliability and ease of use over 2005’s v5.0.
“Now we can admit it, but this version is much improved over 5.0, which we weren’t totally happy with,” Mickos confided.
He reported that more than 1,300 bugs (997 in 2007, 386 so far in 2008) have been fixed in v5.1, and that, according to standard DBT2 benchmarks, the performance of v5.1 is 10 to 15 percent better than the previous version.
“This version now has zero bugs,” Urlocker told eWEEK.
You can check for yourself at the MySQL bug statistics page.
Of course it’s not true. But what did Zack really say, I wonder?
bugs, innodb, Marten Mickos, mysql, Zach UrlockerYesterday I had the opportunity to listen to Marten Mickos deliver the opening keynote at the MySQL conference here in Santa Clara. As usual, Marten does an enviable job at delivering a presentation which talks about MySQL’s business, its new relationship with Sun Microsystems, and what this all has to do with Open Source.
I’ve been lucky to hear Marten speak at a number of events, and have found that one of the most consistent themes can be distilled down to this (which we at Hyperic fully subscribe to):
Build a great product, Empower your Users, Build a great business
He also reiterated the importance of the GPL as an essential element to drive empowerment of users. This lets them adopt products and participate while creating an opportunity for businesses to deliver value people are willing to pay for. A virtuous cycle, right? Sun seems to think so also (a billion dollars is not the type of money any company throws around lightly)
Ironically, as I was in the middle of writing this post, Slashdot’s editors let out this gem in a post claiming that MyS^H^H^HSun had “begun to close source MySQL”. Luckily, Marten was able to set the knee-jerk cable-news-inspired Slashdot post straight by again explaining to the readers that MySQL is a business which has been able to build a great free, open, GPL database by creating value they don’t necessarily give away. He’s candid about the fact that they are experimenting trying to arrive at the best business model that balances all the elements of the above equation. Obviously, it’s not easy and someone’s undoubtedly going to get upset with the result. Apparently some people on Slashdot think MySQL’s database is written by monks who are morally opposed to any compensation.
Why is this important? Well, because software doesn’t build itself. Another admirable (if slightly more outspoken) guy named Marc Fleury made a big point of that with JBoss’ “Professional Open Source” business model. Everyone got what they wanted: the community got a great, free, open J2EE app server, and JBoss got paid to hire more people to continue to build it.
Recently there were a few examples of failed companies in the management space which either directly used open source or had some connection to it in their businesses. Many wonder if the failure had something to do with open source, their choice of license, or the business model. Few (if any) looked at the more obvious part: the products offered by those companies. Just because something is free and open source, it doesnt mean people will flock to it. Without that first element of the equation, there’s no adoption and no opportunity to create value people will pay for. The result is a failed business. The formula for creating that value is still being developed and is different for every company. We’ve chosen one which so far has brought us much success, but might not work for others.
Much like MySQL, we’re eager to experiment with different ways in which we can deliver the best products to the largest audiences while delivering financial success for our employees and investors. Over the course of this year, you’ll see us continue to enhance and deliver more features and functionality to our open source platform, while continuing to enhance the value of our various subscription offerings. Also like MySQL, we’re eager to engage our community directly as we experiment and learn how to continue to build the best solution to managing large scale web infrastructure.
A while ago I asked for people and/or organizations to sponsor development on Maatkit (formerly MySQL Toolkit) so I could take a week off work and improve the Table Sync tool. I asked for $2500 USD, but several companies have graciously offered to cover that and then some.
I'm very happy about this, as it will allow me to dedicate a solid week to fixing bugs and adding features. There's a lot of demand for the tools, and there are a dozen or so bug reports unresolved for the table-sync tool, which I personally want to fix as much as anyone. So I'm very grateful for the support.
Here are the companies who have promised their financial support:
MySQL AB have offered $3000 USD in support. I had an email conversation with Mårten Mickos, MySQL's CEO, and he expressed his happiness about the project's success, and his pleasure in supporting the project:
We have seen you operate in the community and you always have constructive and good ideas. That's why we want to support you. Our goal with this is to stimulate innovation in the MySQL ecosystem.
I don't know how the idea to support the project started at MySQL AB, but that quote really tells me "we get it: we have a symbiotic relationship with our community of users." In a follow-up email, Jay Pipes wrote,
... MySQL wants to make it clear that we very much support and appreciate the work you've done on the toolkit. It has proven to be one of, if not the, most popular and successful open source ecosystem projects surrounding MySQL and for good reason. So, for your work and commitment to the project, a big thank you from MySQL. :)
Secondly, we would like to encourage you to be open and public about our support of you. The community team is always looking for opportunities such as the one which presented itself with your toolkit, and we want the outside community to know about our support and encouragement. Therefore, you have our blessing and encouragement to blog about the sponsorship of your development work. Please do let us know if and when you decide to blog about it. Remember also that this sponsorship is no strings attached. There is no expectation of specific work on our end.
Blue Ridge Internetworks have offered $1000 USD in support. BRIworks, as they're known locally, is headquartered in the town where I live, Charlottesville, Virginia. They offer networking consulting and services. Jeff Cornejo, who offered the support to me, is a friend and used to work where I used to work, and several other highly respected friends and ex-co-workers work at BRIworks too. BRIworks provides Internet service and hosting for my employer.
Percona have offered $500 USD in support. Percona does high-performance website consulting, and are perhaps best known for having some of the world's top MySQL experts, including Peter Zaitsev and Vadim Tkachenko, two of the co-authors on High Performance MySQL, second edition.
Last, but absolutely not least, my employer, The Rimm-Kaufman Group, who do paid search marketing and website effectiveness consulting. They have let me spend a significant amount of time writing these tools for use on our own systems, and instead of keeping them in our own Subversion repository, allowed the code to be released as Free Software. The time I've spent on the tools has gone well above and beyond what we needed to get our work done. Finally, RKG has blessed my unpaid week off to work on the tools.
A big thanks is due to all of these companies and individuals, as well as other people who have contributed financially and otherwise.
I'm grateful for the sponsorship, but I think the real winners are the MySQL community, who have benefited a lot from Maatkit. It has made a lot of hard things easier and impossible things possible. If you're one of those who benefits from Free Software, I encourage you to patronize the businesses that believe in and support it. Four fine examples are listed above! Not coincidentally, all of them are the creme de la creme in their respective fields.
Finally, a quick journalistic note: I pre-approved this post with representatives from the companies I mentioned, because I respect their right to represent themselves as they wish, but the words are mine, not theirs.