Announcing ADCx San Francisco, a one-day Audio Developer Conference pop-up on May 15th, 2023
Designed as a one-day audio developer conference pop-up, ADCx is a hybrid in-person and online event. ADCx will include a full day of inspiring audio developer talks and networking events. All ADCx talks will be in-person and streamed online. Our first ADCx event will be in San Francisco on May 15, 2023, at The Commonwealth Club headquarters.
Talks at ADCx range from audio research to professional practices, to standards in audio development, as well as talks about application areas and career development. Experimental projects are welcome. ADCx talks are in a shorter 18-minute format allowing for a variety of topics and speakers during the one-day event.
Why do you have such a strong conviction that the JUCE team is not focused on JUCE development?
You seem to be making an assumption that the JUCE team’s resources are spent “handling” conferences rather than improving the framework on the basis of a small number of posts on the forum. The bulk of the ADC organisational work is done through an extremely generous donation of time from PACE employees and paid contractors who are funded by ADC ticket sales and sponsorship. We attend ADC, and contribute workshops and talks to the programme, but this is something we would be doing irrespective of the ownership of ADC, and engaging with the community in this way is a fairly unambiguous net benefit to JUCE.
IMHO frustrations recur periodically due to the lack of a clear roadmap (and a well managed issue tracker). Development of the JUCE framework is rather opaque. Interaction with users left messy. For instance nobody really know if we should report bugs in that forum or onto GitHub…
Even if you know, where you should report, the problem is, that from there is no standard procedure. No funneling to bring duplicates together. Often no response at all, no chance to know if it is being worked, forgotten or rejected.
Feature requests are voted, but there is neither a commitment that above a certain threshold it is guaranteed to be adressed, nor if it is considered at all.
I realise I sound much more frustrated than I actually am, but I can remember the situations that come back when reading this thread.
I think a dedicated communications person would be an amazing contribution to the team. Or an issue tracker, but I realise that won’t happen.