Andrew from Blogging on the Free Web asks whether I discussed taking Groove open source with Ray Ozzie prior to the Microsoft acquisition. Unfortunately, one of the constraints of working in the proprietary world is the loss of liberty to be open about the details of business transactions (at least until I write my memoirs). Part of the joy of open source by the way is that it permits, if not virtually requires, a degree of transparency that is congruent with my approach to life and business.
What I can say is that I have consistently had substantive conversations over the past several years whenever the opportunity presented itself to discuss open source opportunities involving ALL of the companies I've made investments in and have at one time or another had board seats on. This includes Real Networks, Groove Networks, and Linden Lab (which makes Second Life, an increasingly popular virtual world).
There are advantages to going open source as well as challenges. In some cases it may even be necessary to forestall a competitive threat, i.e., do it before it is done to you. When I see businesses whose strategies involve defending a class of business model which is simply going to be obsolete going forward, my heart sinks about all the wasted effort.
Caveat altert: In a transitional era like the one we are in now, it is notable that it's harder to convert a code base developed in a proprietary context to be open source than it is to start from scratch for the same reason renovating a house completely is harder than new construction. Trust me if you haven't been through this. I have. This is one of the reasons it took seven years from the day Netscape announced it was going to open source the Mozilla browser to get to Firefox 1.0.
It typically requires a complete overhaul of the code and the development process, which is much harder than starting from scratch. Typically, the existing code base is not one which is amenable to community development. There is major code re-factoring and rewriting to be done, rethinking and reworking of API's, switching to open standards, and changing of the tool set to use transparent, community-oriented tools for source code management, issue and bug tracking, build status, knowledge base, and synchronous messaging.
On top of this, it requires investment to build a developer community and potentially much more investment to create a perception of trustworthiness.
Going the open source route ought to be considered but it is not always really viable given the resources at hand.Posted by firstname.lastname@example.org at March 11, 2005 03:13 PM