<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Kangning Wei</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Self-organization of teams for free/libre open source software development</style></title><secondary-title><style face="normal" font="default" size="100%">Information and Software Technology Journal</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">compiere</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">DESIGN</style></keyword><keyword><style  face="normal" font="default" size="100%">distributed teams</style></keyword><keyword><style  face="normal" font="default" size="100%">egroupware</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">forum</style></keyword><keyword><style  face="normal" font="default" size="100%">free/libre open source software development</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">INTERNET</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">qualitative research methods</style></keyword><keyword><style  face="normal" font="default" size="100%">self-organizing teams</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">SYSTEMS</style></keyword><keyword><style  face="normal" font="default" size="100%">task assignment</style></keyword><keyword><style  face="normal" font="default" size="100%">WORK</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">564-575</style></number><volume><style face="normal" font="default" size="100%">49</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that &quot;self-assignment&quot; was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members&quot;...&quot;projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback&quot;
&quot;3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP.&quot;

all had sourceforge hosting

Data: &quot;The primary data used for our study were interactions on the main developer communication forum, either a developer mailing list or web-based discussion forum.&quot;

Analysis: &quot;For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how&quot;
</style></notes></record></records></xml>
