<?xml version="1.0" encoding="us-ascii"?>
<rss version="2.0" xml:base="http://www.cmswatch.com" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
   <channel>
      <title>CMS Watch Socialtext Feed</title>
      <link>http://www.cmswatch.com</link>
      <description>CMS Watch headlines about Socialtext</description>
      <language>en-us</language>
      <lastBuildDate>Wed, 19 Nov 2008 10:14:59 -0500</lastBuildDate>
      <dc:creator>editor@cmswatch.com (Tony Byrne)</dc:creator>
      <dc:rights>Copyright 2005, CMS Watch</dc:rights>
      <dc:publisher>CMS Watch</dc:publisher>
      <image>
         <title>CMS Watch</title>
         <url>http://www.cmswatch.com/images/cmswatch_logo.gif</url>
         <link>http://www.cmswatch.com</link>
         <width>82</width>
         <height>36</height>
         <description>CMS Watch logo</description>
      </image>
      <item>
         <title>Socialtext, SaaS, and upgrading enterprise wikis</title>
         <description>Noted wiki vendor &lt;a href=&quot;http://www.cmswatch.com/Social/Vendors/Socialtext&quot;&gt;Socialtext&lt;/a&gt; 
has been busy appearing at high-profile conferences to promote their concept of 
&lt;i&gt;business social software&lt;/i&gt;. However, recent experience suggests the still-young 
company may remain a little too fascinated by exciting new features rather than 
supporting and maintaining their customer base.&lt;/p&gt; 
&lt;p&gt;As we mentioned in the Socialtext review in the &lt;i&gt;&lt;a href=&quot;http://cmswatch.com/Social/Report/&quot;&gt;Enterprise 
  Social Software Report 2008&lt;/a&gt;&lt;/i&gt;, customers were concerned earlier this year 
  over quite a few upgrade problems with the hosted Socialtext service. Recent 
  reports from customers suggest that the popular service remains quite a bumpy 
  ride. Here's a few of the issues that Socialtext customers have reported over 
  the past few month: 
&lt;ul&gt;
&lt;li&gt;The one and only reporting feature in Socialtext -- weekly usage reports -- stopped working back in May&lt;/li&gt;
&lt;li&gt;The search feature was suddenly substantially changed. Now search results no longer sort by default according to last edited date, but by relevance. This may seem an improvement, but try a &lt;a href=&quot;http://www.eu.socialtext.net/web2expo/index.cgi?search_term=wiki&amp;action=search&amp;scope=_&quot;&gt;search on a public Socialtext wiki&lt;/a&gt; and you'll find that it still takes some time getting used to.&lt;/li&gt;
  &lt;li&gt;In another incremental upgrade, international characters were transformed 
    to garbage, e.g., the Danish &amp;quot;&amp;aelig;&amp;quot; became an &amp;quot;&amp;Aring;l&amp;quot; 
    and &amp;quot;&amp;aring;&amp;quot; became &amp;quot;&amp;Aring;&amp;yen;.&amp;quot;&lt;/li&gt;
 &lt;/ul&gt;
&lt;p&gt;It is also worth adding that while Socialtext formally announced version 3 back in April, the hosted service is today still running version 2.22, almost 5 months later.&lt;/p&gt;
&lt;p&gt;The larger issue here is that as a SaaS customer you remain very much in the 
  hands of the vendor. Often that's a good thing (&amp;quot;our upgrades happen automatically&amp;quot;); 
  sometimes it's a bad thing (&amp;quot;we can't chose to postpone an upgrade&amp;quot;). 
  How well your SaaS vendor prepares you and performs proper regression testing 
  may seriously impact your project. Enterprises don't like surprises, but it 
  appears like Socialtext still has some way to go here</description>
         <link>http://www.cmswatch.com/Trends/1344-Socialtext,-SaaS,-and-upgrading-enterprise-wikis?source=RSS</link>
         <category>Enterprise Social Software</category>
         <author>info@jboye.dk(Janus Boye)</author>
         <pubDate>Mon, 25 Aug 2008 18:11:00 -0400</pubDate>
      </item>
      <item>
         <title>When a Wiki package gets too real</title>
         <description>In talking to wiki users, we find a wide range of sophistication. Some are 
  quite content with the simplistic &amp;quot;edit this page&amp;quot; features you can 
  now find in most &lt;a href=&quot;http://www.cmswatch.com/CMS/&quot;&gt;Web CMS&lt;/a&gt; and &lt;a href=&quot;http://www.cmswatch.com/Social/&quot;&gt;Social 
  Software&lt;/a&gt; suites, while other customers seek more advanced features (such 
  as topical refactoring and advanced aggregation and print services) that constitute 
  for them a &amp;quot;real&amp;quot; wiki.&lt;/p&gt;
&lt;p&gt;And then there are those who cut their teeth editing Wikipedia pages or learned 
  about wikis by using the earliest tools. They come with a particular set of 
  expectations -- especially around using good old fashioned &amp;quot;&lt;a href=&quot;http://en.wikipedia.org/wiki/Wikitext&quot;&gt;Wikitext&lt;/a&gt;&amp;quot; 
  mark-up -- that today are met largely through the &lt;a href=&quot;http://www.cmswatch.com/Social/Vendors/MediaWiki&quot;&gt;MediaWiki&lt;/a&gt; platform, the same 
  tool that powers Wikipedia. &lt;/p&gt;
&lt;p&gt;As &lt;em&gt;&lt;a href=&quot;http://www.cmswatch.com/Social/Report/&quot;&gt;Enterprise Social Software 
  Report&lt;/a&gt;&lt;/em&gt; readers know, MediaWiki tends to find favor among wiki purists, 
  but is often perceived as too arcane by novice users. Here's a &lt;a href=&quot;http://www.quis.com/2008/07/16/why-mediawiki-is-not-the-right-wiki-product-for-my-clients&quot;&gt;nice 
  summary of some relevant issues by consultant Dan Katz&lt;/a&gt;. (Thanks to &lt;a href=&quot;http://www.cmswatch.com/Analyst/8-Boye&quot;&gt;Janus&lt;/a&gt; 
  for the link.)&lt;/p&gt;
&lt;p&gt; I'm more sanguine about open source wiki options and less enthusiastic about 
  &lt;a href=&quot;http://www.cmswatch.com/Social/Vendors/Socialtext&quot;&gt;Socialtext&lt;/a&gt; than 
  Katz, but he makes some very good points regardless of the tool you select. 
  The key for you the customer is, as always, to test with &amp;quot;real&amp;quot; users 
  before you deploy... </description>
         <link>http://www.cmswatch.com/Trends/1315-When-a-Wiki-package-gets-too-real?source=RSS</link>
         <category>Enterprise Social Software</category>
         <author>tbyrne@cmswatch.com(Tony Byrne)</author>
         <pubDate>Mon, 21 Jul 2008 14:46:00 -0400</pubDate>
      </item>
      <item>
         <title>Announcing the Enterprise Social Software Report 2008</title>
         <description>The full name is actually &lt;em&gt;&lt;a href=&quot;http://www.cmswatch.com/Social/Report/&quot;&gt;Enterprise Social Software Report 2008: Networking 
  &amp;amp; Collaboration Within and Beyond the Enterprise&lt;/a&gt;&lt;/em&gt;. Enterprises are increasingly 
  using social tools -- some new, some not so new -- within and beyond enterprise boundaries.  As one side effect, those boundaries are increasingly blurring, even though
  vendors still find it difficult to satisfy both internal and external scenarios.&lt;/p&gt;
&lt;p&gt;The report evaluates &lt;a href=&quot;http://www.cmswatch.com/Social/Vendors/&quot;&gt;20 Social 
  Software vendors&lt;/a&gt; against eleven common scenarions, weighing in at about 400 pages. Turns out there are a 
  lot of differences among vendors and approaches. The tools may espouse a light 
  touch, but many of the architectures are far from trivial. Our &lt;a href=&quot;http://www.cmswatch.com/About/Press/200806ESSR/&quot;&gt;media release today 
  highlights just one potential challenge&lt;/a&gt; you may face implementing at an enterprise 
  level: the general dearth of system services (like configuration management) 
  across this space. &lt;/p&gt;
&lt;p&gt;The report is &lt;a href=&quot;http://cmsworks.stores.yahoo.net/essr.html&quot;&gt;available for pre-order&lt;/a&gt; today. &lt;a href=&quot;http://www.cmswatch.com/Reports/Subscriptions/&quot;&gt;Subscribers&lt;/a&gt; will receive their 
  copy in a week or so when the official version gets burned out.</description>
         <link>http://www.cmswatch.com/Trends/1270-Announcing-the-Enterprise-Social-Software-Report-2008?source=RSS</link>
         <category>Enterprise Social Software</category>
         <author>tbyrne@cmswatch.com(Tony Byrne)</author>
         <pubDate>Wed, 11 Jun 2008 00:00:00 -0400</pubDate>
      </item>

   </channel>
</rss>

