<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: On Microsoft Sharepoint, wikis: Atlassian and Socialtext</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<pubDate>Tue, 14 Oct 2008 17:14:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: People Over Process &#187; Acquia - A Commercial Company for Drupal</title>
		<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-267995</link>
		<dc:creator>People Over Process &#187; Acquia - A Commercial Company for Drupal</dc:creator>
		<pubDate>Tue, 08 Jan 2008 23:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-267995</guid>
		<description>[...] it&#8217;s easy to shove any open source web page management thing (a CMS ;&#62;) in front of the SharePoint train to see what happens. SharePoint, of course, is more focused on behind-the-firewall content [...]</description>
		<content:encoded><![CDATA[<p>[...] it&#8217;s easy to shove any open source web page management thing (a CMS ;&gt;) in front of the SharePoint train to see what happens. SharePoint, of course, is more focused on behind-the-firewall content [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene Lee</title>
		<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-210849</link>
		<dc:creator>Eugene Lee</dc:creator>
		<pubDate>Wed, 21 Nov 2007 06:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-210849</guid>
		<description>Hi James - Eugene Lee here.  I'm "CEO 2.0" for Socialtext, but you and I met during my previous gig with Adobe.  Would be happy for Ross and I to update you if you are still interested.</description>
		<content:encoded><![CDATA[<p>Hi James - Eugene Lee here.  I&#8217;m &#8220;CEO 2.0&#8243; for Socialtext, but you and I met during my previous gig with Adobe.  Would be happy for Ross and I to update you if you are still interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgovernor</title>
		<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177922</link>
		<dc:creator>jgovernor</dc:creator>
		<pubDate>Fri, 19 Oct 2007 19:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177922</guid>
		<description>great stuff danno. it would be cool to chat some more about your experiences.

Hi Ross. Its good to meet you, too. I didn't want to make too many assumptions about your business but would like to catch up soon to hear more.</description>
		<content:encoded><![CDATA[<p>great stuff danno. it would be cool to chat some more about your experiences.</p>
<p>Hi Ross. Its good to meet you, too. I didn&#8217;t want to make too many assumptions about your business but would like to catch up soon to hear more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Mayfield</title>
		<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177706</link>
		<dc:creator>Ross Mayfield</dc:creator>
		<pubDate>Fri, 19 Oct 2007 13:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177706</guid>
		<description>Hi James --

Good to meet you.  I apologize for not introducing you to Socialtext earlier.

The interesting thing is that Socialtext is a LAMP stack commercial open source offering.  With SocialPoint and Sharepoint, similar to your point above, this is validation of a Best-of-Breed offering from a different culture and platform.  

Socialtext Open is available from an OSI Certified Open Source License, the Common Public Attribution License that we pioneered.  I would point this out as a difference if two of Microsoft's licenses didn't just go through the certification process.  

Zoli is right that a primary benefit of having SocialPoint is removing barriers for Sharepoint shops.  But from the customers and prospects I met at the Microsoft Global CIO Summit last month, the interesting conversation is beyond the barrier in delivering a real and adoptable business solution.

Yes, we have to continue to execute, as being first isn't enough.  I'm glad you remembered us and look forward to our first conversation.

Ross</description>
		<content:encoded><![CDATA[<p>Hi James &#8211;</p>
<p>Good to meet you.  I apologize for not introducing you to Socialtext earlier.</p>
<p>The interesting thing is that Socialtext is a LAMP stack commercial open source offering.  With SocialPoint and Sharepoint, similar to your point above, this is validation of a Best-of-Breed offering from a different culture and platform.  </p>
<p>Socialtext Open is available from an OSI Certified Open Source License, the Common Public Attribution License that we pioneered.  I would point this out as a difference if two of Microsoft&#8217;s licenses didn&#8217;t just go through the certification process.  </p>
<p>Zoli is right that a primary benefit of having SocialPoint is removing barriers for Sharepoint shops.  But from the customers and prospects I met at the Microsoft Global CIO Summit last month, the interesting conversation is beyond the barrier in delivering a real and adoptable business solution.</p>
<p>Yes, we have to continue to execute, as being first isn&#8217;t enough.  I&#8217;m glad you remembered us and look forward to our first conversation.</p>
<p>Ross</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danno</title>
		<link>http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177680</link>
		<dc:creator>Danno</dc:creator>
		<pubDate>Fri, 19 Oct 2007 13:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/10/19/on-microsoft-sharepoint-wikis-atlassian-and-socialtext/#comment-177680</guid>
		<description>Heh, nifty, I actually have some first hand experience to talk about for once.

Atlassian is, from the experience with Wikis that I have, pretty badass.  The capacity to switch between wysiwyg and textile formatting along with the general interface makes it *way* nicer to use than MediaWiki.  The install that my company is running has a lot of very useful plugins an widgets installed.  In particular, my group is exploiting the watch tracker to keep a list of who is interested in the services we provide.

However, it's got at least one boneheaded, fundamental drawback: the wiki's email integration support is garbage.  Our wiki admin and I scoured their plugin repository and documentation for some way to send digest emails for watches to an arbitrary email address (my team wants to monitor changes to our wiki, so we want daily changes sent to our team email list) and we found *nuthin*.  

I thought that this would be offset by the fact that an individual user can get a  daily summary of changes to pages, but what I failed to notice is that the daily summary is for EVERY page that the user has view access to. Since everyone in the corporation has access access to most pages, that email is miles long.</description>
		<content:encoded><![CDATA[<p>Heh, nifty, I actually have some first hand experience to talk about for once.</p>
<p>Atlassian is, from the experience with Wikis that I have, pretty badass.  The capacity to switch between wysiwyg and textile formatting along with the general interface makes it *way* nicer to use than MediaWiki.  The install that my company is running has a lot of very useful plugins an widgets installed.  In particular, my group is exploiting the watch tracker to keep a list of who is interested in the services we provide.</p>
<p>However, it&#8217;s got at least one boneheaded, fundamental drawback: the wiki&#8217;s email integration support is garbage.  Our wiki admin and I scoured their plugin repository and documentation for some way to send digest emails for watches to an arbitrary email address (my team wants to monitor changes to our wiki, so we want daily changes sent to our team email list) and we found *nuthin*.  </p>
<p>I thought that this would be offset by the fact that an individual user can get a  daily summary of changes to pages, but what I failed to notice is that the daily summary is for EVERY page that the user has view access to. Since everyone in the corporation has access access to most pages, that email is miles long.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
