<?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 on: Wikis for Documentation</title>
	<atom:link href="http://battis.net/2009/11/22/wikis-for-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://battis.net/2009/11/22/wikis-for-documentation/</link>
	<description>...and I&#039;m all out of bubble gum.</description>
	<lastBuildDate>Fri, 12 Mar 2010 05:51:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Seth Battis</title>
		<link>http://battis.net/2009/11/22/wikis-for-documentation/comment-page-1/#comment-258</link>
		<dc:creator>Seth Battis</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:45:43 +0000</pubDate>
		<guid isPermaLink="false">http://battis.net/blog/?p=152#comment-258</guid>
		<description>Kind of, but I&#039;m really talking about a regular wiki (e.g. &lt;a href=&quot;http://www.wikispaces.com/site/for/teachers&quot; rel=&quot;nofollow&quot;&gt;WikiSpaces&lt;/a&gt;). Mostly, I&#039;ve been successful by trying to not manage the students too much (ironically) -- set up clear roles and responsibilities, and hold them accountable for meeting those goals. It also helps to be working on an authentic project (like the CNC lathe last spring), rather than something the students feel is contrived or artificial (building study guides is not a winner). The real trick, when the wiki seems to take off, is when I&#039;m not the source of all the answers, so they have to go out and find them. The technical underpinnings could probably work in a Google Doc as well, although linking from page to page would be clunkier.</description>
		<content:encoded><![CDATA[<p>Kind of, but I&#8217;m really talking about a regular wiki (e.g. <a href="http://www.wikispaces.com/site/for/teachers" rel="nofollow">WikiSpaces</a>). Mostly, I&#8217;ve been successful by trying to not manage the students too much (ironically) &#8212; set up clear roles and responsibilities, and hold them accountable for meeting those goals. It also helps to be working on an authentic project (like the CNC lathe last spring), rather than something the students feel is contrived or artificial (building study guides is not a winner). The real trick, when the wiki seems to take off, is when I&#8217;m not the source of all the answers, so they have to go out and find them. The technical underpinnings could probably work in a Google Doc as well, although linking from page to page would be clunkier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melissa</title>
		<link>http://battis.net/2009/11/22/wikis-for-documentation/comment-page-1/#comment-257</link>
		<dc:creator>Melissa</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://battis.net/blog/?p=152#comment-257</guid>
		<description>When you talk about Wikis here, is this similar to using a Google Doc as a shared document that multiple people can access and change?  If so, what are the ways that you have been successful in bringing groups together to use a wiki in a group project?</description>
		<content:encoded><![CDATA[<p>When you talk about Wikis here, is this similar to using a Google Doc as a shared document that multiple people can access and change?  If so, what are the ways that you have been successful in bringing groups together to use a wiki in a group project?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
