<?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: Wikis, Patterns, and Happy Customers</title>
	<atom:link href="http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/feed/" rel="self" type="application/rss+xml" />
	<link>http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/</link>
	<description>The Library Status Quo Must Go!</description>
	<pubDate>Thu, 20 Nov 2008 21:21:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Emily</title>
		<link>http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-460</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Fri, 10 Aug 2007 18:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-460</guid>
		<description>Yes, I agree. I have a real tendency to over engineer. sometime s you just have to let go. :)</description>
		<content:encoded><![CDATA[<p>Yes, I agree. I have a real tendency to over engineer. sometime s you just have to let go. <img src='http://libraryrevolution.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meredith</title>
		<link>http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-459</link>
		<dc:creator>Meredith</dc:creator>
		<pubDate>Fri, 10 Aug 2007 18:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-459</guid>
		<description>Great post. 

When I saw that Wikipatterns site a few months ago, it really clicked for me. I'd been seeing those tendencies on many of the wikis I'd created (and some I'd just observed the development of), and it was nice to know that it wasn't just me who was witnessing those very specific behavioral patterns. It's so tempting when you create a wiki to over-engineer it, to add tons of content, when there is a fine line to be drawn between seeding and "doing it all."</description>
		<content:encoded><![CDATA[<p>Great post. </p>
<p>When I saw that Wikipatterns site a few months ago, it really clicked for me. I&#8217;d been seeing those tendencies on many of the wikis I&#8217;d created (and some I&#8217;d just observed the development of), and it was nice to know that it wasn&#8217;t just me who was witnessing those very specific behavioral patterns. It&#8217;s so tempting when you create a wiki to over-engineer it, to add tons of content, when there is a fine line to be drawn between seeding and &#8220;doing it all.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stewart Mader</title>
		<link>http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-457</link>
		<dc:creator>Stewart Mader</dc:creator>
		<pubDate>Thu, 09 Aug 2007 18:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://libraryrevolution.com/2007/08/07/wikis-patterns-and-happy-customers/#comment-457</guid>
		<description>Emily,
Thanks for sharing your thoughts on Wikipatterns! I'm glad to hear that it's been helpful to you, and helps fill that need for information on how to make - and keep - your wiki successful. If you haven't already, feel free to contribute some of your own ideas, patterns, and examples to the site. Thanks for your support!

Cheers,
Stewart Mader
Wiki Evangelist, Atlassian</description>
		<content:encoded><![CDATA[<p>Emily,<br />
Thanks for sharing your thoughts on Wikipatterns! I&#8217;m glad to hear that it&#8217;s been helpful to you, and helps fill that need for information on how to make - and keep - your wiki successful. If you haven&#8217;t already, feel free to contribute some of your own ideas, patterns, and examples to the site. Thanks for your support!</p>
<p>Cheers,<br />
Stewart Mader<br />
Wiki Evangelist, Atlassian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
