<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>journal</title>
        <link>http://www.20seven.org/journal/</link>
        <description>...not so private reflections of greg.newman</description>
        <language>en</language>
        <copyright>Copyright 2010</copyright>
        <lastBuildDate>Mon, 19 Nov 2007 04:33:47 -0500</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>RubyCocoa Resources: Call for Volunteers</title>
            <description><![CDATA[<p><a href="http://blog.neontology.com/posts/2007/11/17/rubycocoa-resources-call-for-volunteers">RubyCocoa Resources: Call for Volunteers</a>:</p>

<p>Posted today to the rubycocoa-talk mailing list:</p>

	<blockquote>
		With all of the work that has gone into RubyCocoa for Leopard, the articles that I wrote for my <a href="http://rubycocoa.com">RubyCocoa Resources</a> site need an<br />
update.

So with that, it’s time to decide what to do with RubyCocoa Resources. I’ve heard that Apple had lots of RubyCocoa documentation in the works for Leopard. If that’s enough, then I could just shut down my site and point the domain to http://rubycocoa.sourceforge.net. Otherwise, I think it needs a new maintainer. Any volunteers?<br />
	</blockquote>]]></description>
            <link>http://www.20seven.org/journal/2007/11/rubycocoa-resources-call-for-volunteers.html</link>
            <guid>http://www.20seven.org/journal/2007/11/rubycocoa-resources-call-for-volunteers.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Apple</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">Cocoa</category>
            
                <category domain="http://www.sixapart.com/ns/types#category">RubyCocoa</category>
            
            
            <pubDate>Mon, 19 Nov 2007 04:33:47 -0500</pubDate>
        </item>
        
    </channel>
</rss>

