Language Selection

English French German Italian Portuguese Spanish

Commercial Open Source?

Filed under
OSS

Here’s a wrinkle that many devotees of open source either don’t know about, or don’t talk about. As it turns out, open source projects can get acquired by commercial software companies. And to prove that point, one of the more popular open source projects on sourceforge.net was acquired last week. To what extent the acquisition of an open source project results in its being taken out off the open source shelves depends on many things. For example, how many people were contributing to it before the acquisition, who are they, and what are their plans now that their open source project has been acquired?

To acquire an open source project, the acquirer has to, with almost 100 percent certainty, be sure that they are acquiring the copyrights to all of the code being used in the project. Those copyrights ultimately belong to the individual contributors to the project who, up until the point of acquisition, would have been bequeathing certain rights to their code to others under whatever open source license is behind the project. To the extent that licensing that code under an OSI-approved license is what let the code out out of the box and into the open source wild, there’s nothing that the acquirer can do to put it back in the box. That code will always remain available under whatever open source license it was published. But, by acquiring the copyrights and any trademarks that are associated with that code, the acquirer also acquires the right to modify and distribute the original code without having to make those modifications available under an open source license. In other words, future versions of the open source software could become closed source. So, how could this play out?

With a project like Linux, there’s pretty much a zero probablility of the project ever being acquired because of how many contributors are involved. Not only would it be difficult to track them all down, establish with some degree that they are indeed the copyright holders, and reach some mutually beneficial financial arrangement to give an acquirer all the rights they need. There’s also the high likelihood that some passionate group of developers would take the core body of source code that was already available under an open source license (the GPL), and exercise their rights to continue the evolution of an open source version of Linux. The end result, even if someone successfully "acquired" Linux, would be a tangible forking of the code. One fork would be open source version that the passionate community carried forward. The other would be the commercial derivative that was some percentage open source (by virtue of the "grandfathered" code base), and some percentage closed source.

But what about a popular open source project that has far fewer developers with far fewer copyrights to track down? Sure, the developers could sell their copyrights to the acquirer, but nothing prevents them from continuing to evolve the already open-sourced code under an open source license. That is, unless, in the process of acquiring the copyrights to the source code, the acquirer also hires the most passionate developers — the driving forces — behind the open source project.

Full Story.

More in Tux Machines

Ubuntu 16.04.2 LTS Delayed Until February 2, Will Bring Linux 4.8, Newer Mesa

If you've been waiting to upgrade your Ubuntu 16.04 LTS (Xenial Xerus) operating system to the 16.04.2 point release, which should have hit the streets a couple of days ago, you'll have to wait until February 2. We hate to give you guys bad news, but Canonical's engineers are still working hard these days to port all the goodies from the Ubuntu 16.10 (Yakkety Yak) repositories to Ubuntu 16.04 LTS, which is a long-term supported version, until 2019. These include the Linux 4.8 kernel packages and an updated graphics stack based on a newer X.Org Server version and Mesa 3D Graphics Library. Read more

Calamares Release and Adoption

  • Calamares 3.0 Universal Linux Installer Released, Drops Support for KPMcore 2
    Calamares, the open-source distribution-independent system installer, which is used by many GNU/Linux distributions, including the popular KaOS, Netrunner, Chakra GNU/Linux, and recently KDE Neon, was updated today to version 3.0. Calamares 3.0 is a major milestone, ending the support for the 2.4 series, which recently received its last maintenance update, versioned 2.4.6, bringing numerous improvements, countless bug fixes, and some long-anticipated features, including a brand-new PythonQt-based module interface.
  • Due to Popular Request, KDE Neon Is Adopting the Calamares Graphical Installer
    KDE Neon maintainer Jonathan Riddell is announcing today the immediate availability of the popular Calamares distribution-independent Linux installer framework on the Developer Unstable Edition of KDE Neon. It would appear that many KDE Neon users have voted for Calamares to become the default graphical installer system used for installing the Linux-based operating system on their personal computers. Indeed, Calamares is a popular installer framework that's being successfully used by many distros, including Chakra, Netrunner, and KaOS.

Red Hat Financial News

Wine 2.0 RC6 released