@conference {588,
	title = {A Survey on Firms{\textquoteright} Participation in Open Source Community Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {225 - 236},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {The role of firms in commercial Open Source projects (e.g., former MySQL, EnterpriseDB, SugarCRM) is a consolidated and generally accepted fact. On other hand, community Open Source projects, which are built upon communities and not directly associated with firms, are commonly perceived to be based mainly on the work of volunteers. Up to now, firms{\textquoteright} role in these projects has been poorly investigated. We conducted a survey on 1,302 SourceForge.net projects to inquire about the level and the typology of involvement of firms. We propose three different models for firm participation and provide empirical evidence on their diffusion in SourceForge.net.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Survey\%20on\%20Firns\%27\%20Participation.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco and Rossi Lamastra, Cristina}
}
@conference {542,
	title = {Empirical Analysis of the Bug Fixing Process in Open Source Projects},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {187 - 196},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Monitoring the performance of processes is often considered critical in classic engineering fields. However, in the area of software engineering (and especially in the Open Source context) it seems that the literature has not yet taken into consideration the problem of identifying the process characteristics and performance of debugging. The aim of this paper is the identification of the performance characteristics of the bug fixing process of Open Source applications, focusing on continuity and efficiency indicators. The importance of such indicators is even more relevant today, since Open Source software is now adopted also in many business contexts. We have analyzed the debugging process of 9 active and popular Open Source projects, collecting a dataset comprising more than 65,000 closed bugs. Results have highlighted four types of bug fixing processes that can be distinguished by considering temporal continuity and efficiency dimensions.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Empirical\%20Analysis\%20of\%20the\%20Bug\%20Fixinf\%20Process.pdf},
	author = {Francalanci, Chiara and Merlo, Francesco}
}
@article {10.1109/TSE.2008.68,
	title = {An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects},
	journal = {IEEE Transactions on Software Engineering},
	volume = {34},
	year = {2008},
	note = {supplemental material attached},
	pages = {765-782},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2008.68},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tts2008060765s.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco}
}
