Most of the time your users will become your contributors. That's mostly true for libraries targeted at developers, but even if you build software for non-techn

Most of the time your users will become your contributors. That's mostly true for libraries targeted at developers, but even if you build software for non-technical users some of them will be developers and will eventually contribute. Don't expect your community to build large features for you, even though that happens from time to time my experience is more that most people contribute small patches and improvements. That's great too because the small things can be quite time-consuming, so if your community has your back on things like documentation or translations it can help a lot. One of our latest open-source projects is Klaro (https://github.com/kiprotect/klaro https://github.com/kiprotect/klaro), an open-source consent manager for websites. We already got some really great contributions from our community, most people that contributed did so to solve a problem they had with the software (e.g. missing translations) or to build something they wanted for themselves. We don't accept all PRs but if they are in line with our development goals we're happy to merge them.