Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License challenge with nodiacritic (GPLv2) #1237

Closed
simaotwx opened this issue Jan 16, 2023 · 4 comments
Closed

License challenge with nodiacritic (GPLv2) #1237

simaotwx opened this issue Jan 16, 2023 · 4 comments

Comments

@simaotwx
Copy link

simaotwx commented Jan 16, 2023

Is your feature request related to a problem? Please describe.
The license requirement of GPL-2.0 in the nodiacritic library (see https://github.com/publishpress/PublishPress-Planner/blob/development/composer.lock#L10096) is problematic for WordPress instances where GPL-3.0 components are used since the GPLv2 is not forward-compatible to the GPLv3 unless it is licensed "GPLv2 or later".

Describe the solution you'd like
I'd like this dependency to be either removed, rewritten or relicensed to allow distribution with GPLv3.

Describe alternatives you've considered
The alternative is to not use PublishPress when GPL-3.0 components are used.

Additional context
Using WordPress in a business means that we must comply with license requirements. Using GPL-3.0 components implies licensing everything as GPL-3.0. But that is only possible when "GPLv2 or later" or "GPLv3" is used.

@simaotwx simaotwx changed the title License challenge with nodiacritics (GPLv2) License challenge with nodiacritic (GPLv2) Jan 16, 2023
@stevejburge
Copy link
Member

OK, thanks for letting us know, @simaotwx

We'll take a look to see what alternatives are feasible and available.

@simaotwx
Copy link
Author

Any news on this topic so far? Thank you

@stevejburge
Copy link
Member

stevejburge commented Jan 30, 2023

Hi @simaotwx

Sorry, not yet. I'll be honest and say that I see problem, but with everything on our team's plate, I don't expect a super-quick resolution to this.

@simaotwx
Copy link
Author

@stevejburge alright, thank you!

@publishpress publishpress locked and limited conversation to collaborators Jan 30, 2023
@stevejburge stevejburge converted this issue into discussion #1369 Jan 30, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants