You’re right, it’s better to pick a project the community cares about, but the problem we have is that there are a few people who are vocal here and they don’t necessarily represent the views of the wider community.
HOWEVER, just because a project or feature doesn’t feel important to the larger group doesn’t mean it isn’t important… it may not be initially important but it can grow in importance. Conversely, a feature that seemed important at the time may end up not being all that useful or commonly used.
I think Plone has to continue getting new features that please content editors and site managers. This means some of the UI improvements we put into CastleCMS should be backported to Plone. It means that we need more innovations in making Plone easier to use to edit and organize content. If we can include new features that integrate analytics and hot spot measurement and other “advanced” user tracking features then we can sell Plone into more sophisticated advertising/marketing/branding projects.
I think the underlying technology is good and stable, as long as the Python 3 work being done is finished in time. It’s hard to sell underlying technology, so new “behind the scenes” features are a low priority, especially since many of us are able to scale Plone quite nicely as it is.