I realize that you guys are very busy fixing bugs in the current release, but the inability of folks to have their patches accepted upstream is one way to kill off interest in having people develop patches at all.

There are something like 50 issues in ZBXNEXT which are sitting in open state and have patches (searching for 'project = "ZABBIX FEATURE REQUESTS" and comment ~ "patch" and status != Closed ORDER BY updatedDate' shows 76 issues). Some of them date back to 2007, 2008, etc... so they may not be relevant any more. Most of them have not been actioned at all by development.

It would be nice if someone would at least look all the tickets with patches and say, they won't be adopted for whatever reason...

Obviously, I have my own interests at play here wanting to get the patch for ZBXNEXT-384 to uniquely identify alerts adopted, so I can have tickets automatically created in JIRA with unique email subjects without needing to patch and rebuild each release of Zabbix. But there are probably some real gems in the bunch... take "ZBXNEXT-599 - Logarithmic scale for Y-axis in graphs", which would have helped to show performance issues off to management.

Anyway, I'm not sure what can be done about this... perhaps new issues should be "Unassigned" rather then assigned to Alexei Vladishev (who's probably too busy leading the company and the bug fixing efforts to screen them), or maybe there should be a community developer recruited to look at them and bring them to the attention of the dev team.