Hi Michael, thank you very much for the answer, but if the site belongs to the community then it is only fair that the community vote what is most relevant to the community itself.



Of course, the final decision always comes from the Appeon, but if something has a lot of votes from the community, suddenly it is worth investing in the suggestion.



I understand the importance of MVPs, but they are few compared to the number of people in the community.



And I don't see much point in opening a bug to be analyzed later if it is an improvement or a bug.

Every community member can vote up/down on every Q&A entry and rate every article. So voting is there.

Appeon integrated improvements and bug reports into a common workflow for us customers to follow. I favor that over forcing me to make uninformed upfront decision on whether my incident is bug or improvement.

I experience Appeon shapes its products based on customer feedback combined with strategic product direction. Following this thread and the community in general. Reacting to bug reports and e-mails. Participate in user groups. Arrange conferences.