Today's cloud-computing vendors focus on infrastructure, but that won't be the case for long. It can't be. As competing vendors seek to differentiate themselves, they're going to move "up the stack" into applications.
It's like the history of enterprise computing, played out in months and years instead of decades.
Just give me my !%!%! apps, already!
Oracle arguably set this strategy in motion when it acquired its way to a complete infrastructure-plus-applications portfolio to lower customer acquisition costs and improve its competitive differentiation for CIOs. IBM and Microsoft also went that route, though to differing degrees and in different ways.
Cloud-computing platform vendors are going to have to do the same thing, except they don't have the luxury of waiting.
It's not enough for cloud vendors to build the infrastructure and pray, "Field of Dreams" style, that customers will come. They won't. Not without applications and a host of other issues worked out for them, not by them.
Even Google, born in the cloud, recognizes this. Instead of forcing government customers into its public cloud, the company is building a dedicated cloud for government organizations in the U.S. Google's reasoning?
We also want to do our part to make it easier for government to transition to cloud computing. We recognize that government agencies have unique regulatory and compliance requirements for IT systems, and cloud computing is no exception. So we've invested a lot of time in understanding government's needs and how they relate to cloud computing. To help meet those requirements we're taking two important steps....
One step is certification, and the other is dedicated hosting. As much as Google may hope that its other prospective Google Apps customers won't have "unique...requirements," they do (or think they do). it's a losing battle to tell them otherwise, at least in the short term. If an enterprise giant like GE demands a private cloud, GE is going to get it.
This same pragmatism will drive Google and other cloud-infrastructure providers to build out their application suites. Why? Because enterprises that move to the cloud expect to see applications follow them there. Today, however, most enterprise applications don't work well in the cloud, leaving would-be enterprises buyers all dressed up with nowhere to go, in terms of the ability to run desired applications.
Vendors are jockeying to satisfy this demand for cloud-based applications. Google is already well on its way with Gmail and the rest of its Apps, and has been in the market lately for more, but others like Cisco, Microsoft, VMware, and IBM will be jumping into the M&A market to round out their offerings in order to deliver increasingly full application suites.
Microsoft has been actively courting developers to build cloud-ready applications for its Azure platform, while VMware bought into the Spring developer community for the same purpose. But in the winner-takes-most cloud platform war, the best short-term strategy is to provide applications, and not simply hope they get built.
Perhaps this is one reason IBM CEO Sam Palmisano claims to be undisturbed by Google's rise. IBM already has Lotus and more running in the cloud, and has a strong hold on enterprise wallets.
Some, like Red Hat or Amazon, may elect to sit it out and stick to their infrastructure-only guns, but such vows of paucity won't help potential service provider customers, and threaten to position them out of the longer-term battle for enterprise customers. Amazon can afford to refrain from seeking enterprise customers; Red Hat can't.
Microsoft is arguably best positioned in such a battle, at least from a portfolio perspective. After all, it has the applications--e.g., Exchange/Outlook, SharePoint, Office--that enterprises already use. What it doesn't have, at least, not yet, is experience running these applications in significant cloud deployments. But that will come.
Until it does, expect the big cloud-infrastructure vendors to buy competitive application offerings so as to distinguish their platforms to hosting and service providers. Sure, they can sell hosted Exchange, but that's a recipe for entrenching Microsoft in the cloud, just as happened on the "desktop" and server. Cisco et al. don't have much appetite for reliving Microsoft's glory.
Who are the likely targets? Zoho just became belle of the ball, of course, but there are others. I'd expect any application with either a significant following, like Acquia's Drupal, or significant cloud/hosting experience, like SugarCRM (Disclosure: I am an adviser to SugarCRM), to be up for grabs.
Follow me on Twitter @mjasay.
Open source has long been an important development methodology. The biggest surprise of 2009, however, was just how quickly it took center stage as a business strategy in the larger software economy.
The secret is out: open source is big business.
It's not as if open source as a business strategy is anything new. After all, the industry has been chattering about the business benefits of open source for nearly 10 years.
But not on Google scale. And not with the cachet and brand of Google blessing the idea. Despite the impressive sales and profits that Red Hat and other traditional open-source companies consistently deliver, the industry needed Google to take open source out of the realm of geekdom and into the boardroom.
Even Google needed Google. The Mountain View software and advertising giant has been involved with open source for years, running its Summer of Code and hiring up the best and brightest open-source developers, like Guido van Rossum and Greg Stein.
In 2008, however, Google stopped treating open source like a cute science project and source of cheap raw materials to power its search business, and instead started to actively court developers.
Open source stopped being a sideshow for Google and instead became the main event.
The developers were needed to create a groundswell of support for Google products like Android, and to dismantle the house that Bill Gates and Steve Ballmer built.
It's working. In fact, I suspect it's working far better than even Google suspected it would. It's certainly working at a scale that I never imagined we'd see in 2009.
All of which makes me think that 2010 will be the year that the rest of the industry follows Google's lead and starts to use open source as a fundamental business strategy, and not simply a plaything to placate "the community."
So, instead of Microsoft experimenting with fringe products like its open-source CMS Oxite, perhaps we'll see Microsoft open source an ad server (or acquire OpenX?) in an attempt to open-source Google's core, just as Google has been opening up Android, Chrome OS, and other products that undermine Microsoft's profit centers.
Perhaps we'll see SAP open-source software that kidney punches Oracle, while Oracle finally gets its way with MySQL and uses it to sucker-punch Microsoft's SQL Server.
And so on.
The big surprise of 2009 was how open source stepped up its game to become Google's primary business strategy, and not simply a sideshow developer strategy. The big news of 2010 will be how quickly other technology vendors will follow its lead, making 2010 the year of mountains of new, open-source code...and a hugely entertaining spectacle.
Can you find the openness in Google Search?
Google is perhaps the world's largest open-source company. That does not, however, make it the most open. Not even if Google says it's so.
The company is fond of believing itself different. And perhaps it is. For all of its stumbles over privacy concerns, it's still the company that insists it will "not be evil." I give its executives the benefit of the doubt that it really does want to be open, as revealed in a blog published Monday by Senior Vice President Jonathan Rosenberg.
But the irony of Google's position is that it's very open...until it needs to make a buck. Or a billion of them. At that point it's just as closed as its competitors. Perhaps more so.
Rosenberg doesn't shy away from the inconsistency, arguing that Google is closed when it's for its customers' own good:
While we are committed to opening the code for our developer tools, not all Google products are open source. Our goal is to keep the Internet open, which promotes choice and competition and keeps users and developers from getting locked in. In many cases, most notably our search and ads products, opening up the code would not contribute to these goals and would actually hurt users. The search and advertising markets are already highly competitive with very low switching costs, so users and advertisers already have plenty of choice and are not locked in. Not to mention the fact that opening up these systems would allow people to "game" our algorithms to manipulate search and ads quality rankings, reducing our quality for everyone.
Am I the only one that just had Napoleon of "Animal Farm" flash through their minds while reading that statement? Some animals are more equal than others, and some companies know better than others when to keep code closed.
It's not that Rosenberg is wrong. It's just that his embarrassment at admitting Google likes the revenue that results from closed systems ties his arguments up in knots, as Gartner's Brian Prentice highlights:
I don't think Rosenberg is making any attempt to mislead. I think he's thinking out loud and trying to reconcile the paradox he's created for himself--that open systems win even though Google's success is so clearly the result of being strategically closed.
Prentice adds further color:
The truth is that closed systems still win. Open systems, practically speaking, are basically good for making others lose.
The art of business in the 21st century is figuring out how to open up your suppliers' and competitors' business while keeping yours tightly sealed. And in that endeavor Google has proven highly successful.
From Red Hat to Facebook, from Google to Microsoft, from MySQL to Oracle, the same lesson applies: openness is exceptional for creating developer interest, lead generation, and many other things, but some element of proprietary still pays the bills. The big ones, anyway.
No exceptions.
Google is a fantastic company that groks the strategic benefits of openness better than most, and certainly better than its lumbering counterpart in Redmond.
But it's not exceptional in understanding open on-ramps and closed exits. Other important businesses like IBM have been leveraging such principles for years (even before Hewlett-Packard's Martin Fink explained the strategy in "The Business and Economics of Linux and Open Source").
Google isn't original with the business strategy. It's just better at it than most. It's open...until closed takes over to pay the bills.
Follow me on Twitter @mjasay.
Microsoft is in significant disarray, fettered by its destkop dominance as the world goes mobile. Would this have happened anyway, or is Microsoft CEO Steve Ballmer to blame?
Developers! Developers. Developers? Developers!?!?
Ballmer, after all, knows how to sing to developers, but he doesn't really speak their language. Former Microsoft CEO and co-founder Bill Gates did. Now, more than ever, Microsoft needs to get in front of developers but finds itself playing catch-up.
Gates announced his resignation back in 2006 and formally discarded his full-time Microsoft duties in 2008. But it has been a long time since Gates' hand was full time on the steering wheel.
That's a problem for the world's largest software company. It was Gates who saw the threat (and opportunity) the Internet posed for Microsoft--drafting his excellent "The Internet Tidal Wave" (PDF) memo in 1995--and alerting his troops to an array of threats that saved Microsoft from ruin...while helping it to ruin many others on its path to billions in profits.
Gates oversaw Microsoft's early, largely successful forays onto the Web. Ballmer has shepherded Microsoft to vanishing mobile market share (now just 7.9 percent of the market), a hesitant tiptoe into software as a service, and a general sense of retreat in emerging markets.
Hence, while former Microsoftie Don Dodge talks up his new employer, Google, with its food perks and 401(k), it's really the company's vision that has him jazzed:
Google has made three big bets on the future of computing; Chrome (browser), Google Apps (cloud), and Android (mobile). The trends are pretty clear. All the exciting new applications are running in the browser, with application code in the cloud, and the cell phone as the platform....2010 will be the year that enterprises of all sizes start their transition to Gmail and Google Apps, and take their first steps towards the vision of the future.
Dodge couldn't sell this sort of vision at Microsoft.
Microsoft has been playing catch-up for many years, but at least did so successfully under Gates. With Ballmer, there's a sense that Microsoft is always a half-decade too late on critical initiatives like search, open source, and mobile.
So is the problem Ballmer, or is Microsoft simply doomed, blinded by its own success with personal computers--a blindness that no CEO could overcome?
I hate to ascribe so much importance to any one person, but just as Steve Jobs is the soul of Apple and its revolutionary leader, so, too, was Gates the heart and mind of Microsoft. He understood developers, and they rewarded his belief in them by making Microsoft the world's largest software company.
Microsoft is the poorer for Gates' departure.
Even as I type this, Google keeps moving into the future while gouging Microsoft's past. TechCrunch is reporting that Google is acquiring DocVerse, which enables people to collaborate on Microsoft's Office documents. Microsoft is under siege.
This is just the beginning.
Developers are coding for Google projects, Twitter, and other new-style Web applications. Morgan Stanley is predicting the mobile market will be twice the size of the "desktop" market. Will Google someday dwarf Microsoft in size and influence?
Unless Ballmer can discover his recessive developer gene, the answer my well be yes.
Update at 2:10 AM Pacific on Tuesday: Newsweek predicts the ouster of Ballmer in 2010, but ZDNet's Mary Jo Foley cautions "not so fast."
Follow me on Twitter @mjasay.
Once a monopolist, always a monopolist? Not in Microsoft's case. While no one will accuse Microsoft of being a forlorn Tiny Tim, it's also no longer the Ebeneezer Scrooge that it once was. In fact, Microsoft seems haunted by the ghost of monopolies past, to the point that it has lost its ability to fight on equal terms for new markets.
Look at the markets the U.S. government sought to open by suing Microsoft for monopolistic practices. Microsoft's market share in media players, Windows, etc. remains largely unaffected by the government lawsuits.
I miss the smell of monopoly in the morning
Where Microsoft has lost market share (as in Web browsers and mobile), the competition hasn't relied on consent decrees and the like to win. Firefox wins because of its community development and distribution. Apple's iPhone and Google Android are trouncing Windows Mobile because they significantly change the rules of engagement for mobile while providing a better experience.
Government, in other words, probably solved little. But what it did was create a culture of caution within Microsoft that stultifies its ability and desire to compete. (We should note that just today, the European Commission formally ended its browser-focused antitrust pursuit of Microsoft, following concessions by Redmond.)
Microsoft's competitors, like Google, thrive in the wake of this fear, uncertainty, and doubt that plagues Microsoft. Ironically, competitors like Google do many of the same things that got Microsoft into hot water with the U.S. Justice Department.
Google et al. are free to compete. Microsoft is not.
Granted, this constricted freedom may be more psychological than real. As a journalist friend said to me on Tuesday, "Everybody thought Microsoft laughed off the antitrust thing. But I think it really did take the wind out of their competitive sails."
I do, too. In fact, a few years ago a friend and I set out to start a business delivering Microsoft Office-like functionality to mobile phones, which we ultimately abandoned. We didn't worry about Microsoft suing us for patent or copyright infringement. My friend had successfully sued Microsoft for anticompetitive practices in the Caldera litigation. We knew Microsoft's hands were tied by its antitrust settlement.
Microsoft is not the same company it once was. It's under siege, and seemingly incapable of responding. I think we're the poorer for it.
No, this isn't a paean to Microsoft monopolies. Rather, it's a plea for a Microsoft that competes vigorously to win.
Not one that repents in sackcloth and ashes for the "sin" of competing with open source. Not one that is continuously constrained by various antitrust authorities even as it erodes market share for the products in question.
I don't want a monopoly. I understand the important competitive principles that Mozilla and others are fighting for in the ongoing browser/etc. wars.
But I want a competitor again. Microsoft has lost its fight. This should concern us.
It should bother us because companies like Google need to be kept on their toes. It should nag at us because Microsoft writes great software that is comparatively easy to use, and we need its influence on the market.
I hardly use Microsoft software, preferring Apple and Google and open source. But I'd still like Microsoft's influence on the market, and not as a milquetoast competitor too afraid of antitrust shadows to thrash a competitor. Man up, Microsoft.
This post was updated at 2:30 p.m. PST in light of Microsoft's apology, which confirmed the anti-Drupal ads.
Microsoft has launched an advertising campaign against Drupal, an open-source Web publishing system, to promote its WebsiteSpark program. Some will see this as a devious plot on Microsoft's part to crush open source beneath its monopolistic feet.
But here's a more rational explanation: Microsoft competes with Drupal. This is what competitors do: compete.
Here's what Microsoft is accused of doing:
The other day I was checking Listology.com for the Drupal website list. But what attracted me more on the page was the small Google adsense block with the title "Forget Drupal and get:"...
Oops, here is an advertisement against drupal on a very page that lists all drupal websites. But the biggest surprise was that the advertisement was from none other than Microsoft. Clicking the advertisement takes you directly to the page of Microsoft's new product - Webspark, on Microsoft.com.
The horror! The horror!
Microsoft's WebsiteSpark program is designed to make it easy for Web developers to work with Microsoft technologies like .Net. It's hard to find anything nefarious in this, but some see Microsoft's alleged attempts to steer Drupal developers to WebsiteSpark as evidence that Microsoft is more worried about Drupal than it is Google, since it's using Google AdWords to place the ads.
As for Microsoft, no sooner had the community reared its incensed head than Microsoft's Mark Brown dashed out an apology:
I want to offer my sincerest apology for this. I have contacted Google and we are working on having this ad pulled as soon as possible. In addition we are working internally to ensure this doesn't happen again.
Really? For what? Having a business? For competing in the same way the Drupal community does?
This is silly. Microsoft is simply using the advertising channel open to it on the Listology Web site, trying to nudge developers its way. Acquia, the company set up by Drupal's founder to commercialize Drupal adoption, is doing the same thing.
Both are simply advertising where they hope to have a significant return on advertising dollars spent. It's called business. It's not personal.
It's the very same reason that Acquia advertises on Joomla.org, a competing open-source Web publishing system, as Joomla leader Elin Waring notes.
Take off the hair shirt, Microsoft. It doesn't become you.
After all, Microsoft is also promoting Drupal in Google searches:
A Jekyll and Hyde moment for Microsoft? Not really. The Web Platform team, of which Mark Brown is part, undoubtedly wants Drupal developers building on Windows.
But guess what? The WebsiteSpark team wants such developers building on Microsoft's Web technologies. It's a big company with different teams and different priorities.
In other words, it's nothing about which to be concerned. In fact, I'd worry more if Microsoft were doing the kumbaya thing with every open-source project, forgetting its fiduciary duty to compete vigorously...including against open-source competitors.
There is no free lunch with open source and there is no free pass for open source. We're grown-up boys and girls. We can compete. As for you, Microsoft, stop pandering to the hurt feelings of open-source developers who should know better.
Activists worry about the environmental cost of discarded mobile phones, personal computers, and other technology. Perhaps they should also worry about the swelling graveyard of start-ups and tech titans gone bad.
As Le Monde points out (in French), though businesses fail in all areas of the economy, technology ventures, and especially Web start-ups, prove particularly short-lived.
It's Joseph Schumpeter's creative destruction...in overdrive.
Le Monde suggests three reasons: the speed of innovation/evolution (AOL's walled-garden approach meets Yahoo's open-portal approach), the ability of incumbents to crush nascent competitors (Netscape meets Internet Explorer), and the shortcomings of business models (Skype: only $500 million out of more than 520 million subscribers).
These are good points, but perhaps there's another: technology companies are increasingly disposable because they're so darn cheap to create.
This affects start-ups and incumbents alike. For the latter, perhaps the negligible cost of starting a new company fosters the comparative disposability of such start-ups. As Bernard Dalle, a general partner with Index Ventures in London, notes, start-ups need only rent essential infrastructure like hardware and software, and that rent is dirt cheap.
Ideas that couldn't survive a $5 million to $10 million capital-raising process might well weather a friends-and-family round of $50,000...and expire shortly thereafter when the idea proves barren.
But it's also true of the incumbents: Gulliver-esque Microsofts can fight off most of the Lilliputians, but an increasing array of the pesky imps sprout into adulthood (e.g., Google, Salesforce, Facebook).
Unfortunately (or fortunately, depending on your market position), this process of creative destruction may well be accelerating, and open source is one of the primary fuels.
The Linux Foundation's Jim Zemlin insists that the pace and price of innovation today requires open source, a communal effort that isn't bogged down by the bureaucracy or cash constraints of any one company. He may be right.
That certainly seems to be one lesson to take from the success of Linux, Firefox, and other open-source projects, particularly those that are community-led, as opposed to company-led. It's hard to compete with a group of self-selected, highly focused developers who can focus on good code, not good financial quarters.
Now that virtually every technology company depends upon and contributes to open-source software, we may well be laying the foundation for even more industry innovation...and corporate bankruptcies.
Guess what? There's nothing we can do about it. Nor is there anything we should do about it, except focus on building long-term customer value rather than short-term start-up goofiness. That's the way to thrive in the fast-evolving world of technology, because it's the one thing that never changes:
Customers pay for value, and companies that consistently deliver real value acquire the most customers.
Tim O'Reilly points toward this in his call for developers to "work on stuff that matters." It's a reminder but also a warning.
Microsoft is still with us because it has delivered an amazing amount of customer value in its 30-plus years. The same is true of IBM, Oracle, SAP, and other industry incumbents.
But it's equally true of relatively new companies like Salesforce, Red Hat, and Google, which have eschewed gimmicky software and flimsy business strategies to give customers tangible, ongoing value. None of these companies sought an early exit through acquisition. None of them were content to build for the quick flip.
So, yes, technology may be a veritable boneyard of failed companies, and essential ingredients like open source may accelerate the demise of start-ups and incumbents alike. But those companies that use such ingredients to deliver above-average customer value are going to endure...and thrive.
Follow me on Twitter @mjasay.
Open source, like digital media, doesn't suck money out of hitherto profitable industries. Instead, the opening up of software and information simply changes where the money gets made.
This is obvious to the Googles of the world. It's probably equally obvious to the Microsofts of the world. The difference is that the latter can see the train coming but is powerless to stop it, and the former is driving the train.
The evidence for this is increasingly clear and is driven by a shift in how content is sold and consumed. The problem is neatly summarized by Google CEO Eric Schmidt in a Wall Street Journal op-ed piece directed at the newspaper industry:
[T]he Internet has broken down the entire news package with articles read individually, reached from a blog or search engine, and abandoned if there is no good reason to hang around once the story is finished. It's what we have come to call internally the atomic unit of consumption.
That newspaper was "the package," but is increasingly too slow and out-of-sync with how people prefer to discover news content. New packaging is rising, including Google News, that will shift who makes money on news content.
Reporters will still get paid. They'll just have a new employer on their payroll check. Maybe it will be Google.

Think about what is happening in music. I could download New Order's "Regret" for free using LimeWire, but I bought it on iTunes because of the "packaging" which makes my experience easy, high-quality, and legal.
Still, the primary drivers are ease and quality.
Such packaging is worth a lot of money--and to an entirely new breed of vendor--as a quick look at Google's latest income statement suggests.
It's happening in software, too, particularly in open-source software. Red Hat is an example of a company that does a great job of turning software license into an ongoing service contract that enterprises buy. It does this by packaging the power of others' development in the form of a subscription, as Red Hat CEO Jim Whitehurst recently highlighted.
But Red Hat is just Open Source 1.5. Open Source 2.0 looks more like Google or IBM. For every dollar Red Hat makes selling subscriptions to use open-source software like Linux and JBoss, both Google and IBM make multiples of that dollar using open-source software to sell something else, something they've packaged in hardware or Web-based services.
The hardware is running open source. The services are based on open source. The money is made in the packaging of open source.
... Read moreIn the past week, the open-source business community appears to have reached consensus: making money from open-source software is a bad model, but making money with open source is golden.
This can't be good for Microsoft.
Microsoft has long maintained that as the open-source industry has matured, it has become more and more like the commercial world it sought to leave behind. Fundamental freedoms of open source, like the right to modify source code, are signed away to secure a support contract with Red Hat or another vendor.
In many ways, Microsoft was right. Unfortunately for the Redmond giant, however, the new consensus should lead to less commercialization of open source, and more commercialization around open source. There's a big difference, and it's one that threatens to seriously undermine Microsoft and every other traditional software vendor.
That is, unless Microsoft responds in kind.
The new consensus
This consensus has been articulated by TechDirt, Redmonk's Stephen O'Grady, GigaOm, and here on The Open Road.
In fact, it's a drum I've been beating for over a year as Tim O'Reilly's wisdom on the topic finally caught up with my 33MHz brain.
There are fundamental, strategic benefits to open source: ease of distribution, friction-less adoption, costs, etc. There are also serious downsides when it comes to selling it: people chafe at paying for something if they can get it, or something similar to it, for free.
Such problems don't plague companies like Google, which distributes open-source software to drive more adoption of its proprietary advertising or SaaS services. Even Red Hat isn't really in the software business: not with its Linux distribution, anyway. It's in the business of providing certification and update services; of managing the complexity of an operating system.
It's a great business, but if you had to choose between Google's sales or Red Hat's, it's a no-brainer.
Microsoft's response
As this lightbulb goes on across the industry, companies like Microsoft, which insist on direct monetization of software, with little in the way of open-source complements to fuel adoption (or simply undermine competitors), are going to struggle. More and more companies will give away Microsoft's core business as open-source complements to their own.
So, here's a suggestion for Microsoft as just one good way to respond: open-source Internet Explorer.
Fight Firefox with fire
Cut Google's Chrome and Chrome OS off at the knees. Undermine Mozilla Firefox's raison d'etre. Give the European Commission a reason to love you.
More importantly, give developers something to embrace and extend. Microsoft has been steadily losing browser market share as Firefox eats into it. In some countries, like Germany, Firefox has even surpassed IE's market share.
Fight fire with fire. IE is still the world's most popular browser. Make it the world's most open browser, too.
Every Microsoft business could benefit from this move. Even if one assumes that Microsoft isn't ready to take the plunge and fully open up the development process around IE, here's some comfort: neither has Google around Chrome. Microsoft can still steer the IE ship, even if it were open source.
Microsoft needs a proactive open-source strategy, rather than the reactive policy it has had to date. Open source is a threat, yes, but it's a threat to everyone, especially as the industry collectively comes to grips with open source as a business enabler, rather than as a product to sell.
If Microsoft wants to win big in the new world of Web-based software, it needs a bold strategy. Open-sourcing IE is the starting point.
Follow me on Twitter @mjasay.
If something seems too good to be true, it probably is. That popular aphorism never seemed truer than today when reading The Wall Street Journal's analysis of Wikipedia's declining volunteer base. Despite countless articles extolling the virtues and seeming omnipotence of "community" over the past several years, the technology industry seems to be settling back into old habits:
Command and control.
It's not that the "wisdom of crowds" idea hasn't influenced the way technology is developed, or how news and information are gathered and distributed. It has.
It's just that the promised sea change has proved to be far less disruptive than we expected.
Take Wikipedia. As the Journal calls out, volunteerism has declined as the ease of contribution has waned. The easy topics are taken. Rules for upping the quality have proliferated. Wikipedia is becoming...corporate.
Nick Carr has been pointing this out for years, but it's only now becoming self-evident. Wikipedia has grown up and, in so doing, is looking more and more like the encyclopedic world it sought to displace.
Nor is it alone. Open-source business models increasingly look like proprietary software models, as the Software Freedom Law Center's Bradley Kuhn suggests.
Even uber successful open-source communities like Joomla have discovered that reliance on volunteers falls short of what a few good paid developers can do.
That's a positive discovery by Joomla. A more worrisome discovery is that Mozilla remains far too dependent on Google to fund development of Firefox. Mozilla has lots of community, right? Yes. As Mozilla CEO John Lilly has said, 40 percent of Firefox's code comes from developers not employed by the foundation.
But that still leaves 60 percent, and virtually all of the core development work, that relies on "company," not "community," which is how much of the world's best open-source software is developed: funded by IBM and other "community" members.
For those who think "community" is a euphemism for "everyone else doing my work for me," think again. It just doesn't work that way.
Of course, companies can go to the opposite extreme, too. Apple, for one, gets beat up for a heavy-handed approach to its App Store approval process. Apple, in other words, doesn't seem to care one iota what "the community" thinks.
But then, this is the same App Store with more than 100,000 applications and 2 billion downloads to date. No wonder Apple isn't apologizing: it's clearly benefiting most people most of the time, or the application developers would take their complaints to a different platform.
But they haven't, and this calls out the problem with deifying "community." It's accepted wisdom that one shouldn't "anger the community," as if it's some unknown god that demands the occasional virgin to be thrown into the volcano. But the truth is, "community" is not really much different from the "customers" and "partners" the industry has sought to satisfy for decades.
So, yes, by all means seek to work with your community of users and partners, but don't expect "the community" to do your work for you. Guess what? "The community" already has a day job, and can't afford to work full-time for you unless you pay it.
All of which leaves us largely where we started. The most successful software companies don't rely on some vague "community" to build their products. Microsoft, Oracle, IBM, Google (Android, anyone?), and even, increasingly, Red Hat (JBoss, KVM, etc.) build great software based on their own, internal plans and expertise and "the community" buys it (or resells/embeds/etc. it).
The big shift, however, has been in the transparency of the feedback loop, which has been a welcome change in the industry. So, to the extent that "community" simply implies a more open way of developing and distributing software, then, yes, it has been significant.
But it hasn't changed the world. It has only changed the way the dominant technology companies...dominate.





