The brouhaha around Redis Labs taking some enterprise modules of its popular open source in-memory database Redis closed source has somewhat calmed down. However, I didn’t see any discussion of what I thought was the most interesting conclusion of the affair: A core strategy of commercial open source,
the dual-licensing of the software under an aggressive copyleft and a commercial license may not work when cloud providers are involved.
To recap: Redis Labs develops and provides to the market the open source in-memory database Redis. It follows the commercial open source playbook: “Free-loading” users can use the software for free under the AGPLv3 license. Paying customers receive a commercial license. Those with a commercial license do not have to open source their application code, while non-paying users may have to. These are the effects of the AGPLv3 for the free version. It does not apply to in-house solutions, even if hosted in the cloud, but it does apply to software vendors that provide on-premise or hosted solutions to third parties, that is, their customers. To avoid having to open source, software vendors purchase the commercial license and Redis Labs makes some money.
Continue reading “Commercial Open Source in the Cloud”
Open source is a viable business strategy for software vendors to disrupt existing markets and conquer new ones. Just why is it easy in some markets and hard in others? I argue that you need to cut the product in such a way that there is a clear separation between what a never-paying community-user wants and what a commercial customer needs. In addition, you need to tie the commercial features closely to your company’s intellectual property and capabilities to keep competitors at bay. If you can do that, you are in the right place. If you can’t, you may want to get out of there.
Continue reading “The Challenge of Product Management in Commercial Open Source”
Redis is a popular open source database. Its proprietor, Redis Labs, recently announced that some add-on modules will not be open source any longer. The resulting outcry led to a defense and explanation of this decision that is telling. I have two comments and a lesson about product management of commercial open source.
The two comments are about messaging, both ways: What Redis Labs is telling the world and what the open source world is telling Redis Labs and the rest of the world.
Continue reading “The Cardinal Sin of Commercial Open Source?”
Am 18. September 2018 findet in Erfurt das 2018 Bitkom Forum Open Source statt. Thema ist die Werkzeugunterstützung von Open Source Governance und Compliance in der Softwarelieferkette. Meine Forschungsgruppe wird mit einem Vortrag zu Anforderungen an Open Source Governance and License Compliance vertreten sein, basierend auf einem gleichnamigen auf der OSS 2018 präsentierten Papier. Please come and join us!
For my AMCIS 2009 talk on the single-vendor commercial open source business model, first the abstract, then the slides:
Commercial open source software projects are open source software projects that are owned by a single firm that derives a direct and significant revenue stream from the software. Commercial open source at first glance represents an economic paradox: How can a firm earn money if it is making its product available for free as open source? This paper presents the core properties of commercial open source business models and discusses how they work… [more]
The talk slides are available as a PDF file and are licensed under the Creative Commons BY-SA 3.0 license.
For a discussion of the talk’s contents I recommend reading the original article.
I guess everybody knows it but nobody ever named it, as far as I know, so I’m doing it here:
The Intellectual Property Rights Imperative of Single-Vendor Commercial Open Source
Always act in such a way that you, and only you, possess the right to provide the open source project under a license of your choice.
Continue reading “The Intellectual Property Rights Imperative of Single-Vendor Open Source”
You may have noticed the recent discussion about which open source license a single-vendor commercial open source firm should choose for its community offering. In this blog post I’ll argue that this choice depends on the state and speed of the firm.
Continue reading “Every License has its Time and Place”
These are patterns and practices of getting the most out of your 140 characters on Twitter.
dirkriehle: Examples are in-lined using blockquote like this; the author is named first
Table of Contents
- General Principles
- Informational Messages
- Directed Conversations
- Social Filtering
- Global Communication
Continue reading “Patterns of Effective Tweeting and Retweeting”
There are many best practices of using Twitter for organizations. Here is one; I may post others in loose order as I have good examples at hand.
I was attending IBM’s NPUC:09. Like many, my first reaction when I’m unhappy these days is to tweet about it.
dirkriehle: Almaden is a great location, on top of a hill, but cell coverage fails and visitor wireless does not sustain livestreaming the speaker #npuc
Note the use of the event tag #npuc. It was being monitored by an IBM PR person, who I had never met and who I didn’t know. She responded promptly:
Continue reading “A Twitter Best Practice”
In 2004, SugarCRM coined the term “commercial open source“. This term was intend to separate the commercially-oriented open source projects of venture-capital-backed startups from the then dominant community open source projects. The term was picked up quickly, by many. I (as well as others) define it the following way:
“A commercial open source firm is a software firm that provides most or all of its product as open source while maintaining the relicensing rights to the source code.” (Maintaining the rights has the purpose of being able to sell the product to customers under a commercial license.)
This type of software firm has quickly become important and stands to gain even more ground. According to Gartner Group:
“By 2012, at least 50% of direct commercial revenue attributed to open-source products or services will come from projects under a single vendor’s patronage.” From: Mark Driver. “Predicts 2009: The Evolving Open-Source Software Model.” Gartner Inc, 2009.
Continue reading “Commercial Open Source: The Naming Confusion Remains”