<?xml version="1.0" encoding="UTF-8"?>
<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>Don&#039;t Forget to Plant It! &#187; subversion</title>
	<atom:link href="http://blog.codeeg.com/tag/subversion/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.codeeg.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 12:22:47 +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>Twittering Subversion Updates</title>
		<link>http://blog.codeeg.com/2007/03/04/twittering-subversion-updates/</link>
		<comments>http://blog.codeeg.com/2007/03/04/twittering-subversion-updates/#comments</comments>
		<pubDate>Sun, 04 Mar 2007 19:18:02 +0000</pubDate>
		<dc:creator>Calvin</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://blog.codeeg.com/2007/03/04/twittering-subversion-updates/</guid>
		<description><![CDATA[Inspired by this workstreaming post on WWD, I thought it would be a great if I could use Twitter as a way to keep track my current yet-to-be-released project. Twitter is a pretty good fit for workstreaming because it constrains you to a maximum number of characters &#8212; if you&#8217;re doing something that requires more [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Inspired by <a title="Workstreaming post on Web Worker Daily" href="http://webworkerdaily.com/2007/03/03/workstreaming-the-new-face-time/">this workstreaming post on WWD</a>, I thought it would be a great if I could use Twitter as a way to keep track my current yet-to-be-released project.  Twitter is a pretty good fit for workstreaming because it constrains you to a maximum number of characters &#8212; if you&#8217;re doing something that requires more than that, it really should be in posted in a more formalized medium, such as in an email, blog, or Backpack.  For the sake of the people reading your workstream, posts to be short and to the point.</p>
<p>So the first thing I wanted to try is to post Subversion commits Twitter.  An initial Google search pointed me to this <a title="Subverting Twitter" href="http://www.urbanhonking.com/ideasfordozens/archives/2007/01/subverting_twit.html">post about using rake to post to Twitter</a>, but I think having to use rake to do your commits is very inconvenient, so I decided to write it as an Subversion post-commit hook instead.   Fortunately, I found this <a title="Subversion post commit to Basecamp" href="http://www.webtypes.com/2006/03/31/subversion-post-commit-hook-using-basecamp-api">script which posts SVN updates to Basecamp</a>, which got me started.   <a title="Twitter Post Commit Subversion script" href="http://codeeg.com/misc/twitter-post-commit.rb">Here&#8217;s the final script</a>.</p>
<p>So what&#8217;s next?  How about:</p>
<ul>
<li>Update Capistrano to post deploy events.</li>
<li>Post updates to Backpack, Writeboards, or Basecamp</li>
<li>Post updates on important application events and/or errors</li>
</ul>
<p>Granted, this isn&#8217;t exactly workstreaming &#8212; I could update the hook to make posts based on the committer (any takers?), but I think this is good enough.  Unfortunately, I can&#8217;t link to what the output of the script looks like because I&#8217;m posting to protected Twitter accounts, but if you look at the script it&#8217;s pretty basic message.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.codeeg.com/2007/03/04/twittering-subversion-updates/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
