Proposal and Steps To Dual-License Gutenberg Under the GPL and MPL

The GPL is so embedded into WordPress that it is not just the license the platform is under but a part of the community’s culture. Friends have been gained and lost over discussions of it. Bridges burned. Battles waged. People cast out to the dark corners of the web that “we don’t talk about.” There was even a time when one could expect a fortnightly GPL dust-up in which the inner WordPress world argued the same points over and over, ad nauseam.

It might be hard to imagine a world where — outside of third-party libraries — direct contributions to the software are under anything other than the GPL. However, the wheels are now in motion. The Gutenberg project, which is the foundation of WordPress going forward, may soon be under both the GNU General Public License (GPL) v2 and the Mozilla Public License (MPL) v2.0.

The goal is to allow Gutenberg to be used in proprietary applications, particularly in the mobile space, where it can be a hurdle to ship GPL code.

Mobile Team contributor Maxime Biais proposed the change in July 2020. “Gutenberg supports two main platforms, the web and the native mobile apps. The GPL v2.0 license is a blocker for distributing the Gutenberg library in proprietary mobile apps.”

At the moment, the WordPress for Android and WordPress for iOS apps use Gutenberg. Both of these apps are also licensed under the GPL, so it is a non-issue for them. However, it is uncommon for mobile apps to use the GPL. Thus, it limits Gutenberg’s potential reach.

“Rich text editor libraries in the mobile space are lacking,” wrote Biais. “There is no well known open source rich text editor for Android or iOS. We believe that Gutenberg could be a key library for many mobile apps, but that will never happen with the GPL v2.”

The proposal was announced on the Make Core blog in September 2020. It garnered three comments. WordPress project lead Matt Mullenweg was in favor of the change, pointing out that it could help Gutenberg become a cross-CMS standard.

“Right now it’s easy to distribute Gutenberg with web apps that aren’t GPL, due to the way browsers link and bundle things, but embedding Gutenberg inside a native app on desktop, iOS, Android, or beyond is not possible unless the entire application is also GPL,” he wrote. “Allowing people the option to embed Gutenberg under the MPL I think will increase its usage outside of WordPress, bring more contributors to the core experience, and continue the Cambrian explosion of blocks that will give Gutenberg users more tools to fully express their creativity and vision.”

The problem with switching licenses is that Gutenberg needs permission from every contributor who has added code to the project to make this change. The GitHub repository lists 721 individual contributors since the project began in 2016. To change licenses, each one must consent because they still own the copyright to their code.

Some of these people may not be involved any longer and not respond to the consent request. Others may refuse — as is their right. In either case, the Gutenberg team will need to either remove or rewrite the code.

The proposal outlines four stops on the timeline before Gutenberg can be officially dual-licensed:

  • March 19: All future contributions will be under both the GPL and MPL.
  • April 2: Seek consent via GitHub from past contributors and contributors from open pull requests.
  • Three months later: Begin removing or rewriting code that cannot be relicensed.
  • Future: Once all removed or rewritten code is squared away, update Gutenberg as a whole to a GPL/MPL dual license.

For a licensing discussion, only a few people have chimed in. However, some have brought up concerns.

“WordPress has historically strongly believed in the GPL,” wrote core WordPress contributor Aaron Jorbin in the comments. “It has gone so far as to call the Four Freedoms of the GPL it’s ‘Bill Of Rights.’ And now what is being said is that only sometimes do you get these freedoms. Anyone is welcome to take the code and remove these freedoms. Instead of empowering users, this move is empowering the removal of freedom. To me, this feels like a very pro-business move and a very anti-user one.”

The MPL is not considered viral in the same way as the GPL. Applications built with GPL-licensed code must allow for the same freedoms or more. App developers can distribute MPL-licensed code as long as it is in a separate file from their proprietary code. This lets businesses restrict parts of the codebase. Users might not have the freedom to use, fork, modify, and share all of an application’s code.

Most who have commented on the official threads so far have been excited or OK with the proposal. It can open Gutenberg to a new market. If developers in the mobile space begin using it for their apps, it could bring in fresh talent to the WordPress project as a whole.

“Our app sorely lacks a WYSIWYG editor,” wrote Radek Pietruszewski, the tech lead for Nozbe Teams, on the GitHub ticket in July 2020. “We had a working implementation on web, but we decided to scrap it because there was no way to port it on iOS and Android. There are pretty much no viable rich text editors for iOS or Android, let alone both. But even then, shipping three completely separate, but somehow compatible editors would be a vast amount of work. And you know yourself, making a good rich text editor from scratch is incredibly hard. It’s not something we could do ourselves. Gutenberg could solve this problem for us if it wasn’t for the licensing.”

How things move forward comes down to the 700+ contributors. Will the Gutenberg team be rewriting swaths of code? Or, will most developers sign off on the license change?


5 responses to “Proposal and Steps To Dual-License Gutenberg Under the GPL and MPL”

  1. It may be time to start looking for another CMS. I’m a lawyer and don’t even understand all the licensing issues and certainly don’t have time to read and research license agreements. I have long avoided using Code Canyon scripts because of their insanely complicated license agreements.

    I have no interest in trying to understand MPL and how it will affect my 50 or so WordPress sites.

    • I am not a lawyer and understand most of the licensing issues. I was able to read and grasp the MPL in a few minutes. Given your background, I think you should have no issues with it.

      If you are not contributing code to Gutenberg or building a third-party app that bundles it, you can just go about your day as if nothing is changing. If switching to a different CMS, you will need to understand whatever license it is under too.

  2. The communication around GPL from the inception of WP has been that it’s the most ideal license for the project and must be strictly upheld to protect its freedoms. Anything that even slightly touches WP, or refers to WP code in some way, must be GPL. No exceptions or flexibility allowed or tolerated whatsoever. It can be a challenging license, but it makes sense, and we all have learned to embrace it as part of WordPress’ DNA.

    And now a major new component that is touted as the future of WP may get a whole other license? Apparently there’s a business need, but no other business needs have ever been considered, not even slightly (as far as I know).

    And with all due respect to mobile apps (some of my best tools are mobile apps 🙂), how is that the ultimate business need that is succeeding in pushing WP in another direction? I have a feeling that there are a zillion other business needs that would benefit from a different license, but no one has cared about that.

    I’m not saying I’m against this move. It just feels like a drastic about-face after years of effort and messaging and enforcement around upholding GPL down to the tiniest details 🤷🏻‍♀️.

  3. Any free volunteers (I say free because some are paid to “volunteer” on WP) should put much thought in deciding if its still worth contributing free time to a codebase that may soon be allowed to be proprietary for someone to profit off of.

  4. The GPL battles of old gave us fremium plugins (and themes & page builders). If your plugin wasn’t GPL it wasn’t listed on Tough luck if it was good or useful.

    When the history of WP is written the watering down of the GPL requirement will mark the sunset of WP’s place in the sun.

    If Gutenburg is the future of WP, then the GPL must stay at the centre.Pa


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: