Richard Davies wrote: The UK has a good crop of technology pioneers in cloud computing - for example ElasticHosts, FlexiScale, Flexiant, OnApp - and also some strong government initiatives such as G-Cloud.
We will have to see whether this kind of technical leadership converts into swift mass-market adoption or not.
In the previous installment of An Open Source Business, we talked about how to determine if an open source project could also support a successful business. Now let’s look at how to build a successful commercial open-source project.
Before starting your project, ask yourself: What will make a commercial open source project successful?
Believe it or not, most developers get this question wrong because of two myths about software — and doom years of work before they’re begun.
The Two Myths
Here’s the myth that many commercial software companies have:
“The best software is the one with the most features. If we could just get more features in our program, we’ll be able to get more customers and topple Microsoft.”
And here’s its equivalent at many open source projects:
“The best open source project is the one with the most people. If we get more people in our project, we’ll get more contributions and more features, and then we’ll be able to topple Microsoft.”
And What’s Wrong with That?
For commercial software, the number of features is not as important as ease of use. Sure, I want my software to do what I need–but then that’s it. Don’t confuse me with all those other screens, menus, and buttons. I’ve got a life and want to get back to it.
For open source software, the most important thing is having good code. Every project needs more users and more developers, but without the proper technical foundation to absorb them, an open source project could easily hit a wall. (I actually wrote about this almost exactly two years ago under “The Limits of Open Source.”) A successful open source projects must be extensible, stable, and technically interesting — otherwise, who would want to work with your code base?
Now Here’s the Hard Part
If you want to have a successful commercial open source project, you need to do both. You need to create software that is both easy to use and is technically strong. It should have enough features to be useful, so that your project could support your business. Longer term, though, your project — and your business — will succeed only if your software is easy to use and well written.
This may sound like a tough balancing act, but it’s exactly what has worked for opentaps Open Source ERP + CRM. Sure, our users are looking for a program with enough features to meet their needs. But why do they choose opentaps? Because they find it easy to use, and because they like its strong technical architecture. This is why we’ve invested so much in giving opentaps a stronger technical infrastructure and making it easier to use — and we’re just getting started. If you like opentaps now, then just wait — you ain’t seen nothing yet!
In the next installment of “An Open Source Business“, we will look at competitive strategies for an open source project.