Request to relicense to "GPL 2.0 or later"

[simaotwx]

This library is used in a WordPress plugin: https://github.com/publishpress/PublishPress-Planner/blob/a4a52f92eb6c972a3b7c590ebbcfb4a0cb6b1c96/composer.lock#L10096

The WordPress plugin is licensed as GPLv2 or later: https://github.com/publishpress/PublishPress-Planner#license

However, this has no effect because the usage of this library would require everything to be licensed as GPLv2 or compatible. It's not possible to use a GPLv2 component in a GPLv3 context, whereas GPLv2-or-later is allowed.

This means that when another plugin is licensed as GPLv3, then using PublishPress Planner is no longer allowed because of the license clash.

Here are the corresponding issues:
publishpress/PublishPress-Planner#1237
lucatume/wp-browser#600

As short-term solution (until there is a better one), it would be easiest, if this library was relicensed to "GPL 2.0 or later" instead of "GPL 2.0 only" (see https://github.com/vria/nodiacritic/blob/0eb3cafbca8ac1b478bd4dabe0666d8b0d3cba6c/LICENSE and

nodiacritic/composer.json

Line 7 in 0eb3caf

"license": "GPL-2.0",

)

[mpoiriert]

@simaotwx Have you found a alternative ? Another library that does the same thing ?
Because we have an licence issue as well. I was trying to find something more permissive like MIT.
It's not for a WordPress plugin in our case so we have more control over the integration.

[mpoiriert]

Never mind we were not using it anymore (event if it was installed) and symfony/string provide the same feature

[simaotwx]

@mpoiriert Since, in our case, this was just a dev dependency, we decided to disregard the issue.