Slashdot Mirror
Ask MySQL's CEO About Running a Free Software Business
There have been so many articles written about the perils, pitfalls, and possible rewards of running a business based on free or open source software that we can't possibly link to them all. Instead, let's ask MySQL CEO Mårten Mickos how to make money with a company based on free software, because he runs a company that is almost always touted as one of the world's greatest free software (business) successes. You may want to read some of these interviews with Mårten before you come up with your own questions in order to avoid duplication, but other than that suggestion and the usual Slashdot interview rules, ask whatever you like, however you like.
In your eyes, what's the biggest problem with MySQL? More specifically, what leaves market share room for Oracle & your competitors? Do you even see yourself as having any competitors since your product is free?
My work here is dung.
How do you fight the perception that MySQL is not suitable for 'the real world' because it is free?
Dark Reflection
In a market where people are just looking for stability, simplicity & scalability, where do you turn for innovation in your products? Is there a lot of research and development towards new features and completely new products in MySQL's community or do you aim primarily to do one thing well? How do you influence the direction of this research in such a large open source project? Do you attempt to add direction at all?
My work here is dung.
Your website touts you as having the lowest defects per KLOC by up to 12 times the industry standard, what do you attribute as the leading factor to your success in this respect? Since cold cash is the traditional method, how do you incentivise code quality in an open source product?
My work here is dung.
In your five years as MySQL CEO, what has been your proudest moment? Do you find it difficult to lead a company based on a product that belongs to a community? Do you ever experience any fallout/backfire from running your company on such a business model?
My work here is dung.
When you plan your software product roadmaps, what feature requests do you pay more attention to? Enterprise customers want scalability, reliability, redundancy, and security; but some database programmers are looking for features such as solid transaction support, stored procedures, and more functions. How do you rank which feature requests get attention first?
-- Stu
/. ID under 2,000. I feel old now.
One of the most common complaints I've heard about the business model of profiting on support for a product, is that it provides motivation to keep the product from becoming very user friendly. After all, if the product is too easy to use, who will pay for support? In my own experience, I've seen a lot of companies that consider support to be insurance, and don't use it for help with installation, configuration, or to overcome usability issues so much as a way to cover their asses in case something goes very wrong. Do a lot of your customers use support to overcome usability problems and if so, does this de-motivate you to solve other usability issues?
To avoid asking something that's already been answered, here's a synopsis of some of his more recent interviews.
In Guy Kawasaki's Blog, he's asked:
1. How do you make money with an Open Source product?
2. What changes in the Open Source community's attitude have you encountered since you decided "to build a company" around MySQL?
3. Do you compete head to head with Oracle or do you have different customers?
4. What's the biggest MySQL DB?
5. What's the weirdest use of MySQL?
6. What's the most "mission critical" use of MySQL?
7. How does a company controls what's happening to its product when the Open Source community is doing the programming and testing?
8. Is Open Source hindering innovation because it's one thing to debug an existing product but it's another to design a new one?
9. Who fixes the most bugs?
10. If MySQL ceased to exist as an organization, would MySQL the product continue?
In InfoWorld, he's asked:
1. Recently, a number of open-source developers have expressed their unhappiness with the Free Software Foundation (FSF) and the second draft of GPLv3. Are you concerned about a potential forking of the license as some people stick with GPLv2 and others move to GPLv3?
2. How do you decide when MySQL needs to develop new features for the database and when to rely on the open-source community for those innovations?
3. So, is open source then a more forgiving environment than the proprietary software world?
4. What's ahead in 2007 for MySQL?
5. What's the latest news on Falcon, the transactional database engine being developed by database architect Jim Starkey who joined MySQL in February?
6. Is MySQL's current dominance of the open-source database market ever a cause for concern?
In Forbes, he's asked:
1. How is open source software influencing what the bigger tech giants like Oracle, IBM and Microsoft will do in the next year?
2. Do open source firms that sell to large, proprietary software companies risk being dubbed sellouts by the community that's helped them develop their software?
3. How do Oracle's recent open source acquisitions affect MySQL?
4. Is Oracle more of a threat now?
5. What is MySQL's workforce like?
6. MySQL recently took funding from Red Hat, Intel and SAP. What's the strategy here?
7. Is there an IPO for MySQL in the future?
In LXer, he's asked:
1. What are your short and long term goals do you have for the MySQL database system?
2. Realistically where do you think you will pick up quick conversions to enhance your immediate market share from your competitors? Later, how much market share must MySQL commercial versions have to pick up to have long-term viability?
3. If you see your main opportunity is in the replacement of Oracle installations does MySQL match or exceed the forte of Oracle in the transaction per second processing? Are you now aimed at the lower end of the Oracle market installations? What will it take to be really competitive with Oracle at the upper end of the scale?
4. If you see your natural market as the range SQL Server is now aimed at, small medium business and departmental installations, can you match their ease of administration? If not what is the salient argument for such companies to install MySQL over the competition? Since you are primarily aimed at the market willing to pay for your enhancements and support, do you see any advantage in offering a MySQL product that will undercut MySQL server from below?
5. What trade offs have had to be made to make MySQL 5.0 commercial version more feature rich and robust?
6. Where do you see competition arising from for pursuing the paths to th
Why is MySQL's justification of claiming the GPL applies to the MySQL wire level protocol itself?
This doesn't fully explain the situation (as noted by the linked article), but it does at least provide a bit more info:
o nt-discontinued.html
http://chisflorinel.blogspot.com/2006/09/mysql-fr
Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
Hello Mårten,
First, congratulations on MySQL's market capitalization! My question is:
I have been working part time for about 6 years on software for text/data mining and general semantic information extraction. Almost all of my development is in Common Lisp, but I have ported little bits to Java and released that under the GPL in the past. I view this as a small, niche market, not like MySQL. What do you think that chances are for making money on GPLing a niche product?
MySQL is very widely used so if you capture commercial use icensing costs for a small percent of users, you do very well. For my software, with luck perhaps a few hundred companies a year might start adopting my product. Does it seem like wishful thinking for me to use a GPL based business model like MySQL's?
I want my customers to have my source code for a lot of reasons, but I would also like to capture revenue. I might just end up going to market as a proprietary product that incidently includes source code, with licensing that prohibits redistribution to non-customers.
Thanks for your help,
Mark
Is there anything to stop someone from:
a) reverse engineering the protocols and creating their own closed source libraries to access the database
(As a corollary to this, if GPL software can claim this, what is to stop, say, Microsoft from imposing punative costs on 3rd party software that attempts to interoperate with its own servers and/or clients?)
b) modify the older LGPL library to bring it up to date with the current database? Though the changes would have to be released, the code that accesses it would not... if I understand it correctly.
c) using one of the existing modified-LGPL or Closed Source libraries?
If it is not possible to do this, why? If the mere deployment of the database or inter-operability with it becomes grounds for being compelled to open source everything (or potentially be compelled to pay exorbitant fees) which in any shape, way, or form builds upon GPL software, then is there not a real danger for any more conventional (closed source) software company to potentially have their business model be destroyed overnight at the whim of the open source developers or the dual-licensed software/support company? How is a commercial software company supposed to port their software to, say, the Linux platform without facing this kind of risk?
To be clear, I am not opposed to a hybrid licensing model. I can see the advantages for various parties, namely, Open Software developers and the MySQL AB. Providing everyone behaves reasonably and consistently, I see this as being a workable system. However, I can also see great risk for businesses that wish to build upon open source software if a reasonable licensing structure is not available (or continued) that permits closed source development.