There was some interesting discussion following my post last week asking whether there is a growing rift between commercial open source software vendors and some aspects of the open source user community.
Amongst the comments, Chris Marino of SnapLogic suggested that some of the tension might be eased by open source software vendors being more upfront about their intentions via the publication of social contracts. Examples include the Debian Social Contract and also Funambol’s Open Source Project Social Contract.
As Chris noted, the problems come when companies start changing how they interact with open source communities. Nevertheless, this sort of contract at least lays out the ground rules so that users and developers know what sort of vendor they are involved with and have something definitive to refer to when disagreements arise.
If vendors are not proactive about writing and publishing declarative statements about their open source involvement, they may find that community users start judging them on the community’s terms. From Milking the GNU comes the suggestion that a new independent organization could be formed to judge vendors that claim to be open source on a number of criteria, such as patent policy, business model and development model.
“Equitable Open Source” as it is called, is only a suggestion at this stage, but is an example of the caution being expressed by some users towards commercial open source vendors. As the idea is described, it would at least create a level playing field upon which vendors can be judged.
This would help to avoid debates like this one, in which Baron Schwartz argues that MySQL is free software but not open source. His point is that the development model is not open.
While respondents have pointed out that, according to the Open Source Definition, MySQL is in fact open source, the fact is that the OSD only defines the license used to distribute the software, not the method used to develop it.
Simon Phipps has recently suggested adding open source patent and trademark definitions to the Open Source (Copyright) Definition. Does the industry need an open source definition for business and development models?
I was just reading Fabrizio Capobanco’s take on the MySQL excitement (”this move is clearly into the right direction”) when it occurred to me that the situation is related to the comments recently made by the former CTO of Kaplan Test, Jon Williams, at the recent OSBC conference.
As I wrote at the time: “Another point Jon made was that the subscription model helps keep open source vendors on their toes as every year he gets to decide whether they will received another payment.”
In other words, as Matt Asay put it: “the more happy he is with his commercial open-source software, the less likely he will be to pay for it. Why? Because his developers will acquire the expertise over time to support themselves and because the product will mature to the point that support will be less necessary.?
Is this the challenge that MySQL faces? A lot of attention is placed on its circa 1:1,000 conversion rate from Community users to Enterprise subscribers, but I wouldn’t mind betting MySQL and Sun are more concerned about retaining that one existing paying customer than they are chasing the 999 who will most likely never pay.
That does not mean the company should - or can afford to - turn its back on its Community users, of course, but it does make it hard to balance the two communities. Ultimately I believe that a lot of the really negative reaction has been based on a misunderstanding that the company was going to remove features from the open source version, which is clearly not the case.
The company needs to move quickly to decide and explain how exactly it is going to license the new functionality. Once it has everyone can make up their own minds and get on with (or without) it. Until then, the confusion is likely to grow.
License:GPL: del.icio.us tag/gpl
Software
distribution
gpl
opensource
licensing
License:GPL
SaaS