<?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: Challenges faced by Community Projects</title>
	<atom:link href="http://blog.ebrahim.org/2005/05/25/challenges-faced-by-community-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ebrahim.org/2005/05/25/challenges-faced-by-community-projects/</link>
	<description>Ali Ebrahim on web standards, software developement, technology, politics and law.</description>
	<lastBuildDate>Tue, 07 Feb 2012 08:34:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Frank Hecker</title>
		<link>http://blog.ebrahim.org/2005/05/25/challenges-faced-by-community-projects/comment-page-1/#comment-353</link>
		<dc:creator>Frank Hecker</dc:creator>
		<pubDate>Wed, 25 May 2005 17:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ebrahim.org/2005/05/25/challenges-faced-by-community-projects/#comment-353</guid>
		<description>This is an excellent post that highlights what IMO are key issues for open source communities. A couple of points I wanted to expand on:

On the point about volunteers being replaceable or not, IMO healthy projects have a good mix between full-time contributors who are very often paid (otherwise they couldn&#039;t do it full-time), casual volunteers (e.g., who might submit a bug report now and then), and part-time volunteers who do a lot of critical project work on an ongoing basis. I think it is this third group, the committed part-time volunteers, who are most irreplaceable; as you point out, they are typically both technically capable and highly knowlegeable in how the project works and how to get things done. Full-time paid contributors do useful work, but sometimes they are not as plugged into the project and its ideals as committed volunteers.

A project can always go out and hire someone (if it has the money) and can also try to attract more casual colunteers to replace old ones, but it can sometimes takes years to recruit committed volunteers and have them evolve into key contributors as they gain experience and standing within the project.

On the subject of divergent ideas: You are right, conflicts over priorities, goals, and project ideals in general can &quot;turn off&quot; contributors; as you imply, this can especially be the case for committed volunteers who are participating primarily because they believe in the project and not because they&#039;re being paid. (Thus your two points are closely connected.)

I agree that there is no &quot;magic formula&quot; to address problems due to divergent ideas. I think the best one can do is to try to treat project contributors and their views with respect and work to ensure that contributors are involved in project discussions and decisions that might affect them. At least that way any conflicts can be handled openly and honestly, as opposed to key contributors feeling that their opinions have been neglected and denigrated.
</description>
		<content:encoded><![CDATA[<p>This is an excellent post that highlights what IMO are key issues for open source communities. A couple of points I wanted to expand on:</p>
<p>On the point about volunteers being replaceable or not, IMO healthy projects have a good mix between full-time contributors who are very often paid (otherwise they couldn&#8217;t do it full-time), casual volunteers (e.g., who might submit a bug report now and then), and part-time volunteers who do a lot of critical project work on an ongoing basis. I think it is this third group, the committed part-time volunteers, who are most irreplaceable; as you point out, they are typically both technically capable and highly knowlegeable in how the project works and how to get things done. Full-time paid contributors do useful work, but sometimes they are not as plugged into the project and its ideals as committed volunteers.</p>
<p>A project can always go out and hire someone (if it has the money) and can also try to attract more casual colunteers to replace old ones, but it can sometimes takes years to recruit committed volunteers and have them evolve into key contributors as they gain experience and standing within the project.</p>
<p>On the subject of divergent ideas: You are right, conflicts over priorities, goals, and project ideals in general can &#8220;turn off&#8221; contributors; as you imply, this can especially be the case for committed volunteers who are participating primarily because they believe in the project and not because they&#8217;re being paid. (Thus your two points are closely connected.)</p>
<p>I agree that there is no &#8220;magic formula&#8221; to address problems due to divergent ideas. I think the best one can do is to try to treat project contributors and their views with respect and work to ensure that contributors are involved in project discussions and decisions that might affect them. At least that way any conflicts can be handled openly and honestly, as opposed to key contributors feeling that their opinions have been neglected and denigrated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

