<?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: CBC goes wiki for its Spark community</title>
	<atom:link href="http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/feed/" rel="self" type="application/rss+xml" />
	<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/</link>
	<description>convergence, public media, networks, productivity, public engagement</description>
	<lastBuildDate>Thu, 03 Sep 2009 15:45:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Todd</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-28991</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-28991</guid>
		<description>Josh - much love for TiddlyWiki! I&#039;ve used versions of the software for GTD and for note-taking. It&#039;s a slick system and highly portable. Thanks for the note!</description>
		<content:encoded><![CDATA[<p>Josh &#8211; much love for TiddlyWiki! I&#8217;ve used versions of the software for GTD and for note-taking. It&#8217;s a slick system and highly portable. Thanks for the note!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-48222</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-48222</guid>
		<description>Josh - much love for TiddlyWiki! I&#039;ve used versions of the software for GTD and for note-taking. It&#039;s a slick system and highly portable. Thanks for the note!</description>
		<content:encoded><![CDATA[<p>Josh &#8211; much love for TiddlyWiki! I&#8217;ve used versions of the software for GTD and for note-taking. It&#8217;s a slick system and highly portable. Thanks for the note!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-28990</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-28990</guid>
		<description>Dan - I&#039;ll make a note to check in with you in a couple months for an update on the project and what you&#039;re learning from it.

thanks!</description>
		<content:encoded><![CDATA[<p>Dan &#8211; I&#8217;ll make a note to check in with you in a couple months for an update on the project and what you&#8217;re learning from it.</p>
<p>thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-48221</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-48221</guid>
		<description>Dan - I&#039;ll make a note to check in with you in a couple months for an update on the project and what you&#039;re learning from it.&lt;br&gt;&lt;br&gt;thanks!</description>
		<content:encoded><![CDATA[<p>Dan &#8211; I&#8217;ll make a note to check in with you in a couple months for an update on the project and what you&#8217;re learning from it.</p>
<p>thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-28989</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-28989</guid>
		<description>You might also include TiddlyWiki - http://www.tiddlywiki.com - as a choice.  A couple of us are using it for internal collaborations here at WBGO.</description>
		<content:encoded><![CDATA[<p>You might also include TiddlyWiki &#8211; <a href="http://www.tiddlywiki.com" rel="nofollow">http://www.tiddlywiki.com</a> &#8211; as a choice.  A couple of us are using it for internal collaborations here at WBGO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-48220</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-48220</guid>
		<description>You might also include TiddlyWiki - &lt;a href=&quot;http://www.tiddlywiki.com&quot;&gt;http://www.tiddlywiki.com&lt;/a&gt; - as a choice.  A couple of us are using it for internal collaborations here at WBGO.</description>
		<content:encoded><![CDATA[<p>You might also include TiddlyWiki &#8211; <a href="http://www.tiddlywiki.com">http://www.tiddlywiki.com</a> &#8211; as a choice.  A couple of us are using it for internal collaborations here at WBGO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Misener</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-28986</link>
		<dc:creator>Dan Misener</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-28986</guid>
		<description>Todd: Dan from Spark here. Thanks so much for the mention. Here at Spark, we&#039;re all very keen to hear what fruit our little wiki experiment will bear.

We&#039;re discovering some useful things along the way, like how far in advance to ask for help on a story, how much guidance to give to our listeners... that sort of thing. And we&#039;re encountering some interesting questions, too. For example, how can we crowdsource interview questions on a public wiki, but still adhere to the CBC&#039;s journalistic policies on &lt;a href=&quot;http://www.cbc.radio-canada.ca/accountability/journalistic/interviewees.shtml#521&quot; rel=&quot;nofollow&quot;&gt;providing interview questions in advance&lt;/a&gt;?

One of the goals of the wiki experiment is to take the back off the process of making radio. With this comes the question of, &quot;how far out in the open should we work?&quot; Since the show&#039;s launch this past fall, we&#039;ve used an internal wiki for things like contact information, and scripts, and chase lists. But where do you draw the line between private and public information on the wiki?

Clearly, the relationship between radio producers and &quot;&lt;a href=&quot;http://journalism.nyu.edu/pubzone/weblogs/pressthink/2006/06/27/ppl_frmr.html&quot; rel=&quot;nofollow&quot;&gt;the people formerly known as the audience&lt;/a&gt;&quot; is changing. Exciting times.

Thanks again for mentioning us.</description>
		<content:encoded><![CDATA[<p>Todd: Dan from Spark here. Thanks so much for the mention. Here at Spark, we&#8217;re all very keen to hear what fruit our little wiki experiment will bear.</p>
<p>We&#8217;re discovering some useful things along the way, like how far in advance to ask for help on a story, how much guidance to give to our listeners&#8230; that sort of thing. And we&#8217;re encountering some interesting questions, too. For example, how can we crowdsource interview questions on a public wiki, but still adhere to the CBC&#8217;s journalistic policies on <a href="http://www.cbc.radio-canada.ca/accountability/journalistic/interviewees.shtml#521" rel="nofollow">providing interview questions in advance</a>?</p>
<p>One of the goals of the wiki experiment is to take the back off the process of making radio. With this comes the question of, &#8220;how far out in the open should we work?&#8221; Since the show&#8217;s launch this past fall, we&#8217;ve used an internal wiki for things like contact information, and scripts, and chase lists. But where do you draw the line between private and public information on the wiki?</p>
<p>Clearly, the relationship between radio producers and &#8220;<a href="http://journalism.nyu.edu/pubzone/weblogs/pressthink/2006/06/27/ppl_frmr.html" rel="nofollow">the people formerly known as the audience</a>&#8221; is changing. Exciting times.</p>
<p>Thanks again for mentioning us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Misener</title>
		<link>http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/comment-page-1/#comment-48219</link>
		<dc:creator>Dan Misener</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://toddmundt.com/blog/2008/01/25/cbc-goes-wiki-for-its-spark-community/#comment-48219</guid>
		<description>Todd: Dan from Spark here. Thanks so much for the mention. Here at Spark, we&#039;re all very keen to hear what fruit our little wiki experiment will bear.&lt;br&gt;&lt;br&gt;We&#039;re discovering some useful things along the way, like how far in advance to ask for help on a story, how much guidance to give to our listeners... that sort of thing. And we&#039;re encountering some interesting questions, too. For example, how can we crowdsource interview questions on a public wiki, but still adhere to the CBC&#039;s journalistic policies on &lt;a href=&quot;http://www.cbc.radio-canada.ca/accountability/journalistic/interviewees.shtml#521&quot; rel=&quot;nofollow&quot;&gt;providing interview questions in advance&lt;/a&gt;?&lt;br&gt;&lt;br&gt;One of the goals of the wiki experiment is to take the back off the process of making radio. With this comes the question of, &quot;how far out in the open should we work?&quot; Since the show&#039;s launch this past fall, we&#039;ve used an internal wiki for things like contact information, and scripts, and chase lists. But where do you draw the line between private and public information on the wiki?&lt;br&gt;&lt;br&gt;Clearly, the relationship between radio producers and &quot;&lt;a href=&quot;http://journalism.nyu.edu/pubzone/weblogs/pressthink/2006/06/27/ppl_frmr.html&quot; rel=&quot;nofollow&quot;&gt;the people formerly known as the audience&lt;/a&gt;&quot; is changing. Exciting times.&lt;br&gt;&lt;br&gt;Thanks again for mentioning us.</description>
		<content:encoded><![CDATA[<p>Todd: Dan from Spark here. Thanks so much for the mention. Here at Spark, we&#8217;re all very keen to hear what fruit our little wiki experiment will bear.</p>
<p>We&#8217;re discovering some useful things along the way, like how far in advance to ask for help on a story, how much guidance to give to our listeners&#8230; that sort of thing. And we&#8217;re encountering some interesting questions, too. For example, how can we crowdsource interview questions on a public wiki, but still adhere to the CBC&#8217;s journalistic policies on <a href="http://www.cbc.radio-canada.ca/accountability/journalistic/interviewees.shtml#521" rel="nofollow">providing interview questions in advance</a>?</p>
<p>One of the goals of the wiki experiment is to take the back off the process of making radio. With this comes the question of, &#8220;how far out in the open should we work?&#8221; Since the show&#8217;s launch this past fall, we&#8217;ve used an internal wiki for things like contact information, and scripts, and chase lists. But where do you draw the line between private and public information on the wiki?</p>
<p>Clearly, the relationship between radio producers and &#8220;<a href="http://journalism.nyu.edu/pubzone/weblogs/pressthink/2006/06/27/ppl_frmr.html" rel="nofollow">the people formerly known as the audience</a>&#8221; is changing. Exciting times.</p>
<p>Thanks again for mentioning us.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
