Please use GPLv3.0+ instead of GPLv3.0-only license

[falkTX]

Hi there,
I have noticed that all of your projects are licensed as GPLv3.0-only, instead of the more common GPLv3.0+
Is there a reason for this?

If one wants to integrate your code into another open-source project, the only license possible would be GPLv3.0, which is not very nice...
If using GPLv3.0+ we could mix it together with GPLv2.0+ and future GPLv4, v5 etc

Using GPLv3.0-only as the code license is problematic going forward, if GPLv4 ever gets released.
(GPLv4 supposedly will add restrictions for AI scrappers, like done on GitHub, stuff that reads code and "generates" new stuff via AI. Currently GPL does not provide anything against it)

Is this something you would be willing to change? I can answer license related questions if you have any, since I have been dealing with those for a long time (but FYI I am no lawyer, just an open-source developer and packager)

The target is to include your modules in a 100% open-source and free VCV plugin version
See DISTRHO/Cardinal#1 for details and news

If you do not want to change the license, please let me know, I will promptly remove your modules/code from the Cardinal project.

PS: Aria was really awesome and already did the update, can be seen at AriaSalvatrice/AriaModules@484bea3
There is also a similar issue at Tonecarver/tcRackModules#7

[falkTX]

Small addition here, might be worth mentioning that https://vcvrack.com/manual/PluginLicensing recommends using gplv3+ as well.

[MarcBoule]

Hi, after talking it over with my colleague with whom I manage this project, were going to stay with the current lisence for the time being. Yet we will consider making the change in a near future according to how things develop with Cardinal.

[jypma]

Have there been any further thoughts on this? Geodesics is one of the most popular modules still missing from Cardinal, and it would be awesome to see it included.

Can you share some of the arguments of preferring GPLv3.0-only over GPL-3.0-or-later? I expect this can be helpful when discussing with other module authors as well.

[MarcBoule]

No further thoughts at this time unfortunately. We'll keep the issue open and let you know when we have more to say on this.

[mpicard]

Has anything changed or updates on this?

[MarcBoule]

Not that I know of, but the person deciding this is Pierre (aka Pyer), so perhaps it's best if you contact him directly: [email protected]