<?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 content and tie-dye</title>
	<atom:link href="http://openedweb.com/blog/2008/12/03/open-content-and-tie-dye/feed/" rel="self" type="application/rss+xml" />
	<link>http://openedweb.com/blog/2008/12/03/open-content-and-tie-dye/</link>
	<description>Education and Technology</description>
	<lastBuildDate>Fri, 12 Mar 2010 10:28:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve</title>
		<link>http://openedweb.com/blog/2008/12/03/open-content-and-tie-dye/comment-page-1/#comment-2133</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 04 Dec 2008 21:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=775#comment-2133</guid>
		<description>This tension between tools and content tears me in two directions. I am trying to shift my balance away from the tools, and increasingly to content and pedagogical use of the tools.

There is a place for proprietary software, but neither I nor my school can afford it.

The degree to which one needs programming skills depends very much upon what software one chooses to use. Elgg is more complex in that it is somewhat of a niche product (I suspect not as niche as the developers expected though), it is very young with limited documentation, and has a fairly small community. There are others such as WordPress that are pretty simple with push button installs and intuitive management. It is a mature project with awide user base, and large community. I also was able to install that tie-dye discussion forum, configure it very quickly and had a community running within a few days of the intial concept.

Thanks for stopping by and adding your thoughts</description>
		<content:encoded><![CDATA[<p>This tension between tools and content tears me in two directions. I am trying to shift my balance away from the tools, and increasingly to content and pedagogical use of the tools.</p>
<p>There is a place for proprietary software, but neither I nor my school can afford it.</p>
<p>The degree to which one needs programming skills depends very much upon what software one chooses to use. Elgg is more complex in that it is somewhat of a niche product (I suspect not as niche as the developers expected though), it is very young with limited documentation, and has a fairly small community. There are others such as WordPress that are pretty simple with push button installs and intuitive management. It is a mature project with awide user base, and large community. I also was able to install that tie-dye discussion forum, configure it very quickly and had a community running within a few days of the intial concept.</p>
<p>Thanks for stopping by and adding your thoughts</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Edminster</title>
		<link>http://openedweb.com/blog/2008/12/03/open-content-and-tie-dye/comment-page-1/#comment-2126</link>
		<dc:creator>Matt Edminster</dc:creator>
		<pubDate>Thu, 04 Dec 2008 06:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://openedweb.com/blog/?p=775#comment-2126</guid>
		<description>Steve ... this idea of bottom-up knowledge sharing is exactly what drew me to OpenSource programs like Elgg. Because we are sharing information over geographical distances - tie-dyers, teachers or in my case rural churches - we need ways to share this information in practical and easy to use ways. 

Kasimpaur&#039;s clarification that open knowledge is the goal is helpful because oftentimes the tools we use to achieve this goal become the focus in and of themselves. I&#039;ve now spent countless hours attempting to learn how to use and customize Elgg. I sometimes wonder if this shiny new tool will ever meet with its intended purpose or if it will completely steal the spotlight. 

Perhaps there is a place for proprietary programming if it allows content providers to share their knowledge without having to worry about the mechanics. I certainly prefer the open source concept (my wallet concurs). But especially those of us without programming skills (including many in both your and my target groups) are a bit disadvantaged when it comes to creating the tools for the job.</description>
		<content:encoded><![CDATA[<p>Steve &#8230; this idea of bottom-up knowledge sharing is exactly what drew me to OpenSource programs like Elgg. Because we are sharing information over geographical distances &#8211; tie-dyers, teachers or in my case rural churches &#8211; we need ways to share this information in practical and easy to use ways. </p>
<p>Kasimpaur&#8217;s clarification that open knowledge is the goal is helpful because oftentimes the tools we use to achieve this goal become the focus in and of themselves. I&#8217;ve now spent countless hours attempting to learn how to use and customize Elgg. I sometimes wonder if this shiny new tool will ever meet with its intended purpose or if it will completely steal the spotlight. </p>
<p>Perhaps there is a place for proprietary programming if it allows content providers to share their knowledge without having to worry about the mechanics. I certainly prefer the open source concept (my wallet concurs). But especially those of us without programming skills (including many in both your and my target groups) are a bit disadvantaged when it comes to creating the tools for the job.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
