Sorry, but the “community needs” are really, really clear after all the criticism and discussions in the last months.
The problem here are the non-saying marketing responses to all the criticism, not that you don’t know what the community really concerns.
But to help you a bit:
- to enable group calls again there shouldn’t be the need to manually build the whole binary. Just add an option in config.json, as you do for all the other settings
- to reset/disable the hard user limit there shouldn’t be the need to manually build the whole binary. Just add an option in config.json, as you do for all the other settings
- let the playbooks plugin free to use for anyone with the basic functions as in the last years
- generally: don’t paywall stuff that has been free for all to use since now and then! If you want to add more value to the enterprise edition, just develop new fancy features for enterprise-only
- make a clear statement what to expect for community edition users. Will you paywall more stuff? Will the restrictions become harder? Or will you even degrade the community edition to a “staging build for enterprise edition” that isn’t really usable in a production environment for anybody anymore?
Just communicate transparently what your plans for the next years and decades are and don’t argue with your focus on critical infrastructure and such stuff. This focus is new since 2024 and really no argument, why you have to paywall stuff for “quality reasons” or any other (sorry) bullshit arguments.