17 Jun
2018
17 Jun
'18
10:08 a.m.
On 06/17/2018 04:35 AM, bill-auger wrote:
i suspect this concern is a bit belated - it probably
goes back to the release
of JUCE v5 in april 2017 - i dont think anything has changed since then - quite
a fuss was made at the time like starting the very next day
the GPL is still an option but it was removed from mention on the website and
now is essentially a secret - new users need to actually download and read the
source code or download and run the binary to learn that the GPL was an option
i could point you to this discussion that tried to address the down-playing of
the GPL option and the possibility of a community fork to remove the anti-
features
https://forum.juce.com/t/should-the-community-consider-a-juce-fork/22056
You can use my fork which is pure GPLv3: https://github.com/DISTRHO/Juce
I removed the tracking from the "IDE" (ProJucer) and also the
tracking+watermark that gets exported per each plugin.