Language Selection

English French German Italian Portuguese Spanish

MongoDB Becomes Less Affero GPL-Like

Filed under
Server
OSS
Legal
  • Fed up with cloud giants ripping off its database, MongoDB forks new open-source license

    After Redis Labs relicensed the modules it developed to complement its open-source database, from AGPL to Apache v2.0 with a Commons Clause, the free-software community expressed dismay.

    And, inevitably, some responded by forking the affected code.

    Today, the maker of another open source database, MongoDB, plans to introduce a license of its own to deal with the issue cited by Redis: cloud service providers that sell hosted versions of open-source programs – such as Redis and MongoDB database servers – without offering anything in return.

    "Once an open source project becomes interesting or popular, it becomes too easy for the cloud vendors to capture all the value and give nothing back to the community," said Dev Ittycheria, CEO of MongoDB, in a phone interview with The Register.

    Ittycheria pointed to cloud service providers such as Alibaba, Tencent, and Yandex. Those companies, he claims, are testing the boundaries of the AGPL by benefiting from the work of others while failing to share their code.

  • MongoDB switches up its open-source license

    MongoDB is a bit miffed that some cloud providers — especially in Asia — are taking its open-source code and offering a hosted commercial version of its database to their users without playing by the open-source rules. To combat this, MongoDB today announced it has issued a new software license, the Server Side Public License (SSPL), that will apply to all new releases of its MongoDB Community Server, as well as all patch fixes for prior versions.

    Previously, MongoDB used the GNU AGPLv3 license, but it has now submitted the SSPL for approval from the Open Source Initiative.

  • MongoDB license could push open source deeper into cloud: Is this what industry needs?

    Things just got serious in open source land. Despite the occasional Commons Clause or Fair Source licensing attempt to change the meaning of the words "open source" to include "the right for a private company to make money from its open source efforts," we've stuck to the Open Source Definition, and it has served us well. Open source communities have become the center of the innovation universe, giving us exceptional code like Linux, Kubernetes, Apache Kafka, and more.

  • It's MongoDB's turn to change its open source license

    The old maxim that the nice thing about standards is that there are so many to choose from could well apply to open source licensing. While now nearing a couple years old, the last WhiteSource Software survey of the top 10 open source licenses found close competition between the GPL, MIT, and Apache licenses. While the commercial-friendly Apache license has dominated the world of big data platforms and AI frameworks, MIT and GPL (which has "copyleft" provisions requiring developers to contribute back all modifications and enhancements) continues to be popular. GPL and variants such as the AGPL have been popular amongst vendors that seek to control their own open source projects, like MongoDB.

  • Matthew Garrett: Initial thoughts on MongoDB's new Server Side Public License

    MongoDB just announced that they were relicensing under their new Server Side Public License. This is basically the Affero GPL except with section 13 largely replaced with new text, as follows:

    "If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge, under the terms of this License. Making the functionality of the Program or modified version available to third parties as a service includes, without limitation, enabling third parties to interact with the functionality of the Program or modified version remotely through a computer network, offering a service the value of which entirely or primarily derives from the value of the Program or modified version, or offering a service that accomplishes for users the primary purpose of the Software or modified version.

    “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available."

    MongoDB admit that this license is not currently open source in the sense of being approved by the Open Source Initiative, but say:"We believe that the SSPL meets the standards for an open source license and are working to have it approved by the OSI."

    At the broadest level, AGPL requires you to distribute the source code to the AGPLed work[1] while the SSPL requires you to distribute the source code to everything involved in providing the service. Having a license place requirements around things that aren't derived works of the covered code is unusual but not entirely unheard of - the GPL requires you to provide build scripts even if they're not strictly derived works, and you could probably make an argument that the anti-Tivoisation provisions of GPL3 fall into this category.

"submitted the SSPL... approval from the Open Source Initiative"

Bradley M. Kuhn's Take

    • Bradley M. Kuhn: Toward Community-Oriented, Public & Transparent Copyleft Policy Planning

      More than 15 years ago, Free, Libre, and Open Source Software (FLOSS) community activists successfully argued that licensing proliferation was a serious threat to the viability of FLOSS. We convinced companies to end the era of “vanity” licenses. Different charities — from the Open Source Initiative (OSI) to the Free Software Foundation (FSF) to the Apache Software Foundation — all agreed we were better off with fewer FLOSS licenses. We de-facto instituted what my colleague Richard Fontana once called the “Rule of Three” — assuring that any potential FLOSS license should be met with suspicion unless (a) the OSI declares that it meets their Open Source Definition, (Cool the FSF declares that it meets their Free Software Definition, and (c) the Debian Project declares that it meets their Debian Free Software Guidelines. The work for those organizations quelled license proliferation from radioactive threat to safe background noise. Everyone thought the problem was solved. Pointless license drafting had become a rare practice, and updated versions of established licenses were handled with public engagement and close discussion with the OSI and other license evaluation experts.

      Sadly, the age of license proliferation has returned. It's harder to stop this time, because this isn't merely about corporate vanity licenses. Companies now have complex FLOSS policy agendas, and those agendas are not to guarantee software freedom for all. While it is annoying that our community must again confront an old threat, we are fortunate the problem is not hidden: companies proposing their own licenses are now straightforward about their new FLOSS licenses' purposes: to maximize profits.

      Open-in-name-only licenses are now common, but seem like FLOSS licenses only to the most casual of readers. We've succeeded in convincing everyone to “check the OSI license list before you buy”. We can therefore easily dismiss licenses like Common Clause merely by stating they are non-free/non-open-source and urging the community to avoid them. But, the next stage of tactics have begun, and they are harder to combat. What happens when for-profit companies promulgate their own hyper-aggressive (quasi-)copyleft licenses that seek to pursue the key policy goal of “selling proprietary licenses” over “defending software freedom”? We're about to find out, because, yesterday, MongoDB declared themselves the arbiter of what “strong copyleft” means.

Late coverage of this

  • MongoDB introduces the Server Side Public License for open source

    Recently, a group of disgruntled developers and companies took to the Commons Clause as a way to protect their open-source work. However, this caused great controversy within the open-source industry because the clause added restrictions to open-source licenses, therefore violating the accepted definition of open source as well as the guidelines for the Open Source Initiative’s (OSI) approved open-source licenses, according to Vicky Brasseur, vice president of the OSI.

A week later again

  • MongoDB Changes License

    MongoDB has revamped its open source license type in an attempt to prevent commercial organizations in Asia using the database commercially without sticking to the open source rules.

    The problem MongoDB has had is that some cloud service providers have been offering the Community Edition of its database as a service to clients. In a bid to prevent this happening, the database company has issued a new software license called the Server Side Public License (SSPL). This will apply to all new releases of its MongoDB Community Server, as well as all patch fixes for prior versions. Until now, MongoDB has been using the GNU AGPLv3 license.

    In practical terms, this doesn't make a lot of difference to most users as the changes to the license terms don't apply to them. The changes are only designed to apply to companies who want to run MongoDB as a publicly available service.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

This week in KDE: all about the apps

This week we landed a lot of nice improvements for KDE’s apps, which I’ve highlighted below! Of course we didn’t forget about Plasma, so have a look-see... Read more

Rolando Blanco: Ubuntu Desktop Makeover

I must confess that since Ubuntu started, there have been a lot of changes that we have experienced on our desktop (each time for the better). However, I have always loved changing its appearance, to one more according to my particular tastes, sometimes up to 3 changes per year. This is one of the features that I like most about GNU / Linux, the freedom to adapt everything to my liking. This time, I wanted to make some slight changes in search of elegant minimalism. This is how I started testing a new icon pack and a tool that works as a widget and that animates my desktop, for this I used Conky. Read more

WiFi Goes Open

For most people, adding WiFi to a project means grabbing something like an ESP8266 or an ESP32. But if you are developing your own design on an FPGA, that means adding another package. If you are targeting Linux, the OpenWifi project has a good start at providing WiFi in Verilog. There are examples for many development boards and advice for porting to your own target on GitHub. You can also see one of the developers, [Xianjun Jiao], demonstrate the whole thing in the video below. The demo uses a Xilinx Zynq, so the Linux backend runs on the Arm processor that is on the same chip as the FPGA doing the software-defined radio. We’ll warn you that this project is not for the faint of heart. If you want to understand the code, you’ll have to dig into a lot of WiFi trivia. Read more

Kernel: Linux 5.8, Linux 5.7, FSGSBASE and HWMON

  • Improved EXT4 + XFS DAX Implementation Appears Ready To Go For Linux 5.8

    Adding to the expected changes for Linux 5.8 is improved EXT4 and XFS file-system direct access "DAX" support. DAX is the means of direct access to files backed by persistent memory (such as Intel Optane DC Persistent Memory) without needing to be copied via the page cache. Thus DAX bypasses that extra copy for reads/writes to the storage device and mapping the storage device directly into user-space.

  • The Top Linux 5.7 Features From Apple Fast Charge To Official Tiger Lake Graphics

    Assuming no last minute concerns, the Linux 5.7 kernel is set to debut as stable this weekend. Given all the weeks since the merge window and our many articles covering all the feature activity at that point (and not to be confused with our activity of new work being queued for the upcoming Linux 5.8 cycle), here is a look back at some of the top features of the Linux 5.7 kernel. Among the most interesting new features and improvements for Linux 5.7 include: - Intel Tiger Lake "Gen12" graphics are now enabled by default in being deemed stable enough for out-of-the-box support where as on prior kernels the support at the time was hidden behind a kernel module parameter.

  • Performance-Helping FSGSBASE Patches Spun For Linux A 13th Time

    The FSGSBASE Linux kernel patches that have the potential of helping performance going back to Intel Ivy Bridge era CPUs in select workloads have now hit their 13th revision to the series in the long-running effort to getting this support mainlined.

  • Linux's Hardware Monitoring "HWMON" Picking Up Notification Support

    In addition to the AMD Zen "amd_energy" driver coming for Linux 5.8, another late change now queued into hwmon staging is introducing notification support for the hardware monitoring subsystem. HWMON subsystem maintainer and Google employee Guenter Roeck has queued up notification support for this subsystem. This serves as a generic notification mechanism not only to notify user-space but also the thermal subsystem for any HWMON driver events. In the HWMON context, these events could be important like warnings/critical alarms over detected temperatures or voltages for different components.