<?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/"
		>
<channel>
	<title>Comments on: Open Source AT: What&#8217;s Next?</title>
	<atom:link href="http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/</link>
	<description>Agroecology...agroforestry...agrorevolution</description>
	<lastBuildDate>Tue, 24 Aug 2010 17:56:42 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vinay Gupta</title>
		<link>http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/comment-page-1/#comment-19536</link>
		<dc:creator>Vinay Gupta</dc:creator>
		<pubDate>Sat, 20 Oct 2007 03:44:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/#comment-19536</guid>
		<description>Hm. So are you talking about SourceForge for appropriate technology?

That could be ThinkCycle - check it out.

Or more like Google Code?

Or more like one of the open source project management tools?

What&#039;s the closest analogy in the pure-software ecosystem?

That would really help me understand what you want to create!

Vinay</description>
		<content:encoded><![CDATA[Hm. So are you talking about SourceForge for appropriate technology?

That could be ThinkCycle - check it out.

Or more like Google Code?

Or more like one of the open source project management tools?

What's the closest analogy in the pure-software ecosystem?

That would really help me understand what you want to create!

Vinay]]></content:encoded>
	</item>
	<item>
		<title>By: Chriswaterguy</title>
		<link>http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/comment-page-1/#comment-19534</link>
		<dc:creator>Chriswaterguy</dc:creator>
		<pubDate>Sat, 20 Oct 2007 02:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/#comment-19534</guid>
		<description>Good work! Longing to see such tools developed. My focus is on information and networking rather than software though, so I&#039;ll be cheering from the sidelines (and pointing some people in your direction). 

A wiki is a blunt tool - yes, and sometimes a blunt but flexible tool is needed. The design community (and the community at large) needs special design tools, as you say, but these must be integrated with methods of sharing broader information, experience and ideas, fact-checking, brainstorming and networking. Some form of wiki (whatever a wiki ends up looking like in future) will probably be central to the solution we develop in the next few years. 

When OSAT software is developed, integration with a wiki will be an important part of making it accessible, effective and high-impact.

I&#039;m one a co-founders of 
&lt;a HREF=&quot;http://www.appropedia.org/&quot; rel=&quot;nofollow&quot;&gt;Appropedia &lt;/a&gt;, the largest and most active wiki on appropriate technology or sustainability issues (and the home of Hexayurt information resources) so it&#039;s not surprising I think this way - we give a lot of thought to this broad question. 

Re &quot;the prospect of having to reproduce the information four, five, six...times to give it full coverage on all of the different existing communities&quot; - absolutely an important issue. We have placed a lot of emphasis on synergy, and about 7 wikis have merged to form the current Appropedia site - happy to place the grander vision above our own personal success or failure. We&#039;re continuing to explore partnerships with other organizations, and ways of feeding and cross-searching information to ensure that it&#039;s easily accessible. 

Btw, check out our partners, &lt;a HREF=&quot;http://www.openarchitecturenetwork.org/&quot; rel=&quot;nofollow&quot;&gt;Open
Architecture Network&lt;/a&gt; doing excellent work with open source design. 

There are others in the Appropedia network who are more software savvy than me, who&#039;ll be very interested in your comments, so I&#039;ll send them the link.

Don&#039;t let the conversation die - keep in touch.</description>
		<content:encoded><![CDATA[Good work! Longing to see such tools developed. My focus is on information and networking rather than software though, so I'll be cheering from the sidelines (and pointing some people in your direction). 

A wiki is a blunt tool - yes, and sometimes a blunt but flexible tool is needed. The design community (and the community at large) needs special design tools, as you say, but these must be integrated with methods of sharing broader information, experience and ideas, fact-checking, brainstorming and networking. Some form of wiki (whatever a wiki ends up looking like in future) will probably be central to the solution we develop in the next few years. 

When OSAT software is developed, integration with a wiki will be an important part of making it accessible, effective and high-impact.

I'm one a co-founders of 
<a HREF="http://www.appropedia.org/" rel="nofollow">Appropedia </a>, the largest and most active wiki on appropriate technology or sustainability issues (and the home of Hexayurt information resources) so it's not surprising I think this way - we give a lot of thought to this broad question. 

Re "the prospect of having to reproduce the information four, five, six...times to give it full coverage on all of the different existing communities" - absolutely an important issue. We have placed a lot of emphasis on synergy, and about 7 wikis have merged to form the current Appropedia site - happy to place the grander vision above our own personal success or failure. We're continuing to explore partnerships with other organizations, and ways of feeding and cross-searching information to ensure that it's easily accessible. 

Btw, check out our partners, <a HREF="http://www.openarchitecturenetwork.org/" rel="nofollow">Open
Architecture Network</a> doing excellent work with open source design. 

There are others in the Appropedia network who are more software savvy than me, who'll be very interested in your comments, so I'll send them the link.

Don't let the conversation die - keep in touch.]]></content:encoded>
	</item>
	<item>
		<title>By: What&#8217;s next for the Open Source Appropriate Technology movement? &#187; P2P Foundation</title>
		<link>http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/comment-page-1/#comment-19520</link>
		<dc:creator>What&#8217;s next for the Open Source Appropriate Technology movement? &#187; P2P Foundation</dc:creator>
		<pubDate>Fri, 19 Oct 2007 09:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.agroblogger.com/2007/10/18/open-source-at-whats-next/#comment-19520</guid>
		<description>[...] In Agroblogger we find the following item describing what needs to be done to bring AT on a par with developments in the field of software: [...]</description>
		<content:encoded><![CDATA[[...] In Agroblogger we find the following item describing what needs to be done to bring AT on a par with developments in the field of software: [...]]]></content:encoded>
	</item>
</channel>
</rss>
