(Or “the return of 451 CAOS Links“)

Having been a bit busy for the last three weeks I have a bit of catching up to do on the latest open source software news. Here’s the headlines that caught my eye.

MySQL co-founder resigns from Sun
No, not that one. David Axmark resigned stating “I HATE all the rules that I need to follow, and I also HATE breaking them. It would be far better for me to “retire” from employment and work with MySQL and Sun on a less formal basis.” If I may paraphrase Oscar Wilde, to lose one co-founder may be regarded as a misfortune; to lose both …

JasperSoft’s business development director Andrew Lampitt has kicked off his new blog with an interesting post related to business models used by open source-related vendors.

In it he attempts to define the approach utilized by the likes of JasperSoft and SugarCRM, which offer open source products with core functionality, as well as commercial extensions. The approach is a twist on the dual licensing approach made famous by MySQL* where the vendor, as copyright holder, makes the code available under both the GNU GPL and a commercial license for customers that would rather avoid the GPL.

The approach taken by JasperSoft et al is not to segment by user base but by features. As Andrew explains, “the commercial license is a super-set of the open source product, i.e., it offers premium product features that you will not see in …

A couple of articles have been published recently that point to a growing realisation/admission about the role that open source will play in the future of enterprise software.

In “The Commercial Bear Hug of Open Source” Dan Woods details the various methods by which open source has become increasingly commercial in recent years, while in “The Microsoft-Novell Deal and Trust in Princes” Bruce Byfield discusses the relationship between business and open source.

Neither article is perfect. Woods, in particular, appears to paint open source in the role of the glorious failure - failing to surpass traditional licensing models and being subsumed into the mainstream (a subject …

Lukas Kahwe Smith has an awesome post titled "Open Source is not making enough rich people richer" .
Indeed, there is much talk that the VC's , the Investors and different others aren't seeing the big money fast enough, according to them that is.
Does that mean that the open source industry is going bad ? Does that mean you can't make a living when working in the Open Source industry ?

Absolutely not, as he points out there are uncountable people gaining a good living with Open Source, developers working on the different projects as their day job, system administrators managing open source platforms. We are helping out customers to implement Open Source and Free Software. And there are numerous other Drupal, Mysql, Xen, shops out there. Some have their own open source products and create a business on top of …

A classic Morecambe and Wise comedy sketch from the 1970s sees Andre Previn criticizing Eric for playing all the wrong notes while attempting the Greig Piano Concerto. Morecambe responds that he is in fact “playing all the right notes. But not necessarily in the right order.”

I was reminded of the sketch this morning while reading BusinessWeek’s article on the potential perils facing open source vendors today. It seems to ask all the right questions, but not necessarily in the right way.

The report suggests that while industry giants such as IBM, HP, Oracle and Intel stand to benefit from open source software, investor impatience could spell trouble for open source …

I was in San Francisco at the tail-end of last week and was fortunate to have some time to meet up with Josh Berkus, a member of the PostgreSQL core team and, until recently, a Sun employee.

Our conversation covered a lot of ground, including his reasons for leaving Sun (he didn’t go into detail but suffice to say he’s working a business idea), the future of the database market (more choice, more horizontal scaling, more use of specialist databases), the future of PostgreSQL (as a development platform), the level or authorization afforded to the Drizzle project, and the future of Sun.

I won’t go into the latter now, but the …

It seems almost churlish to wonder whether Google could be even more successful than it already is with a different strategy, but the company’s approach to open source and open development has come into focus in recent weeks.

On last week’s podcast we discussed whether the company should see the AGPL as more of an opportunity than a threat following Jay’s post about the company releasing more code under open source licenses.

Nik Cubrilovic over at TechCrunch, meanwhile, has written an interesting …

I was sitting in a train in the middle of rainy Ireland when I received a mail that Nokia has bought Symbian and is releasing it as Open Source. I didn't believe a word of it. But the web was full of news about it, so it was true. This is an amazing turn of events that I didn't anticipate at all. (You may or may not know that in my previous job I was heavily involved with Symbian programming. Ironically, one reason I left just 6 months ago is that I wanted to work in an Open Source environment :-)

read more

James Dixon has given the thumbs-up to my stretching his Bee Keeper analogy to explain open source development models (which is nice) and in doing so has suggested a new term to help quickly explain the difference between vendor- and community- dominated development projects.

The debate about the difference between the two approaches, and the language used to describe them, has been simmering for some time. For some background on it, and an explanation about why it matters, see Ted Ts’o’s …

I?ve been reading The Bee Keeper (also here in PDF), an explanation of the relationship between professional open source software (POSS) vendors and their communities, written by Pentaho?s CTO James Dixon. It is a very elegant explanation of the development/business model employed by the POSS vendors such as MySQL, Pentaho, JBoss and Alfresco.

James uses the analogy of the Bee Keeper to explain the model. It?s worth reading the paper in its entirety to understand just how appropriate this is but to put it very simply: the vendor is the bee keeper; the community is the bees; the open source project is the honey; and the customer …