About 5-6 years ago, when free and/or open source blog software was robust enough to handle small magazine or newspaper sites, I started using them for that purpose. However, they really needed to be hacked up to work well for multi-user, multi-author workflow and certain other features. I was surprised at this, because their whole conceptual architecture was that of journal/newspaper publishing.
Now things have improved a bit, but the main CMSes I use to develop media and other websites still have not been adopted or developed from the standpoint of journalist/ic enterprises. Further, they have been somewhat behind the curve with web 2.0 and social networking features--the whole CMS architecture is too traditional, too newspapery, and needs to be fundamentally reconsidered from the standpoint of social media/social publishing, IMHO.
Regrettably I still see no real journalistic application focus or orientation in FOSS CMS developer circles. Am I missing something? If not, is this a real need? If so, how might it be filled?
The main CMS I deploy these days is Joomla. It beats the alternatives for most clients' needs, from the pragmatic standpoint of giving them the most for their money and something that is easy to use. However, it has some serious failings, especially for newspapery/zine-type sites. On the other hand, Drupal is good in the areas where Joomla is weak and yet weak where Joomla is strong. That's frustrating, and it puzzles me that both (especially Drupal) are in such wide circulation without being impacted by the demands or needs that to me seem pretty common and obvious. Perhaps this is due to a common FOSS cultural tic: overselling by techie enthusiasts who think their favorite CMS can do anything because they can hack it to do anything. (Sort of.) They are not thinking about the practical and long-term needs of most (non-technical) users.
I think Drupal may have the potential to become the publishing CMS I've always wanted, but I have no reason to believe it will be taken in that direction. Wordpress is probably closer and more to my tastes and common uses. It's been a while since I used MovableType, but it was pretty solid when I did use it, and it may be sneaking back up on me as something I'll go back to. My loyalty is to what works well for a particular project and the people who will be using the platform long-term.