Personal license - shared JUCE modifications

Sorry if this seems elementary, but I don’t play with licensing.
I have a GitHub fork of JUCE that I use in a GPL project of mine, where I added one function. It’s available to everyone.
I now want to make a few more modifications to that same fork in order to use it in a closed source project, using a Personal license. I am not 100% sure if I want to GPL this second project, but I’m leaning towards no.
My modifications aren’t significant and I’m fine with sharing them if it means I don’t have to have two separate modified JUCE repositories on my computer. But how does it work, if I want to use these changes in a closed-source project? My forked version is technically GPL, right?
Do I really need to clone JUCE again on my computer and keep these modifications private in order to use them in a closed-source project?
It sounds like a silly thing to do, but that’s my understanding of GPL.

1 Like

Not a lawyer (nor expert), but I believe if you’re the author of the changes then you have the right to do whatever you want with the changes you made. The license you apply to the code impacts how other people are allowed to use your code.

1 Like