<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Brent McConnell</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Community 101</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Business Resource</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2010</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://timreview.ca/article/317</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Talent First Network</style></publisher><pub-location><style face="normal" font="default" size="100%">Ottawa</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Recently, a quote stirred some controversy among my peers. The part about &quot;results are not the point&quot; was hard for some people to understand and come to grips with.  Aren't results always the point?  Well, as with most things, &quot;It depends&quot;.  The people and community that evolve around an open source software project will ultimately determine its success.  Even if the core team launches the project with spectacular productivity and results, this phase of evolution will be fleeting if the necessary processes and community to make the project a long lasting success are not put into place.

This article presents some of the actions open source community leaders can take to ensure not only results, but a system that encourages productivity and longevity.</style></abstract><issue><style face="normal" font="default" size="100%">January 2010</style></issue><work-type><style face="normal" font="default" size="100%">Articles</style></work-type><custom1><style face="normal" font="default" size="100%">CollabNet
Brent McConnell is a self-described Community Guy who has worked in and around open source software and communities since 1997 when he happened upon a copy of Slackware. He is currently a Community Consultant with &lt;a href=&quot;http://www.collab.net&quot;&gt; CollabNet&lt;/a&gt;, helping developer communities with adoption and reuse on the CollabNet TeamForge platform. He's also been the Community Manager for the &lt;a href=&quot;http://www.kablink.org/&quot;&gt; Kablink&lt;/a&gt; Open Collaboration platform, and &lt;a href=&quot;http://www.ifolder.com/&quot;&gt; iFolder&lt;/a&gt;. Before all this &quot;community stuff&quot;, he held jobs at Lucent Technologies, Compaq, and HP in various levels of engineering responsibility. He &lt;a href=&quot;http://www.mindby.com/&quot;&gt; blogs&lt;/a&gt; regularly on community issues.</style></custom1></record></records></xml>