We have many feature requests that have build up over the years, some for a niche thing others for something that would benefit many users. Many have been implemented but enough remain to be a significant number. And from one perspective every open issue is one too many. But I've learned over the years that not everything can be solved. I speak of 'we' as in the wider group of ISPconfig users, not only the developers. I personally count myself somewhere in between. I do supply patches every now and then, but do not have the time to closely follow development. Not all users understand how it works in free software, but as long as we're not paying a yearly fee we can't expect development to do happen like magic. (True, even with commercial products you often have very little influence) ... but here someone spends their own time. I assume that most develop it because they have a personal benefit from it, either for work or private hosting. Motivation can go a long way but some changes are more interesting than others. The best way to get your need fixed is still to do it yourself... or hire someone who has the right skills. Then you are in full control to dedicate time to get things done.... (as long as you can convince others that it's an improvement overall). Besides that someone has to be motivates to do the work. The founder of the Drupal project has several in-depth blog posts about this topic on https://dri.es/ e.g. https://dri.es/balancing-makers-and-takers-to-scale-and-sustain-open-source can be worth the read. How can we motivate our community to keep improving, and maybe even accelerate. There have been many bounty and fund raising systems. These have come and gone with varying degrees of success. Patreon.com seems to be in the lead these days. (at least in my filter bubble) There are some recurring revenue streams going into the project. What we have: ISPprotect HowtoForge subscriptions which give access to ISPConfig 3 Priority Support forum Business Support on https://www.ispconfig.org/get-support/ Billing module Migration toolkit I'm not sure how much developer time that pays for... but maybe we should promote the 'Business Support' page when there is a feature request in the forum or on Gitlab? Some other options are: bug bounties? tip jar Patreon Paid plan (with some form of support offer) Raising some awareness on 'bug tasks' to raise funding and rally users. Raising funds in the free software world is not easy, but we can do it! My goal with this post is to start a discussion. It may give some negative reactions when a feature request is met with a link to a funding system but maybe it will also help to set a realistic view of how much effort it takes to maintain a piece of software. Thanks to all who have contributed to this great piece of software so fare.