<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chuqui 3.0 &#187; Community Management</title>
	<atom:link href="http://www.chuqui.com/tag/communitymanagement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chuqui.com</link>
	<description>Typing Without A Net</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:20:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Open Source Communities – Push cx</title>
		<link>http://www.chuqui.com/2009/01/open-source-communities-push-cx/</link>
		<comments>http://www.chuqui.com/2009/01/open-source-communities-push-cx/#comments</comments>
		<pubDate>Tue, 20 Jan 2009 06:52:10 +0000</pubDate>
		<dc:creator>Chuq Von Rospach</dc:creator>
				<category><![CDATA[Community Management and Social Media]]></category>
		<category><![CDATA[Community Management]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Rails]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Server Technologies]]></category>
		<category><![CDATA[Social Networking]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Web Programming Frameworks]]></category>
		<category><![CDATA[Web Technologies]]></category>

		<guid isPermaLink="false">http://www.chuqui.com/?p=485</guid>
		<description><![CDATA[Open source projects should be judged as much by their community as by their technological achievements. The code tells you what it’s good for, but the community tells you what its future is. Communities need to be active to continue improving the project, deal with bugs and changes to their ecosystem. If no one is interested enough to talk about the project, none of that will happen. Newcomers need to meet experienced users to be sold on why to use the software, to get help as they learn their way around, to maybe be drawn into contributing to the project itself. via Open Source Communities &#8211; Push cx. I nice view of the dynamics of communities by Peter Harkins. One of the aspects of this, I think, is that from the communities I&#8217;ve been involved in over the years, the smaller the set of people actively involved in the decision process, design and implementation, the more sensitive that project is to fading or falling apart if the life or motivation of a key member changes. For that reason alone, communities really need to foster new members into the project and ways to recognize and enable the most effective and capable into the &#8220;inner circle&#8221; where they&#8217;re ready and able to step up and move a project forward. If you don&#8217;t do this kind of &#8220;succesion planning&#8221; from the start, when you need it, it won&#8217;t be there. Geeks tend to think you don&#8217;t need marketing, but they&#8217;re wrong. Marketing, even of an open source project, is key to enable adoption and convince people to evaluate it and join the project. projects really should consider community growth as a key metric in he success of a community, and communities really need to look at outreach, evangelism, and recruitment to be tasked out the same way bugs, features and documentation are, and those members should be part of the &#8220;core team&#8221; whether or not they actually code. One reason it looks to me that Rails has taken off faster than django is simple: the rails guys did a lot of talking and promoting and evangelizing of rails, where the django folks have been quieter and less self-promoting of themselves and the technology. A technology nobody knowss about may be great, but it won&#8217;t change the world. This article was posted on Chuqui 3.0 at Open Source Communities – Push cx. This article is copyright 2012 by Chuq Von Rospach under a Creative Commons license for non-commericial use only with attribution. See the web site for details on the usage policy.<p><p style="padding: 8px; background-color: #dddddd; border-top: thin dotted #000000" >
This article was posted on <a href="http://www.chuqui.com">Chuqui 3.0</a> at <a href="http://www.chuqui.com/2009/01/open-source-communities-push-cx/">Open Source Communities – Push cx</a>.  This article is copyright 2012 by Chuq Von Rospach under a Creative Commons license for non-commericial use only with attribution. See the web site for details on the usage policy. </p>
</p>
]]></description>
			<content:encoded><![CDATA[<blockquote><p>Open source projects should be judged as much by their community as by their technological achievements. The code tells you what it’s good for, but the community tells you what its future is.</p>
<p>Communities need to be active to continue improving the project, deal with bugs and changes to their ecosystem. If no one is interested enough to talk about the project, none of that will happen. Newcomers need to meet experienced users to be sold on why to use the software, to get help as they learn their way around, to maybe be drawn into contributing to the project itself.</p>
<p>via <a href="http://push.cx/2009/open-source-communities">Open Source Communities &#8211; Push cx</a>.</p></blockquote>
<p>I nice view of the dynamics of communities by Peter Harkins. One of the aspects of this, I think, is that from the communities I&#8217;ve been involved in over the years, the smaller the set of people actively involved in the decision process, design and implementation, the more sensitive that project is to fading or falling apart if the life or motivation of a key member changes. For that reason alone, communities really need to foster new members into the project and ways to recognize and enable the most effective and capable into the &#8220;inner circle&#8221; where they&#8217;re ready and able to step up and move a project forward. If you don&#8217;t do this kind of &#8220;succesion planning&#8221; from the start, when you need it, it won&#8217;t be there.</p>
<p>Geeks tend to think you don&#8217;t need marketing, but they&#8217;re wrong. Marketing, even of an open source project, is key to enable adoption and convince people to evaluate it and join the project. projects really should consider community growth as a key metric in he success of a community, and communities really need to look at outreach, evangelism, and recruitment to be tasked out the same way bugs, features and documentation are, and those members should be part of the &#8220;core team&#8221; whether or not they actually code.</p>
<p>One reason it looks to me that Rails has taken off faster than django is simple: the rails guys did a lot of talking and promoting and evangelizing of rails, where the django folks have been quieter and less self-promoting of themselves and the technology.</p>
<p>A technology nobody knowss about may be great, but it won&#8217;t change the world.</p>
<p><p style="padding: 8px; background-color: #dddddd; border-top: thin dotted #000000" >
This article was posted on <a href="http://www.chuqui.com">Chuqui 3.0</a> at <a href="http://www.chuqui.com/2009/01/open-source-communities-push-cx/">Open Source Communities – Push cx</a>.  This article is copyright 2012 by Chuq Von Rospach under a Creative Commons license for non-commericial use only with attribution. See the web site for details on the usage policy. </p>
</p>
]]></content:encoded>
			<wfw:commentRss>http://www.chuqui.com/2009/01/open-source-communities-push-cx/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: basic

Served from: www.chuqui.com @ 2012-02-10 07:19:04 -->
