Commentary
Open Three Ways, Or More
Ealier in the week the CAOS Theory blog of the 451 Group noted there were three, or actually four, ways you could handle "open core" licensing -- where the basic version of your product is free, but the add-ons and support and such are not. Everyone will (and should) do these things differently, and the details are full of devils.
Ealier in the week the CAOS Theory blog of the 451 Group noted there were three, or actually four, ways you could handle "open core" licensing -- where the basic version of your product is free, but the add-ons and support and such are not. Everyone will (and should) do these things differently, and the details are full of devils.
More Software Insights
White Papers
- Red Alert: Why Tablet Security Matters - by BlackBerry
- New Visual and Wizard-Driven Paradigms for Exploring Data and Developing Analytic Workflows
Reports
More >>Webcasts
- Maximize ROI with Database Consolidation onto Private Clouds
- Outsourcing Security: What Every Potential Cloud Security Customer Should Know
The blog post itself surrounded the three-and-a-half choices in question with a lot of good commentary. The options themselves run like so:
- Open core with paid services. Free product, with bonus features (support, management, auxiliary storage, hosting) delivered in a managed / SaaS fashion to the end user. Some folks who do open source CMS are taking an approach like this: you can snag the core product, run in on your own, or pay them to run it for you in a guaranteed-uptime fashion.
- Open core with closed add-ons. Such for-pay components usually consist of things like data connectors that allow you to plug into other proprietary products: you can be free on your own, but you'll have to pay to liberate your existing data. Or it's add-ons that transform what you have for the rest of the world's sake in ways that would involve a lot of additional programming.
- Open core under a custom license. That's right -- release an open core product using a license of your own devising, without hanging around for OSI approval.
The third option is a deviation of "open core under an OSI-approved license", which is the path most people take for such things anyway. Hence, three-and-a-half.
Option #1 and #2 are worth their own discussions. But Option #3? I can imagine a response from the existing open source folks that goes something like this:
It's hard not to make use of an existing OSI-approved license. There's plenty of them, they cover the vast majority of business or development scenarios; and (most useful if you are big on people giving back) picking the right one means you automatically attract a certain class of user and developer to you. Hatching your own license is an uphill battle, the sort of thing you only do when there is literally no other choice.
End imaginary quote. In fact, I've said things of a similar tenor myself more than a few times. But the problem with the "there's all the licenses you could need" mind-set is the same as the (admittedly mythological) "640K should be enough for anyone" quote.
Things change. That includes the circumstances under which software licenses are created, adopted, and put to use. It's also going to include the way open source is handled by commercial outfits, and whether or not it forms the real basis for their business.
InformationWeek has published an in-depth report on Sun's future under Oracle. Download the report here (registration required).
Follow me and the rest of InformationWeek on Twitter.
Related Reading
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. | |
|
|
T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting! |
Subscribe to RSSResource Links
This Week's Issue
Technology Whitepapers
- Mobile BI: Actionable Intelligence for the Agile Enterprise
- Creating the Enterprise-Class Tablet Environment - by Yankee Group
- How To Regain IT Control In An Increasingly Mobile World - by BlackBerry
- The BlackBerry PlayBook tablet's Good Bones - by BlackBerry
- Red Alert: Why Tablet Security Matters - by BlackBerry
Featured Broadcast
This white paper explains how to create a manageable, scalable environment suited to answer real-time business needs by building out a data center on a standards-based, virtualization-aware, energy-efficient and affordable platform. Plus, learn how virtualization is making the jump from the server realm into the application, mobile and database worlds in the additional resources section.
Learn More












