IBM's ex-Mr GNU/Linux Joins Obama Policy Group

Good news: Irving Wladawsky-Berger, the person who essentially steered IBM toward GNU/Linux - with huge knock-on effects - has joined one of that nice Mr Obama's policy groups:

Technology, Innovation & Government Reform

The Technology, Innovation & Government Reform Policy Working Group will help prepare the incoming Administration to implement the Innovation Agenda, which includes a range of proposals to create a 21st century government that is more open and effective; leverages technology to grow the economy, create jobs, and solve our country’s most pressing problems; respects the integrity of and renews our commitment to science; and catalyzes active citizenship and partnerships in shared governance with civil society institutions. The Working Group is organized into four sub-teams: (1) Innovation and Government, (2) Innovation and National Priorities, (3) Innovation and Science, and (4) Innovation and Civil Society.

As well as interviewing him for Rebel Code, where he graciously spent some time explaining things when he was a busy man, I also interviewed him for the Guardian. That piece provides a lot of hints at just how wide-ranging his interests are. (Via eightbar.)

The Olympian Apache

Here's a nice reminder that open source - in the form of Apache - has been head of the field for more than 12 years, despite what certain companies would have us believe:

In 1996 the World Wide Web was truly in its very early stages. The Olympics took place less than a year after Netscape went public, which many consider the key event marking the transition of the Internet from a research network used primarily by the technical community to the commercial behemoth that it went on to become.

The new World Wide Web had the feeling of magic, but, in 1996, it was pretty primitive magic. To begin with, the vast majority of people accessing the Web at the time were doing so over slow dial-up modems with bandwidths of 56 kilobits per second or less. Only at work, if you were lucky, did you have access to faster broadband speeds. It wasn't until years later that broadband usage in the home became commonplace.

As we were planning the IT infrastructure for the Olympics website, hardware was not an issue. We used IBM's SP family of parallel supercomputers which we were confident would provide us with all the computing power we could want.

But the software for web servers was quite immature. Netscape's web software was the most widely used in those days, and while it was adequate for small workloads, its scalability was suspect. We could not use it. Instead, we used the open source Apache Server as the basic web server, and custom built the extensions needed to support its content, applications and other capabilities.

We were pretty sure that the Atlanta Olympics website was the largest such web project anyone had undertaken so far. Because it was all so new, we did not know how many people would come to our website and what features they would use once they got there. We were well aware of the considerable risks inherent in doing such a complex, new project on such a global stage. We knew, for example, that beyond a certain number of users, the response time would start to degrade, and if sufficiently stressed beyond its capabilities, the system could become unstable and crash.

...

Our Olympics website worked quite well, except for some unduly slow response times when traffic got very heavy. Overall, the site handled 187 million hits – that is, individual pieces of information served to users. We learned a lot about the requirements for building and operating large, complex websites. All in all, it was a very successful experiment.

Virtual Worlds Get a Second Life with IBM

I was lucky enough to interview Irving Wladawsky-Berger for the Guardian shortly before he retired from IBM. One of the most intriguing hints of things to come concerned virtual worlds:

Does IBM have its own internal virtual world system - an intraworld running on its intranet?

We plan to build them; exactly how is all under discussion. We very much feel that many of our clients will want intraworlds in the same way they have intranets.

Then you want to make the navigation between the intraworlds and public worlds as seamless as possible.

Some of the "how" regarding interoperability is being addressed with this interesting collaboration between IBM and Linden Lab:

IBM and Linden Lab, creator of the virtual world Second Life (www.secondlife.com), today announced the intent to develop new technologies and methodologies based on open standards that will help advance the future of 3D virtual worlds.

...

IBM and Linden Lab plan to work together on issues concerning the integration of virtual worlds with the current Web; driving security-rich transactions of virtual goods and services; working with the industry to enable interoperability between various virtual worlds; and building more stability and high quality of service into virtual world platforms. These are expected to be key characteristics facing organizations which want to take advantage of virtual worlds for commerce, collaboration, education and other business applications.

What's striking about this announcement - still rather lacking in details, but clearly very good news for Linden Lab - is the emphasis on openness:

Open source development of interoperable formats and protocols. Open standards in this area are expected to allow virtual worlds to connect together so that users can cross from one world to another, just like they can go from one web page to another on the Internet today.

No surprise there, really - open standards are the only way to build resilient, heterogeneous systems. And if you're contemplating linking together myriad, disparate virtual worlds, it had better be resilient in the extreme. (Via Clickable Culture.)

Irving Wladawsky-Berger: And Another Thing

I interviewed Irving Wladawsky-Berger twice: once for Rebel Code, soon after IBM announced its support for GNU/Linux - arguably one of the key moments in the corporate acceptance of open source - and once for the Guardian, shortly before he retired from IBM. On both occasions he was a pleasure to talk to.

And now I find another reason to like the chap:

One of my favorite films is the 1956 science fiction classic Forbidden Planet.

Me too, me too.

IBM's Virtual Mainframe

It's been an open secret that IBM was working on its own virtual world platform, but details are now beginning to emerge:

IBM said its new "gameframe" system was being designed in collaboration with Hoplon Infotainment, a Brazilian game developer that is interested in creating a software layer it calls a "bitverse" to support virtual online worlds.

There are already massively multiplayer games that support hundreds of thousands of simultaneous players, but the IBM system will add an unparalleled level of realism to visual interactions, Meyerson said.

He argued that in addition to gaming applications, this kind of technology could be used to enhance the performance and scaleability of existing virtual worlds like Second Life, an Internet-based service that crosses the boundary between online entertainment and workplace collaboration.

Mark Wallace has more information.

Welcome the Real and Virtual 2007

I won't add to all the other prognostications for this year - not least because some people have already done it so well:

let me start the year by commenting on a key trend that I believe will similarly take off in 2007 and become more widely accepted in the marketplace as the year progresses. I believe that highly visual interfaces and virtual worlds will become increasingly important for interacting with applications, communicating with people and engaging in commerce, - what we in IBM have started to call v-business.

And Irving Wladawsky-Berger - for it is he - then goes on to explain why:

In IBM, as in many companies, we spend a lot of our day in conference calls with people all around the world. The choice is not whether to have those meetings in person - but how to make the meetings more effective, more human. As many have been discovering, virtual world meetings might be one of the ways of significantly improving the quality and feeling of meetings involving multiple people in remote locations.

He concludes with an important caveat:

In the end, the market acceptance of virtual worlds, - as that of any other technology-based trend, - depends on whether it brings real value to whatever it is people want to do and are willing to pay for.

Open Source, At Your Service

So far, the best answer to How can open source companies make money? seems to be that of providing services - typically training, support and general consultancy. There's another approach, involving dual licensing, but this is more problematic in some ways, and there's also evidence that it may only be a transitional approach on the way to a full service model.

Against this background, Irving Wladawsky-Berger has an interesting post on his blog about services, beginning with this observation:

If you look at IBM's business last year, services revenues were roughly 55%, while systems (hardware) and software revenues were around 25% and 20% respectively. But services constituted around one-third of the company's profit, for a very simple reason. Systems and software products leverage technology assets and apply engineering principles to improve quality, scale-up capacity, and achieve higher productivity and profit margins. Services, on the other hand, have historically been significantly more labor-based, less prone to economies of scale, subject to higher quality variations, and generally less productive and profitable.

Services - and analyses of them - will clearly be moving to the foreground in years to come, and not just in open source. The latter will, however, be a trailblazer in this respect as in many others. Another reason for those outside the world of free software to pay close attention to it.

Democratise Innovation: Put It Online

This isn't particularly new, but I've only just caught up with it (on Irving Wladawsky-Berger's blog). It's "Democratizing Innovation" by Eric Von Hippel, yet another book that draws inspiration from open source:

The trend toward democratized innovation can be seen in software and information products -- most notably in the free and open-source software movement -- but also in physical products. Von Hippel's many examples of user innovation in action range from surgical equipment to surfboards to software security features. He shows that product and service development is concentrated among "lead users," who are ahead on marketplace trends and whose innovations are often commercially attractive.

Nor have I read it, but the basic idea sounds good, and Von Hippel is generally very sound - as evidenced by the fact that he has made the book freely available online under a CC licence.

Closing off Microsoft's Patent Options

Patents are boring - but important. They are the chokepoint for much intellectual activity - especially the kind discussed in these pages - so anything that can be done to loosen their grip on the free interchange of ideas is welcome.

Against this background, the announcement by the US Patent and Trademark Office (USPTO) that it has "created a partnership with the open source community to ensure that patent examiners have access to all available prior art relating to software code during the patent examination process" is an encouraging step, since software patents are some of the most problematic of all (see Richard Stallman's brilliant explanation of why). However, this is a statement of intent, rather than a concrete move, and it remains to be seen what practical effect it will have on stemming the flood of trivial or downright bad patents being granted by the USPTO.

Meanwhile, the USPTO has upheld Microsoft's patent on the File Allocation Table (FAT) storage technology. This is bad news: it represents both a direct defeat for the open source world, which sought to overturn it, and a sword of Damocles that henceforth will hang over the entire free software movement. The danger is that Microsoft will demand royalties - maybe even "reasonable and non-discriminatory" ones - that will be impossible for free software projects that use the FAT technology to pay.

Update: On the other hand, maybe it's not over yet...(who said patents were boring?)

Update 2: For a view on the USPTO initiative from inside one of the companies helping to make it happen - IBM - see this excellent post by Irving Wladawsky-Berger. Anyone who's read my Rebel Code will know that he was the man who essentially turned Big Blue onto GNU/Linux. This means that he is someone with his finger on the pulse, and that his blog is well worth following.