Archive for October, 2006

Forks vs. distributions

Monday, October 30th, 2006

Dries Buytaert, lead developer on Drupal, has written an insightful post on the difference between forking a project and different distributions of that project. As he notes, the differences can be subtle, but ultimately come down to the intentions behind the divergence, revealed in how much the fork/distribution relies on the original project’s foundation for future development.

The distinction is critical in light of Oracle’s fork of Red Hat Enterprise Linux: customers that buy into Oracle’s support are effectively buying into a fork, and one that Oracle is ill-equipped to support.

But the distinction plays out every day in a myriad of different projects, and occasionally turns into a full-fledged fork, which tends to benefit no one (which is why it rarely happens in the community-minded open source world. Dries writes of Drupal:

It is important that Drupal distributions collaborate, and not compete. To do so, we have to provide Drupal distributions an environment that encourages collaboration, and that allows for specialization (such as custom documentation and support) without introducing incompatibilities that drive competition.

The good news is that we know how to do this. We’ve been through this already with CivicSpace (previously called “DeanSpace”), a Drupal distribution for online campaign management and grassroots activism. They were quick to realize that the success of the CivicSpace distribution depends on the success Drupal core, and vice versa. The decided they shouldn’t fork core development. Instead, CivicSpace decided to do all its development on the drupal.org infrastructure, to synchronize releases, to submit all patches upstream, to centralize bug reports, and to share documentation where possible. Collaboration, not competition.

The bad news is that can be hard work. People will find that creating a distribution is fun and easy, but that being a responsible maintainer might be a lot less fun. Who wants to track changes, write documentation, maintain modules, provide upgrade paths, manage releases and provide support for years to come?

In short, distributions are fine because they add value to the core. Forks are bad because they splinter communities and thereby fragment value, attenuating it until the point that either the fork dies or the originating project dies.

For this reason, I agree with Dries. What’s true of Drupal is true of other open source communities. He writes:

As a community we should disapprove Drupal distributions that do not intend to collaborate, that have no signs of long term commitment, or that risk locking people in.

Amen, Dries.

IT still matters…

Monday, October 23rd, 2006

InformationWeek has a great story and survey detailing where and how the industry’s top enterprises spend their IT dollars. The results are illuminating, and portend great things for open source.

Interestingly, IT dollars continue to rise, even as overall company revenues fell from 2005 to 2006:
InformationWeek 500 IT Dollars Spent
As for where those dollars are going, despite all the hype that licenses don’t matter (because the real costs are in implementation), the numbers don’t bear that hype out. The numbers say, “Enterprises are wasting money on licenses.”
InformationWeek 500 - IT Spending by Category
The license cost savings open source delivers (as compared, say, to Microsoft), however, would be negated if open source implementations cost more (in fact, they cost less or at least give the CIO choice as to how she spends those dollars) or if open source required more IT personnel (clearly the biggest IT cost). But experience proves otherwise, as The Robert Frances Group has written.

Besides, as The Christian Science Monitor and others have found, open source makes those IT personnel costs stretch farther, deliver more innovation, etc. Open source makes IT dollars work for the enterprise, and not for the vendor.

So, Posted in Uncategorized | No Comments »

Microsoft’s top competitors

Thursday, October 12th, 2006

You want to know what keeps Steve Ballmer up at night? Apparently, not specific competitors, but rather competitive industry trends that strike at the core of Microsoft’s software license business model: open source, advertising, and software-under-the-guise-of-hardware. (Thanks to Brady for calling out the BW article.)

Ballmer says:

Who are Microsoft’s top competitors?

Guys who can touch us in multiple places probably matter more than guys who can touch us in any one place. And actually we don’t really have our big competition from any one company. Any one company, we know how to compete with. It’s alternate business models that we will have to embrace or compete well with. You give me any enterprise software company, O.K., and I’ll say c’mon. We know how to go do that. We do do that. And we’re really pretty good at it. We haven’t gotten any worse at it. Boom. Boom. Boom. We know how to keep coming.

[Take open source.] Open source is not a new technology area. It was a new business model. In the last three or four years, we have competed very well by extending our value. Open source never goes away as a business model or competitor. We have learned how to compete with open source, and we will compete with it for the rest of time. But competing with open source will have to be something that’s burned bright on the foreheads of our senior people.

The second big competitive force is advertising as a business model. Typically, people just want to reduce that to Google, and if you want to do that, you can. But it’s do we embrace advertising fully enough as a business model? Because at the end of the day, anybody who comes at you with a cheaper-to-the-customer proposition, you got to worry about. And advertising looks cheaper to a consumer than something you pay for.

In the case of open source, we couldn’t adopt the business model. We adopted a competitive approach that so far has worked very well. In the advertising case, we can embrace that model. We don’t have to sit here and say it’s that bad.

A third model I could sit here and write down on this list is that there are cases where software gets monetized through hardware. That’s what an iPod is. iPod is a software thing. You just happen to collect the money on the hardware. You could say in China and India, it’s unclear whether classic software will get paid for as much as advertising, hardware, subscriptions, etc.

So our ability to embrace and benefit from or compete with new business models—and I would say ad-funded and open source, more than this hardware thing—is more the way to categorize the key competitive dynamic for us.

Fascinating stuff, and I’d encourage you to read the rest of the interview, too.

This isn’t revolutionary stuff (Clay Christensen has been talking about how to disrupt an industry for some time), but it’s interesting to hear the CEO of the world’s largest software company candidly explaining how to beat Microsoft. As with open source code, just because you have “the answer” doesn’t make it any easier to crack the code.

To disrupt a Microsoft product you have to cut off its traditional air supply. Open source is disruptive to Microsoft because it a) removes the one-size-fits-all approach that Microsoft imposes and b) the entry cost is $0. Microsoft knows how to disrupt with “free” (remember IE?), but it has yet to learn how to compete with someone else undercutting its prices by 100%.

Over the long haul, however, it’s going to be modifiability that beats Microsoft. This will sound odd to many, because the common industry wisdom is that no one wants to modify anything. We just want to passively consume software. My experience at Alfresco and Lineo, however, has been the complete inverse of this received wisdom. Many users want their Firefox customized to them. Many enterprises want their ECM customized to them. Etc.

Microsoft has been good about enabling a robust partner ecosystem to extend its products. The question will be whether it can allow its customers, non-customers, and non-partners to do the same. I don’t think it can, and I think that matters.

Better, but not necessarily cheaper

Friday, October 6th, 2006

Slashdot carried a story earlier today entitled “Why Is Commercial OSS So Expensive?” He was referring to embedded software, and his experience is 100% contrary to my own experience. (My background is in open source embedded software.) He says:

Our startup honestly wanted to use OSS products. We do not want to spend time for any OSS bug fixing so our main requirement was -official support for all OSS products-. We thought were prepared to pay the price for OSS products, but then we got a price sticker shock….After all, we have decided that the survival of our business is more important for us then ‘do-good’ ideas. Except for that embedded Linux (slated for WinCE or VxWorks substitution), we are not OSS shop anymore.

Taking the author at his word - that commercial open source is, in fact, expensive (has he tried the alternatives?) - I think he’s asking the wrong question. Given that in his world the open source alternatives are actually better than their proprietary counterparts, his question really should be, “Why isn’t it more expensive?”

It surprises me that some people persist in wanting something for nothing, or next to nothing. Open source is about a superior software development and distribution methodology. It really has nothing to do with cost.

Today, it’s much cheaper. SugarCRM? A fraction of the cost of Salesforce.com, Siebel, etc. MySQL? Pennies on the Oracle dollar.

But maybe not forever. If in five years MySQL ends up being more expensive than Oracle (not sure how Marten and crew could find ways to jack up the price that much, but let’s assume he’s very creative :-) , it won’t be for any other reason than the market will bear that price. And why would the market bear such price inflation?

Because it’s better software.

So, to the author of the article above, let me suggest that his projected switch to VxWorks or WinCE may get him exactly what he pays for:

Less.