http://tlf.disqus.com/The Technology Liberation Front is the tech policy blog dedicated to keeping politicians' hands off the 'net and everything else related to technology.enWed, 04 Nov 2009 10:52:19 -0000https://techliberation.com/2009/11/03/2009-open-source-cms-report-by-water-stone/#comment-21860990<p>You should see my recent comments to Tim Lee, reposted here <a href="http://timothyblee.com/?p=1432" rel="nofollow noopener" target="_blank" title="http://timothyblee.com/?p=1432">http://timothyblee.com/?p=1432</a> as a post with his comments, that illustrate why I believe there is a bias against free software specifically in the free market non-profit community. The advocates of free software often use highly charged language and try to turn an engineering question into a political one. That politicizing has made a lot of folks suspicious of open source, something that has set advocates of freedom behind because, as you say, money has been wasted on closed-source technologies that don't stack up to open software.</p>cordblomquistWed, 04 Nov 2009 10:52:19 -0000https://techliberation.com/2009/11/03/2009-open-source-cms-report-by-water-stone/#comment-21812332<p>We actually develop sites for clients using both open source content management systems and custom proprietary systems.</p><p>Systems like Drupal, Joomla, and WordPress are good options when a client needs something that doesn't conflict with the basic assumptions made by the software's development community (who are catering to a general user base). If a client is willing to stay within the lines, then they can usually get 95% of what they want or need for 40% of the comparative cost. This is the preferred way of doing things whenever it will help realize the basic objectives of the project.</p><p>Sometimes, however, clients have a very particular way they need things maintained. It could be because of a need to manage a large number of idiosyncratic data-relationships. It could be the result of a very specialized internal workflow. Sometimes it's just bullheadedness on the part of an executive decisionmaker. In these situations, it's often better to go the custom route. Trying to use an open source CMS when it's not appropriate can be not only very messy, but much more expensive to maintain than a well-built custom solution.</p><p>To make sure you don't get burned, find a vendor who is both familiar with open source systems and able to identify when they are and are not appropriate. To put it another way: vendors who only work with open source content management systems tend to see every problem as a nail; vendors who never use them tend to see you as an easy mark.</p>PJ DolandTue, 03 Nov 2009 18:52:50 -0000