<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Change &#187; googledocs</title>
	<atom:link href="http://change.bbvx.org/tag/googledocs/feed/" rel="self" type="application/rss+xml" />
	<link>http://change.bbvx.org</link>
	<description>Musings of a sometime AAUW member</description>
	<lastBuildDate>Thu, 22 Jul 2010 15:39:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>DRAFT &#8211; Policies of the AAUW Tar Heel Branch</title>
		<link>http://change.bbvx.org/2009/05/321/</link>
		<comments>http://change.bbvx.org/2009/05/321/#comments</comments>
		<pubDate>Thu, 14 May 2009 15:38:45 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[Public]]></category>
		<category><![CDATA[Structure]]></category>
		<category><![CDATA[googledocs]]></category>

		<guid isPermaLink="false">http://change.bbvx.org/2009/05/321/</guid>
		<description><![CDATA[Discussion here has moved to the branch web site &#8212; tarheel.aauwnc.org. Posting here was only an expedient step since when I wanted an initial review, it was easier to use the Google doc option &#8220;post to blog&#8221; rather than logout, login as the owner of the document, and publish through the Google interface.]]></description>
			<content:encoded><![CDATA[<p>Discussion here has moved to the branch web site &#8212; <a href="http://tarheel.aauwnc.org">tarheel.aauwnc.org</a>.</p>
<p>Posting here was only an expedient step since when I wanted an initial review, it was easier to use the Google doc option &#8220;post to blog&#8221; rather than logout, login as the owner of the document, and publish through the Google interface.</p>
]]></content:encoded>
			<wfw:commentRss>http://change.bbvx.org/2009/05/321/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lessons learned on Google Docs</title>
		<link>http://change.bbvx.org/2007/10/lessons-learned-on-google-docs/</link>
		<comments>http://change.bbvx.org/2007/10/lessons-learned-on-google-docs/#comments</comments>
		<pubDate>Mon, 08 Oct 2007 13:58:49 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[googledocs]]></category>
		<category><![CDATA[webconferencing]]></category>

		<guid isPermaLink="false">http://change.bbvx.org/2007/10/lessons-learned-on-google-docs/</guid>
		<description><![CDATA[Recently, I&#8217;ve been part of a group that&#8217;s using Google docs to discuss a particular topic. While we&#8217;ve got a draft document as our deliverable, we&#8217;re still at the stage of figuring out what the outline of the document should be and drilling down in to a few fundamental questions. Essentially, we&#8217;re using Google docs [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I&#8217;ve been part of a group that&#8217;s using Google docs to discuss a particular topic. While we&#8217;ve got a draft document as our deliverable, we&#8217;re still at the stage of figuring out what the outline of the document should be and drilling down in to a few fundamental questions. Essentially, we&#8217;re using Google docs as an &#8220;asynchronous chat room&#8221;. Here are a few lessons learned:</p>
<ol>
<li>Make sure everyone knows how to use the &#8220;insert comment&#8221; feature. That automatically signs, time-stamps and color codes comments. [Some folks were using the highlighter tool to color-code their comments.]</li>
<li>Encourage folks to use a separate section of the document for &#8220;discussions&#8221; and to indent comments to show how the thread is evolving &#8212; e.g.<br />
<blockquote><p>Mary makes a comment on section xx</p></blockquote>
<blockquote>
<blockquote><p>Jane comments on Mary&#8217;s comment</p></blockquote>
</blockquote>
<blockquote>
<blockquote><p>Alice replies with another comment on this same topic</p></blockquote>
<p>Sally starts a new thread</p></blockquote>
<p>Try to get people to keep separate topics separate. You can then do some quick cut and paste and/or indenting to show the &#8220;conversations&#8221;.</li>
<li>Use the print icon to print the document with comments. At least in Firefox, print from the browser or Preview/print shows just the document, not the comments.</li>
<li>Once you get to editing the document itself, you can also use comments and go back and &#8220;accept/reject&#8221; them, or make the edits in the document and uses the revision history to track the who and when.</li>
</ol>
<p>If you&#8217;re doing this in a Facebook context, look at the Zoho application (like Google docs, but integrated with Facebook) or the Box application (uses Box.net) to share files of types that Facebook doesn&#8217;t allow you to upload directly.  It might be easier to have the &#8220;discussions&#8221; on Facebook and leave the &#8220;document&#8221; as &#8220;just a document&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://change.bbvx.org/2007/10/lessons-learned-on-google-docs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
