Language Selection

English French German Italian Portuguese Spanish

Does “Open Core” Actually Differ from Proprietary Relicensing?

Filed under
OSS

I've been criticized — quite a bit this week, but before that too — for using the term “Open Core” as a shortcut for the phrase “proprietary relicensing0 that harms software freedom”. Meanwhile, Matt Aslett points to Andrew Lampitt's “Open Core” definition as canonical. I admit I wasn't aware of Lampitt's definition before, but I dutifully read it when Aslett linked to it, and I quote it here:

[Lampitt] propose[s] the following for the Open Core Licensing business model:

* core is GPL: if you embed the GPL in closed source, you pay a fee

* technical support of GPL product may be offered for a fee (up for debate as to whether it must be offered)

* annual commercial subscription includes: indemnity, technical support, and additional features and/or platform support. (Additional commercial features having viewable or closed source, becoming GPL after timebomb period are both up for debate).

* professional services and training are for a fee.

The amusing fact about this definition is that half the things on it (i.e., technical support, services/training, indemnity, tech support) can be part of any FLOSS business model and do not require the offering company to hold the exclusive right of proprietary relicensing. Meanwhile, the rest of the items on the list are definitely part of what was traditionally called the “proprietary relicensing business“ dating back to the late 1990s: namely, customers can buy their way out of GPL obligations, and a single company can exclusively offer proprietary add-ons. For example, this is precisely what Ximian did with their Microsoft Exchange Connector for Evolution, which predated the first use of the term “Open Core” by nearly a decade.

rest here




More in Tux Machines

today's leftovers

Software: Grafana, Heaptrack, Vim

  • Grafana – An Open Source Software for Analytics and Monitoring
    Grafana is an open source, feature rich, powerful, elegant and highly-extensible analytics and monitoring software that runs on Linux, Windows and MacOS. It is a de facto software for data analytics, being used at Stack Overflow, eBay, PayPal, Uber and Digital Ocean – just to mention but a few. It supports 30+ open source as well as commercial databases/data sources including MySQL, PostgreSQL, Graphite, Elasticsearch, OpenTSDB, Prometheus and InfluxDB. It allows you to dig deeply into large volumes of real-time, operational data; visualize, query, set alerts and get insights from your metrics from differen
  • Heaptrack v1.1.0 release
    Better memory profiling on Linux After more than a year of work, I’m pleased to release another version of heaptrack, the Linux memory profiler! The new version 1.1.0 comes with some new features, significant performance improvements and – most importantly – much improved stability and correctness. If you have tried version v1.0 in the past and encountered problems, update to the new v1.1 and try again!
  • Ten Years of Vim
     

    The philosophy behind Vim takes a while to sink in: While other editors focus on writing as the central part of working with text, Vim thinks it's editing.

     

    You see, most of the time I don't spend writing new text; instead, I edit existing text.

  •  

GNU/Linux: Parrot 4.0, Oregan, Containers and Linux 4.18 Plans

  • Parrot 4.0 is out
    Parrot 4.0 has been released. Parrot is a security-oriented distribution aimed at penetration tests and digital forensics analysis, with additional tools to preserve privacy.
  • Parrot 4.0 release notes
  • Oregan launches SparQ middleware for Linux and Android TV
    Oregan said that the open standards-based offering resolves the differences between the current security and performance requirements of modern-day TV services and the hardware capabilities of STBs that were deployed up to a decade ago.
  • Linux app support coming to older Chrome OS devices
    Linux apps on Chrome OS is one of the biggest developments for the OS since Android apps. Previous reports stated Chromebooks with certain kernel versions would be left in the dust, but the Chrome OS developers have older devices on the roadmap, too. When Google first broke silence on Linux app functionality, it was understood that Linux kernel 4.4 was required to run apps due to dependencies on newer kernel modules. Thanks to an issue found on Chromium’s public bugtracker, we have confirmation that containers won’t be limited to the handful of Chrome OS devices released with kernel 4.4.
  • Looking Ahead To The Linux 4.18 Kernel
    There still are several weeks to go until the Linux 4.17 kernel will be officially released and for that to initiate the Linux 4.18 merge window, but we already know some of the features coming to this next kernel cycle as well as an idea for some other work that may potentially land.

Red Hat and Fedora Leftovers