Justin Tadlock takes the dual licensing question and puts it in user friendly terms, WP Tavern, Proposal and Steps To Dual-License Gutenberg Under the GPL and MPL: “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.”
The big procedural hurdle in the dual licensing plan is getting permission from all existing copyright holders. Justin does go about detailing how this can be solved, but in my head this seems like a complicated and/or long process.
This is sweet and simple, load WordPress sites in as fast as 37ms with Cloudways!
So what can be done? As per usual the GPL licensing discussions can get confusing, personal, frustrating, or ignored. I may be showing my Gutenberg naïveté but would it be crazy to suggest a Gutenberg API connection to a users site? Bear with me.
Gutenberg proper would reside on the hosted WordPress site. APIs and descriptions of the functionality also live on the WordPress site. A proprietary editor could be created to connect with the API, interrogate functions, and dynamically generate its own experience based on the rules sent.
I’m a bit outside my wheelhouse here with regards to the technology and/or feasibility of such an idea but let’s take a look at the plus side of such an undertaking.
- No more issues with licensing
- Lots of control for app developers
- Innovation opportunities
Gutenberg has a brilliant future, and I think we should take advantage of the best features without necessarily trying to shoehorn it into apps where it may not be as strong.