<?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: best software talk ever?</title>
	<atom:link href="http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/feed/" rel="self" type="application/rss+xml" />
	<link>http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/</link>
	<description>tagline goes here</description>
	<pubDate>Thu, 08 Jan 2009 22:48:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rachel</title>
		<link>http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/comment-page-1/#comment-1514</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Tue, 13 Dec 2005 06:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/#comment-1514</guid>
		<description>Dude, found some links about the talk - they're in my post thusly: http://writeonwriteoff.blogspot.com/2005/11/ending-death-marches-if-possible.html.  there seriously needs to be a repository of previous talks somewhere - Lecturester? Eventster? Something-ster?  Some sort of knowledge repository thingy...

and Steve if you get a chance to see this, accept all good speakers, but give priority/preference to people who agree to be podcast/share slides/open to having the discussion continue after the talk ;)</description>
		<content:encoded><![CDATA[<p>Dude, found some links about the talk - they&#8217;re in my post thusly: <a href="http://writeonwriteoff.blogspot.com/2005/11/ending-death-marches-if-possible.html" rel="nofollow">http://writeonwriteoff.blogspot.com/2005/11/ending-death-marches-if-possible.html</a>.  there seriously needs to be a repository of previous talks somewhere - Lecturester? Eventster? Something-ster?  Some sort of knowledge repository thingy&#8230;</p>
<p>and Steve if you get a chance to see this, accept all good speakers, but give priority/preference to people who agree to be podcast/share slides/open to having the discussion continue after the talk ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Williams</title>
		<link>http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/comment-page-1/#comment-1509</link>
		<dc:creator>Steve Williams</dc:creator>
		<pubDate>Tue, 13 Dec 2005 01:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://paulschreiber.com/blog/2005/12/12/best-software-talk-ever/#comment-1509</guid>
		<description>Thanks for your interest in the BayCHI program.  We're very fortunate to have such great speakers and a great volunteer program committee to recruit them.  And how lucky are we to have such a great volunteer meeting reporter in Alison Andrews?

While we can't publish the recording without Alan Cooper's permission, we would love to hear from everyone who wishes we could!  The BayCHI steering committee is thinking about changing our policy: Should we only accept speakers who agree to be podcast and share their slides?  If that meant we'd lose someone like Alan Cooper as a speaker, would it be worth it?

Let us know!</description>
		<content:encoded><![CDATA[<p>Thanks for your interest in the BayCHI program.  We&#8217;re very fortunate to have such great speakers and a great volunteer program committee to recruit them.  And how lucky are we to have such a great volunteer meeting reporter in Alison Andrews?</p>
<p>While we can&#8217;t publish the recording without Alan Cooper&#8217;s permission, we would love to hear from everyone who wishes we could!  The BayCHI steering committee is thinking about changing our policy: Should we only accept speakers who agree to be podcast and share their slides?  If that meant we&#8217;d lose someone like Alan Cooper as a speaker, would it be worth it?</p>
<p>Let us know!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
