<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Portlet Farm</title>
	<atom:link href="http://jjmarkow.wordpress.com/2007/11/19/portlet-farm/feed/" rel="self" type="application/rss+xml" />
	<link>http://jjmarkow.wordpress.com/2007/11/19/portlet-farm/</link>
	<description>Observations and musings from Jonathan Markow</description>
	<lastBuildDate>Sat, 19 Jan 2008 22:08:34 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Petro</title>
		<link>http://jjmarkow.wordpress.com/2007/11/19/portlet-farm/#comment-10</link>
		<dc:creator>Andrew Petro</dc:creator>
		<pubDate>Wed, 05 Dec 2007 21:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://jjmarkow.wordpress.com/2007/11/19/portlet-farm/#comment-10</guid>
		<description>&quot;An interesting question was raised at our unconference about how to provide support for shared portlets.&quot;

I don&#039;t worry much about how to support the portlets in the sense of supporting schools in using them.  The self-support behaviors in the context of JA-SIG and uPortal, while largely effective, are very informal.  There&#039;s a commercially provided support program near and dear to my heart that already provides technical support for a number of JA-SIG uPortal channels and portlets.

No, I worry much more about how to support there being these shared, collaboratively developed, open source, freely available, participatory portlet projects in the first place. Build real living widget development projects that produce actual tagged and built releases, and an ability to iterate, and the rest follows.</description>
		<content:encoded><![CDATA[<p>&#8220;An interesting question was raised at our unconference about how to provide support for shared portlets.&#8221;</p>
<p>I don&#8217;t worry much about how to support the portlets in the sense of supporting schools in using them.  The self-support behaviors in the context of JA-SIG and uPortal, while largely effective, are very informal.  There&#8217;s a commercially provided support program near and dear to my heart that already provides technical support for a number of JA-SIG uPortal channels and portlets.</p>
<p>No, I worry much more about how to support there being these shared, collaboratively developed, open source, freely available, participatory portlet projects in the first place. Build real living widget development projects that produce actual tagged and built releases, and an ability to iterate, and the rest follows.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
