@conference {Meneely:2011:SDN:1985793.1985832, title = {Socio-technical developer networks: should we trust our measurements?}, booktitle = {Proceedings of the 33rd International Conference on Software Engineering}, series = {ICSE {\textquoteright}11}, year = {2011}, pages = {281{\textendash}290}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Software development teams must be properly structured to provide effectiv collaboration to produce quality software. Over the last several years, social network analysis (SNA) has emerged as a popular method for studying the collaboration and organization of people working in large software development teams. Researchers have been modeling networks of developers based on socio-technical connections found in software development artifacts. Using these developer networks, researchers have proposed several SNA metrics that can predict software quality factors and describe the team structure. But do SNA metrics measure what they purport to measure? The objective of this research is to investigate if SNA metrics represent socio-technical relationships by examining if developer networks can be corroborated with developer perceptions. To measure developer perceptions, we developed an online survey that is personalized to each developer of a development team based on that developer{\textquoteright}s SNA metrics. Developers answered questions about other members of the team, such as identifying their collaborators and the project experts. A total of 124 developers responded to our survey from three popular open source projects: the Linux kernel, the PHP programming language, and the Wireshark network protocol analyzer. Our results indicate that connections in the developer network are statistically associated with the collaborators whom the developers named. Our results substantiate that SNA metrics represent socio-technical relationships in open source development projects, while also clarifying how the developer network can be interpreted by researchers and practitioners.}, keywords = {developer network, developers, linux, linux kernel, PHP, social network analysis, Survey, wireshark}, isbn = {978-1-4503-0445-0}, doi = {10.1145/1985793.1985832}, url = {http://doi.acm.org/10.1145/1985793.1985832}, author = {Meneely, Andrew and Williams, Laurie} } @conference {773, title = {Fare Open Source all{\textquoteright}Istat: il generatore di data-entry per indagini statistiche}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {283-286}, abstract = {Viene presentata una prima esperienza di sviluppo di software Open Source all{\textquoteright}Istat, che riguarda un sistema generalizzato di data-entry per indagini statistiche. L{\textquoteright}applicazione, in via di rilascio, copre la fase di acquisizione dati propria delle indagini statistiche e consentir{\`a} di generare maschere che potranno essere utilizzate sia in Intranet che sul Web. L{\textquoteright}applicazione descritta, che utilizza PHP e XML come tecnologie fondanti, rappresenta un{\textquoteright}esperienza concreta di sviluppo Open Source nella quale l{\textquoteright}Istat vuole riversare le proprie esperienze specifiche, mettendole poi a disposizione delle altre strutture interessate.}, keywords = {data-entry, indagini statistiche, open source, PHP, web, XML}, url = {http://pascal.case.unibz.it/handle/2038/903}, author = {Altarocca, Francesco and Vaccari, Carlo} } @conference {1248, title = {Supporting Distributed and Decentralized Projects: Drawing Lessons from the Open Source Community}, booktitle = {1st Workshop on Open Source in an Industrial Context}, year = {2003}, note = {"We begin the remainder of the paper with discussion of a survey of open source projects, showing similarities that have arisen in tool usage"}, month = {10/2003}, abstract = {Open source projects are typically organized in a distributed and decentralized manner. These factors strongly determine the processes followed and constrain the types of tools that can be utilized. This paper explores how distribution and decentralization have affected processes and tools in existing open source projects with the goals of summarizing the lessons learned and identifying opportunities for improving both. Issues considered include decision-making, accountability, communication, awareness, rationale, managing source code, testing, and release management.}, keywords = {abiword, apache, debian, freebsd, kde, linux, mozilla, mysql, perl, PHP, postgresql, python, subversion, tomcat, tools}, attachments = {https://flosshub.org/sites/flosshub.org/files/erenkrantz2003.pdf}, author = {Erenkrantz, J. and Taylor, R.N.} }