Showing entries 1 to 7
Displaying posts with tag: james dixon (reset)
451 CAOS Links 2010.04.23

The White House contributes to OSS. Growth for Pentaho and MuleSoft. And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca
“Tracking the open source news wires, so you don’t have to.”

# The White House released some of the custom code it has developed for whitehouse.gov as open source.

# Pentaho reported 229% bookings growth and 177% Enterprise Edition customer growth in Q2.

# MuleSoft grew bookings by 140% in Q1.

# The beta of Red Hat Enterprise Linux 6 is now available, without Xen.

[Read more]
Let he who is without proprietary features cast the first stone

If the recent debate about open core licensing has proven one thing, it is that the issue of combining proprietary and open source code continues to be a controversial one.

It ought to be simple: either the software meets the Open Source Definition or it does not. But it is not always easy to tell what license is being used, and in the case of software being delivered as a service, does it matter anyway?

The ability to deliver software as a hosted service enables some companies that are claimed to be 100% open source to offer customers software for which the source code is not available. Coincidentally, James Dixon has this week highlighted one …

[Read more]
451 CAOS Links 2009.05.15

Open Database Alliance formed. Oracle buys Virtual Iron. AccesStream reaches version 1.0. And more.

Follow 451 CAOS Links live @caostheory

I’ve just met a fork named Maria
MySQL founder Monty Widenius and Percona CEO Peter Zaitsev announced the launch of the Open Database Alliance - “a collection of companies working together to provide the software, support and services for MariaDB, an enterprise-grade, community-developed branch of MySQL.”

Continuent and Open Query quickly announced their membership, while Monty later …

[Read more]
451 CAOS Links 2009.04.24

Oracle buys Sun. Sun previews MySQL update, makes GlassFish Portfolio, OpenSSO and OpenDS available on EC2. Numerous partner announcements from the MySQL conference. Red Hat maps open source adoption. And more.

Follow 451 CAOS Links live @caostheory

Oracle to acquire Sun
Unless you’ve been living under a rock (or like me you decided to take a few inappropriately-timed days off) you probably noticed that Oracle announced an agreement to acquire Sun this week. Jay delivered our assessment on Oracle’s open source credentials, while I followed up with some …

[Read more]
451 CAOS Links 2009.04.14

Refining the Beekeeper model. Investment opportunities. Schooner, Gear6 and Virident line up memcached appliances. The launch of the Open Source Channel Alliance. Is source code necessary? And more.

Follow 451 CAOS Links live @caostheory

Of bees and trees
We noted last week that James Dixon, CTO of Pentaho, had updated his Beekeeper model for understanding the commercial-community relationships employed by vendors to engage with open source. Roberto Galoppini quickly followed up with some feedback, as did Tarus …

[Read more]
The vocabulary of open source development models

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 …

[Read more]
Applying the Bee Keeper model beyond captive open source projects

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 …

[Read more]
Showing entries 1 to 7