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

4 keys to success for LibreOffice as a service

The announcement of LibreOffice Online this week came as welcome news to many people concerned about the paucity of online options for those who want software freedom with their online document solutions. But can open source SaaS succeed? The open source community needs a truly open alternative to current mainstream online document collaboration solutions, all of which are compromised by lock-in. LibreOffice Online will offer the full flexibility to deploy in-house or hosted cloud instances while using true open standards for its documents. Read more

Bazel: Google Build Tool is now Open Source

Bazel, the tool that Google uses to build the majority of its software has been partially open sourced. According to Google, Bazel is aimed to build “code quickly and reliably” and is “critical to Google’s ability to continue to scale its software development practices as the company grows.” Read more Also: Q&A: Databases, Open Source & Virtualisation with CEO Vinay Joosery

Ubuntu Kylin 15.04 Beta 2 Is Now Available for Download - Screenshot Tour

After announcing the Ubuntu 15.04 Final Beta and Kubuntu 15.04 Beta 2, it is now time to take a look at the second and last Beta release of the upcoming Ubuntu Kylin 15.04 (Vivid Vervet) operating system that has been designed especially for the Chinese Ubuntu Linux community. Read more Also: Ubuntu MATE 15.04 (Vivid Vervet) Beta 2 Switches to Systemd - Screenshot Tour Ubuntu 15.04 (Vivid Vervet) Final Beta Officially Released - Screenshot Tour

Kubuntu 15.04 Beta 2 Released with KDE Plasma 5 as Default Desktop - Screenshot Tour

Today’s announcement for Ubuntu 15.04 (Vivid Vervet) Final Beta also mentioned the immediate availability for download and testing of Kubuntu 15.04 Beta 2, an official Ubuntu flavor built around the modern and attractive KDE Plasma 5 desktop environment, as well as the KDE Applications project. Read more Also: Xubuntu 15.04 Beta 2 Released, Offers a Neat Xfce 4.12 Experience - Screenshot Tour