You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the licensing for Gutenberg blocks? Will it be ok to publish blocks to the Wordpress Marketplace?
Since #2298 was raised, React moved to the MIT license. This is not GPL and, although they are compatible, Automattic will not accept dual licensed code in the Marketplace for either themes or plugins. Matt explained the situation in There is No Such Thing as a Split License
How does the inclusion of React (and the many licenses included in its dependencies) affect this position? If people start creating blocks will the restrictions for non-GPL code be lifted in light of Matt's strong stance on the issue?
The text was updated successfully, but these errors were encountered:
In Gutenberg, blocks are programmed in a similar way to widgets or other WordPress plugins, they are directly linked to WordPress' APIs. With that in mind, the advice we received from the Software Freedom Law Center years ago also applies to the JavaScript that you write to create blocks: the code is directly linked to WordPress' (or Gutenberg's) GPLv2-licensed JavaScript, so must have a GPLv2-compatible license.
What's the licensing for Gutenberg blocks? Will it be ok to publish blocks to the Wordpress Marketplace?
Since #2298 was raised, React moved to the MIT license. This is not GPL and, although they are compatible, Automattic will not accept dual licensed code in the Marketplace for either themes or plugins. Matt explained the situation in There is No Such Thing as a Split License
How does the inclusion of React (and the many licenses included in its dependencies) affect this position? If people start creating blocks will the restrictions for non-GPL code be lifted in light of Matt's strong stance on the issue?
The text was updated successfully, but these errors were encountered: