Hi Geert, thanks for your detailed mail. I didn't (still don't) know the exact size of the community. I understand that not having a stable dev-team is definitely a problem and may even forbid things like a commitment to solve "popular" feature requests per release. Yet I'm convinced that knowing what your user's want should be a central part of an open-source project like Pharo, where you are actually building a platform for other people to use and exploit. Most successful open-source projects are those that can built a strong community around them and from my point of view knowing what the community wants is an important step. I believe that if the message is "we are listening to what you want and we will try to achieve it" instead of "do it yourself" you have more chances of creating a healthy community. Cheers, Andrés