<?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"
	>
<channel>
	<title>Comments on: PEAR Weekly Summary</title>
	<atom:link href="http://www.sitepoint.com/blogs/2004/04/09/pear-weekly-summary/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2004/04/09/pear-weekly-summary/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Fri, 05 Dec 2008 01:52:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Lukas</title>
		<link>http://www.sitepoint.com/blogs/2004/04/09/pear-weekly-summary/#comment-199</link>
		<dc:creator>Lukas</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">923136314#comment-199</guid>
		<description>&lt;p&gt;Alans proposal was about how to write RFC's for new regulations inside PEAR. It had nothing to do with the actual process of proposing packages. However someone could obviously write an RFC to change the package proposal handling.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Alans proposal was about how to write RFC&#8217;s for new regulations inside PEAR. It had nothing to do with the actual process of proposing packages. However someone could obviously write an RFC to change the package proposal handling.</p>]]></content:encoded>
	</item>
</channel>
</rss>
