This post has been updated to reflect the outcome of discussion below.
When visiting the JUCE website, it is increasingly difficult to find mention of the open source code and licensing. Rather, the marketing language is oriented towards the commercial licensing options.
Note: after discussion, the above concern still remains. It may be something to be worked out with the JUCE marketing and website management team alongside a JUCE community advocate.
When one does manage to find the open source repository, they are immediately informed that the code has additional terms and conditions, such as requiring the acceptance of a privacy policy permitting data collection from downstream users. These additional terms and conditions seem to be incompatible with the spirit and definitions of Free Software and Open Source Software. Furthermore, the main repository now contains code that has long been known to be incompatible with any free/open source project, namely the Steinberg VST SDK.
Note: The concern about the README still stands, but with better understanding. It was agreed that it would be useful to describe more clearly how GPL projects are exempted from the End User Agreement and Privacy Policy, which is mentioned in source code headers. It has also been explained that downstream developers are responsible for removing any GPL incompatible code, namely the Steinberg VST2 SDK from their projects, since JUCE is merely distributing the SDK with permission from Steinberg for convenience of developers.
Note: the following statement is in error, and was clarified in further discussion.
It is a shame, as in videos from even one year ago JUCE seemed to be a mature open source project with a thriving community. Even the commit history for the main repository has dwindled considerably in the past year.
Note: the following statement is also better understood. However, I am not the only person with these concerns.
What is going on with this project? Should we look for alternative frameworks for open source audio development?