Abstract: Today’s software systems build on open source software. Thus, we need to understand how to successfully create, nurture, and mature the software development communities of these open source projects. In this article, we review and discuss best practices of the open source volunteering and recruitment process that successful project leaders are using to lead their projects to success. We combine the perspective of the volunteer, looking at a project, with the perspective of a project leader, looking to find additional volunteers for the project. We identify a five-stage process consisting of a connecting, understanding, engaging, performing, and leading stage. The underlying best practices, when applied, significantly increase the chance of an open source project being successful.
Keywords: Crowdsourcing, open source software, open source communities, volunteering process
Reference: Riehle, D. (2015). The Five Stages of Open Source Volunteering. In Crowdsourcing. Li, Wei; Huhns, Michael N.; Tsai, Wei-Tek; Wu, Wenjun (Editors). Springer-Verlag, 2015, 25-38.
The paper is available as a PDF file and as HTML on this site.
Republished from The Five Stages of Open Source Volunteering. Friedrich-Alexander-Universität Erlangen-Nürnberg, Dept. of Computer Science, Technical Report, CS-2014-01, March 2014. Erlangen, Germany, 2014.
9 Replies to “The Five Stages of Open Source Volunteering [Book Chapter]”
That sounds like it could make a good talk. Contact me if you want a slot in Palo Alto!
Hi Martin, thanks for the invitation. Let me follow-up by private email. –Dirk
First paragraph of my comment is a quote. I must have failed to enter blockquote element correctly.
Hi Mike, thanks for the comments!
I stand by my definition though I can see how it may be confusing.
In my definition, delberately, Apache projects, the Eclipse platform, even OpenStack components are community open source software, because they are being developed jointly by a group of companies. Those companies have commercial motives, but the software they are developing jointly is not competitively differentiating to any of the participants.
Products built on top of these community software components are commercial, of course, but they may or may not be open source.
So, I consider a group of companies with commercial motives still a commuity and the community work not commercial open source software.
Does this make sense?