★ OpenSolaris Governing Board Resigns

I’m very sad to report that, as expected, it proved necessary for the OpenSolaris Governing Board to collectively resign today. The motion was as follows:

OpenSolaris

Motion concerning dissolution of the OGB

Whereas Oracle has continued to ignore requests to appoint a liaison to work with the OGB concerning the future of OpenSolaris development and our community, and
Whereas Oracle distributed an email to its employees on Aug 13 2010 that set forth Oracle’s decision to unilaterally terminate the development partnership between Oracle and the OpenSolaris Community, and
Whereas, without the continued support and participation of Oracle in the open development of OpenSolaris, the OGB and the community Sun/Oracle created to support the open Solaris development partnership have no meaning, and
Whereas the desire and enthusiasm for continuing open development of the OpenSolaris code base has clearly passed out of Oracle’s (and thus this community’s) hands into other communities,

Be it Resolved that the OpenSolaris Governing Board hereby collectively resigns, noting that under the terms of the OpenSolaris Charter section 1.1 (and Constitution 1.3.5) the responsibility to appoint an OGB passes to Oracle.

The motion passed unopposed.

As I said in the meeting, huge thanks are due key members of the OpenSolaris team at Sun who have stuck with the project despite an enormous change of context. I would like to specially recognise Alan Coopersmith and Jim Grisanzio for their wisdom and patience.

★ Open Source Trade Associations Lack Sanctions

Software patents are broken and the only possible justification for having them is self-defence (which is itself a risky accumulation of armaments that can easily fall into the wrong hands). It seems plenty of important members of both the Linux Foundation and the Open Invention Network make public assertions claiming they believe that, so there should surely be no objection to equipping both of these trade associations with firm, meaningful sanctions.

Read on over at ComputerWorldUK.

★ The King Is Dead, Long Live The King

I wrote last week about the end of the “open source bubble”:

“The anomaly is not that projects like Hadoop or OpenStack lack a company ‘monetising’ them – it’s that we believe open source projects ought to have such a company. The past decade has been something of an ‘open source bubble’, with many people believing there is a fortune to be made if only they can find the right business model to pack around open source.”

Matthew Aslett of The 451 followed up with a blog post that describes what I called “the open source bubble” as open source 3.0. He agrees it’s ceding prominence in favour of what he calls “open source 4.0” or corporate-dominated (but not controlled) collaborative development communities.

He notes he’s adjusting his predictions in the light of the changed environment for corporate engagement in open source. For example, NASA is collaborating in the OpenStack cloud computing project, and Adobe’s purchase of Day Software gives them an important involvement in the Apache Software Foundations without any direct control.

Aslett describes this as the coming “golden age of open source” and it certainly reflects the reality I am observing at the leading edge of open source activity. As Thomas Prowse comments this does not mean the demise of the model where a single company attempts to use open source as a vehicle for its aspirations. Nor does it necessarily harm existing activities.

But I would argue that new attempts to do this need careful scrutiny, and I expect to see very few of them. Attempts to control and constrain an open source community will more and more been seen as a failure to embrace the ‘open source way’ and the network effects is creates. Where new businesses do arise, I expect to see them using elements from the collaborative community model to ensure that their engagement involves influence and not attempts at control.

This return to the core engagement in co-development in transparent communities is very welcome. Software freedom matters, and this approach leverages rather challenges it. So the bubble is over, and open source will live on stronger than ever – “the King is dead, long live the King”.

[First published on ComputerWorldUK]

✭ Will Illumos Bring OpenSolaris Back To Life?

Illumos tape graphic

Today sees the launch of the Illumos Project, heralded last week in a message on the OpenSolaris mailing lists. The announcement caused much excitement, with many assuming it was a fork of OpenSolaris or another OpenSolaris distribution.

Illumos is neither. It is in fact a project to create a fully open-source-licensed version of the Solaris operating system and networking consolidation – the closest Solaris comes to a “kernel project”. It’s a downstream open source project, happy to contribute upstream but resolutely independent. As such it is a thoroughly good thing and a breath of fresh air.

It’s a good thing because it unblocks the potential of the OpenSolaris community to have a fully open source free software commons at its heart and creates the possibility of a new operating system that carries forward the legacy of UNIX yet is fully independent. The founders have already worked hard to create a bootable version of ON, including rewrites of closed portions of libc and the most critical utilities and drivers. Now the project is launched, they are looking for participants who will work on the lock manager, crypto, labeld and on remaining drivers. As I’ve written before, open, multi-party communities are the key to the future of open source.

It’s a breath of fresh air because after half a year of stonewalling and silence from Oracle from everyone in a position to carry OpenSolaris forward, the conversation in the community had spiraled lower and lower from concern to conjecture to complaint and finally beyond into ad hominem. Indeed, project founder Garrett D’Amore told me he played it quietly up until now as there was too much complaining and not enough getting-things-done. He wanted there to be actual code available on opening day and not just promises.

It’s clearly beyond just promises. As well as all the new code, the new project is supported by key OpenSolaris community vendors and members. Storage appliance vendors Nexenta – who employ Garrett – have their own OpenSolaris distribution along with a growing staff of former Sun engineers to support it, and have committed to using Illumos. Cloud hosting company Joyent – whose recent hire of DTrace co-inventor Bryan Cantrill (who has also written about Illumos) signals a positive engagement with the technology – use OpenSolaris in production. That support, along with the other positive support from respected Solaris and OpenSolaris leaders, means Illumos could well be the restart OpenSolaris needed, as long as its founders can deliver on the promise.

I’ve seen a project like this succeed before. When the OpenJDK project was announced to deliver an open source Java platform, members of the existing open source Classpath community were delighted but remained concerned Sun would not make a priority of getting the remaining closed portions replaced. The community started the IcedTea project, a fully Free downstream of OpenJDK, and offered to contribute everything upstream. It was that action that meant OpenJDK soon became a fully open source project with all Free software in it.

Illumos has similarly invited Oracle to participate or even just to accept upstream the rework done by the Illumos project. Time will tell whether Oracle responds positively or whether Illumos becomes the new, independent heart of the former OpenSolaris community. Either way, count me among its fans!

[First published on ComputerWorldUK]

✭ Is the “Open Source Bubble” Over?

I was pleased to be able to attend this year’s OSCON, O’Reilly Media’s open source convention held once again in Portland, Oregon in mid-July. There have been numerous reports about it, not least from the New York Times, but one that caught my eye was the meta-analysis from analyst Stephen O’Grady. O’Grady is characteristically detail-rich and his article is packed with Google Trends graphs, but this quote is key:

The business of selling open source software, remember, is dwarfed by the business of using open source software to produce and sell other services. And yet historically, most of the focus on open source software has accrued to those who sold it. Today, attention and traction is shifting to those who are not in the business of selling software, but rather share their assets via a variety of open source mechanisms.

If we look back to Eric Raymond’s seminal essay The Cathedral and The Bazaar, the model behind open source is clear; an open community gathered around a free software commons, with each participant “scratching their own itch”. But it’s clear we’ve forgotten this, to the point of delusional false conclusions based on partial insight. The enduring popularity of the false question “if you give it away free, how do you make money” shows that the echoes of the Cathedral model ring on long after we’ve realised that the Bazaar model is the one that works in the meshed era of the Internet.

Why is that? O’Grady seems to imply there’s novelty here:

The difference this time around is that by sharing the code developed internally as open source, it becomes possible to amortize the development costs across multiple organizations with similar needs.

But I believe that is a rediscovery, not an innovation. The anomaly is not that projects like Hadoop or OpenStack lack a company “monetising” them – it’s that we believe open source projects ought to have such a company. The past decade has been something of an “open source bubble”, with many people believing there is a fortune to be made if only they can find the right business model to pack around open source.

But that thinking has usually involved a compromise of one of the key qualities that make open source work. Usually it’s a desire for control or exclusivity in some form, but the outcome is always to progressively negate the “open source effect” in search of profit, by limiting the ability of every participant to get what they want and thus give what they can. While there’s clearly a niche for one or two expertly-balanced businesses, the propensity of commentators to focus on these colourful exceptions has created the perception this is the norm.

That anomalous decade is just about over. The new projects on the block are once again collaborative, seeded by companies whose business does not depend on selling the software or its direct derivatives. They involve synchronizing fragments of the interests of many, diverse participants rather than having the whole of a single party’s interests at their core. Every participant comes to them paying their own way rather than expecting the project to pay them.

They aren’t really new, either. They are a continuation of the quiet, enormous success of the Apache community and the GNOME community and their peers. This, not the commercial bubble, is the true open source way.

[First published in ComputerWorldUK]

☞ Evolutionary Pressures

  • Announcement – Illumos Project
    “A number of the community leaders from the OpenSolaris community have been working quietly together on a new effort called Illumos, and we’re just about ready to fully disclose our work to, and invite the general participation of, the general public.” (from the announcement on opensolaris-discuss)
  • Brazilian Government Signs OpenJDK Manifesto
    Concerned about Oracle’s approach to communities, the Brazilian Government has signed up to testing and using open source Java platforms (notably OpenJDK) instead of the proprietary one. (Linked page is in Portuguese – translation)

Ⓕ First Post!

Today is a significant milestone for the new venture I’m helping, ForgeRock. We’ve announced availability of our first full independent release of OpenAM, the open source authentication and access management system. If you look at the release, you’ll see it’s a significant update, with SAML2 support, fine-grained authentication controls and a host of other improvements.

It’s significant for open source because it signals that the OpenAM community – especially the part on ForgeRock’s own team – is up to speed maintaining and evolving the code and that the transition from its former home is going well. And it’s important to OpenSSO customers because it finally gives them a smooth upgrade path from the version 8 of Sun’s old OpenSSO product, which most of them are using.

My congratulations go out to the whole community for their work, but especially to the ForgeRock team who have been working flat out to make it happen – especially Steve, who really deserves a break! Great job, everyone!

✍ Did Open Core Trigger OpenStack?

At the end of the Community Leadership Summit here in Portland people arriving for OSCON started to show up. They included one of the guys behind Rackspace’s announcement of OpenStack that was made today. He gave me a full rundown of both the news and the history behind it. The history seems to suggest it was the open core business model that lead to the creation of OpenStack. Read more on ComputerWorldUK.

✭ On the term “open source business”

Hunter and HuntedI’ve been having a number of conversations in e-mail on the subject of open core business models. The problem that keeps coming up is that there are a range of behaviours exhibited, some of which are acceptable to pragmatists and some of which cross the line into abusing the term “open source”. Where should we draw the line in? When is it acceptable for a company to call itself “an open source business” and when is it not?

An example is a hypothetical  business with an open source “Community Edition” of their software product which lacks many features of the commercial versions. It is indeed freely available under an open source license and fully functional. I am sure there are happy deployers of this version. If this was the only version available, I would have no issues.

The commercial versions are significantly different from the community version, with both user interface differences and functional differences. While paid licensees are entitled to source access to this version, the commercial licence is not perpetual, meaning that if the customer ends their relationship with the vendor, they lose the right to use this version. Since this version significantly differs from the community version, there is no fall-back plan and while the customer may have access to their data (if the vendor is sufficiently enlightened about open data), there’s no software they can continue to use. They are unable to trade “time” for “money”, to use Mårten Mickos’ famous explanation – they are locked in and the open source core of the proprietary version delivers no freedom to them.

If this latter situation was described as “proprietary” (or avoided association with open source, as for example IBM’s WebSphere does in its embedding of Apache HTTPD) I would have no issues either.

The fact is, the community edition and the commercial editions have disjoint user bases. The community edition is used by a group of people who have the time and skills to deploy by themselves and who have no need of the many differences of the commercial versions. The commercial versions are feature-rich and effectively lock their users into a traditional commercial ISV relationship with the vendor.  If these two were kept distinct, there would probably be no pragmatic issue (naturally Free Software purists would still protest the existence of closed code, but that’s not a part of this particular argument).

But a vendor which mixes these two encourages exactly the market confusion that OSI was designed to minimise. If they claim to be “an open source business” and use the presence of the community edition as a credential to sell the proprietary versions, they wrap themselves in the open source flag and their actions are exactly the gaming of the maturity of the Open Source Initiative that I believe should be challenged.

The question is how. As Matthew Aslett points out,

In short, if you want to police the term “open source company” then you have to have a definition for it first.

That’s true. Defining an “open source company” will be impossibly subjective, since most companies have open source in their source code mix these days. Given “open source” can only refer to software, I think is far smarter to discourage use of the term all together.

✍ OpenSolaris Governance

You may have seen some of the news reporting of the OpenSolaris Governing Board (OGB) meeting that was held last Monday (I am an elected member of the Board). At a meeting with an unusually large number of community observers, we discussed how to respond to the 100% radio silence the OGB has experienced from the new owners of the OpenSolaris copyright and infrastructure. I believe we reached a balanced and well-considered conclusion and remain hopeful of a good outcome.

Read about it on my ComputerWorld blog