<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: An open-source success story from last semester</title>
	<atom:link href="http://blogs.law.harvard.edu/philg/2006/08/17/an-open-source-success-story-from-last-semester/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/philg/2006/08/17/an-open-source-success-story-from-last-semester/</link>
	<description>A posting every day; an interesting idea every three months...</description>
	<lastBuildDate>Sat, 05 Dec 2009 20:28:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ron</title>
		<link>http://blogs.law.harvard.edu/philg/2006/08/17/an-open-source-success-story-from-last-semester/comment-page-1/#comment-14481</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Sun, 27 Aug 2006 06:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/08/17/an-open-source-success-story-from-last-#comment-14481</guid>
		<description>I tried to get a look at the system in operation on the East Coast Aero site, but couldn&#039;t find any way to see the schedule.  I was curious about it because my employer also has a custom web-based FBO scheduling application:

http://sunrise.flitestart.com/</description>
		<content:encoded><![CDATA[<p>I tried to get a look at the system in operation on the East Coast Aero site, but couldn&#8217;t find any way to see the schedule.  I was curious about it because my employer also has a custom web-based FBO scheduling application:</p>
<p><a href="http://sunrise.flitestart.com/" rel="nofollow">http://sunrise.flitestart.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
