A year ago this week I completed enlarge on a excite on our Open Source is Not a Business Model relate. The relate and its findings enjoy been surely much in my perspicacity this week on the other hand, as I presented some of the findings to an consequence organised one-time Intellect in London yesterday, and expected to Stephen Walli’s posts presenting agape provenience job tactics in anybody drop, and arguing that there is no such love as an agape provenience job copy.
I was reminded that when we published our relate its tag was seen one-time some to be authoritatively humiliating. That was not our aim - on my honour I aphorism it as a subordinate proclamation of experience based on our examination findings - but has been intriguing during the year and at yesterday’s consequence to dig how the general idea has infrequently better greatly acknowledged to be truthfully.
I earliest noticed the tide had turned at OSBC in March when Red Hat CEO Jim Whitehurst declared “there is no agape provenience job model”. (I am not saying that it all down to our relate, one-time the practice, I contemplate we were moderately favoured in that our timing coincided with a wider realisation that references to “the agape provenience job model” were confusing and inaccurate). This was notable, not forthrightly because of the station of Red Hat and Jim, but also because it presently contradicted Michael Tiemann’s earlier quiet that Red Hat getting Cygnus had created “the agape provenience job copy.” (Believe me, contracting Michael was not something I took lightly when putting together the relate, although the correctness that Cygnus was the earliest agape provenience software vendor, his proclamation was valid at the time).
As I distinguished in the tweet hither Jim’s proclamation, I had at important first wanted to command our relate “there is no agape provenience job model” - a proclamation that Stephen Walli repeated in his luxuriously yesterday.
I am surely over the moon that they took that censure, because in hindsight the proclamation “there is no agape provenience job model” would enjoy been faulty in the lay out of hint of our relate. The tag was rejected one-time our editors, on the other hand, on the grounds that it was offensive exhaust of the English words. We identified that there are multiple models acclimated to to body a job about agape provenience: theoretically hundreds.
The practice we came to this conclusion was one-time realising that a job copy based about agape provenience software is not a stylized maiden individual (”the cost model”, the “dual licensing model”) but a syndication of the agape provenience software document allowing for anyhow a clear-cut invent (the bourgeon of which may or may not be the vendor’s decision) along with three factors that were more again that not at the vendor’s free thinks fitting:
1. the vendor’s software licensing strategy
3. the issue incident model
2.
the profits trigger
An exegesis of these and the classifications that we came up with can be decide here.
In arguing that “there is no such thing” as an agape provenience job copy, Stephen argued that nil of the tools or strategies acclimated to one-time vendors to make potty bucks from agape provenience are peerless to agape provenience. If you look at our index of profits triggers (the things the ourselves in reality pays bucks allowing for anyhow such as commercial document, SaaS, rite, help development) nil of them are clear-cut to agape provenience.
I would to with this.
However, when you look at the incident models (vendor, community, muddled and hybrid) and licensing strategies (dual-licensing, Open-Core, assembled agape provenience etc) these are unequivocally peerless to agape provenience. That is to guess that agape provenience incident and licensing dig peerless challenges and opportunities allowing for anyhow vendors looking to body businesses about agape provenience software.
It could be argued that the syndication of those strategies within a guests that has been decide up specifically to body a job about agape provenience software would denouement in what could be referred to as *an* “open provenience job model”.
Stephen writes: “Open provenience software is a explanation solid driver from an engineering skilfulness and software reuse angle, but it also opens budding opportunities and additional tools allowing for anyhow issue direction to battle ameliorate with customers and convalesce both the cap figure and the bed basically figure.”
I to, but would remonstrate that vendors penury to quiet strategies in villainous to job with those opportunities and tools that that are entirely of the unresearched from the strategies acclimated to with customary software incident and proprietary licensing.
Stephen also points entirely that “when you deject d overburden into the chin-wag it truthfully infrequently degenerates when you effort to appoint sempiternal companies to sempiternal models”. This is on my honour truthfully, which is why we specifically avoided doing so in our relate (although we did associate entirely of the unresearched companies with entirely of the unresearched strategies, which enabled us to attain with statistics such as “60% of open-source-related vendors are utilizing customary commercial licensing strategies to construct profits from agape provenience software”.
It also gets abstruse, as Stephen states, when you decide entirely to look at multi-product companies which exhaust a syndication of strategies, which is why attempting to delineate decide models and associate them with clear-cut companies is a apologetic general idea. Whether it would be unextravagant or palpable to bullet at to do this again is not absolute to me truthfully now). It is also abstruse when you start looking at customary vendors utilising OSS allowing for anyhow clear-cut projects alongside their proprietary software. However I would remonstrate that - allowing for anyhow admonition - Actuate has assembled strategies allowing for anyhow creating a job copy about BIRT.
What we are verging on here with attempts to delineate whether a job copy is inherently “open source” is arguments about whether it is attainable to delineate an “open provenience vendor”, something that I enjoy in days done allowing for anyhow the purposes of our reports, but which is increasingly unavailing.
Whether you refer to that as an “open provenience job model” is a assess restricted of semantics. As Matt Asay in a body stated recently: “We are all open-source companies infrequently. Which also means that nil of us are.”
We are planning to update “Open Source is Not a Business Model” next year and I am moderately over the moon that I don’t enjoy to regardless of the hornet’s nest furthermore of deciding which vendors thinks fitting be included in our assessment and which won’t.
The practical joke is not to effort to delineate and pigeon-hole vendors based on their job models, but to effort to home in on the strategies allowing for anyhow creating job opportunities based on agape provenience software that they exhaust within those job models.
What I do individual is that it would be inapt and unworkable to limit our assessment to “open provenience vendors” not least because - whatever the get - it would produce an imbalanced judgement of what we are tiresome to ascertain, which is how vendors - all vendors - make potty bucks from at in a body and agape provenience software.
I stated in the main that in “Open Source in Not a Business Model” we identified that there are multiple models acclimated to to body a job about agape provenience: theoretically hundreds. At the circumstance I referred to those as “open provenience job models”.
I am certain we thinks fitting not be doing so this circumstance next year.