<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for OneStop Secret Sauce</title>
	<atom:link href="http://www.mikebriggs.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.mikebriggs.com</link>
	<description>Building Web Community</description>
	<lastBuildDate>Tue, 30 Mar 2010 21:22:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Stale Content is our Enemy by The thorny issue of archival content on the intranet - Intranet Blog - ThoughtFarmer</title>
		<link>http://www.mikebriggs.com/?p=15&#038;cpage=1#comment-60</link>
		<dc:creator>The thorny issue of archival content on the intranet - Intranet Blog - ThoughtFarmer</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebriggs.com/?p=15#comment-60</guid>
		<description>[...] Mike Briggs of Sun had this important point in his post on stale content: keep the authors tied to their content as much as possible. The publish-and-forget anti-pattern of intranet publishing, combined with the &#8220;orphaned content&#8221; anti-pattern are harder to have happen if you keep the connection alive between content and author. You created this page, it&#8217;s your responsibility to keep tabs on it, remove it when you see fit, or pass the ownership onto someone who will. That&#8217;s a design pattern that we baked into ThoughtFarmer from the start: there is no anonymous page ownership. Page and author are always coupled together. [...]</description>
		<content:encoded><![CDATA[<p>[...] Mike Briggs of Sun had this important point in his post on stale content: keep the authors tied to their content as much as possible. The publish-and-forget anti-pattern of intranet publishing, combined with the &#8220;orphaned content&#8221; anti-pattern are harder to have happen if you keep the connection alive between content and author. You created this page, it&#8217;s your responsibility to keep tabs on it, remove it when you see fit, or pass the ownership onto someone who will. That&#8217;s a design pattern that we baked into ThoughtFarmer from the start: there is no anonymous page ownership. Page and author are always coupled together. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What&#8217;s in for Me: Why Should I Bother? by Dave Edstrom</title>
		<link>http://www.mikebriggs.com/?p=211&#038;cpage=1#comment-6</link>
		<dc:creator>Dave Edstrom</dc:creator>
		<pubDate>Mon, 11 Jan 2010 14:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebriggs.com/?p=211#comment-6</guid>
		<description>I have had the privilege of knowing Mike Briggs, Principal Field Technologist for Sun Microsystems for about 20 years.   I have never met or heard of anyone that is better than Mike Briggs in terms of building global technical communities on the web.  Far and away the most popular site at Sun Microsystems is onestop.   The name  onestop says it all.  The idea was/is that onestop is the only place you need to go to find technical information on a piece of hardware, software or any technology.

As anyone who has tried to created a global technical community knows, it is easy to have grand goals when starting a global community, then reality sets in.  The reality is that it is extremely hard to create a successful technical community for a variety of reasons.  Mike is very unique in that he has the ability to pull individuals together for a common cause, create the right balance between consistency and freedom, put in a governance mechanism that is very balanced all while having the technical ability to write whatever needs to be created to keep improving the site/experience.

Mike has recently taken on the very important challenge of making Sun&#039;s Partners part of onestop   This is very important to Sun&#039;s future.

If/when the Oracle acquisition of Sun Microsystems goes through, IMHO, there is no one more important to make sure that transition goes smoothly than Mike Briggs.  Mike is a great guy and it should be pointed out that Mike was personally recruited by Scott McNealy to work at Sun.</description>
		<content:encoded><![CDATA[<p>I have had the privilege of knowing Mike Briggs, Principal Field Technologist for Sun Microsystems for about 20 years.   I have never met or heard of anyone that is better than Mike Briggs in terms of building global technical communities on the web.  Far and away the most popular site at Sun Microsystems is onestop.   The name  onestop says it all.  The idea was/is that onestop is the only place you need to go to find technical information on a piece of hardware, software or any technology.</p>
<p>As anyone who has tried to created a global technical community knows, it is easy to have grand goals when starting a global community, then reality sets in.  The reality is that it is extremely hard to create a successful technical community for a variety of reasons.  Mike is very unique in that he has the ability to pull individuals together for a common cause, create the right balance between consistency and freedom, put in a governance mechanism that is very balanced all while having the technical ability to write whatever needs to be created to keep improving the site/experience.</p>
<p>Mike has recently taken on the very important challenge of making Sun&#8217;s Partners part of onestop   This is very important to Sun&#8217;s future.</p>
<p>If/when the Oracle acquisition of Sun Microsystems goes through, IMHO, there is no one more important to make sure that transition goes smoothly than Mike Briggs.  Mike is a great guy and it should be pointed out that Mike was personally recruited by Scott McNealy to work at Sun.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
