@conference {Bougie:2011:TUT:1984701.1984707, title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions}, booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering}, series = {Web2SE {\textquoteright}11}, year = {2011}, note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong "From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."}, pages = {31{\textendash}36}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.}, keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0}, isbn = {978-1-4503-0595-2}, doi = {10.1145/1984701.1984707}, url = {http://doi.acm.org/10.1145/1984701.1984707}, attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011.pdf}, author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German} } @conference {Bougie:2011:TUT:1984701.1984707, title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions}, booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering}, series = {Web2SE {\textquoteright}11}, year = {2011}, note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong "From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."}, pages = {31{\textendash}36}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.}, keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0}, isbn = {978-1-4503-0595-2}, doi = {10.1145/1984701.1984707}, url = {http://doi.acm.org/10.1145/1984701.1984707}, attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011_0.pdf}, author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German} } @article {1388, title = {Adoption of open source software in software-intensive organizations {\textendash} A systematic literature review}, journal = {Information and Software Technology}, volume = {52}, year = {2010}, month = {11/2010}, pages = {1133 - 1154}, abstract = {Context Open source software (OSS) is changing the way organizations develop, acquire, use, and commercialize software. Objective This paper seeks to identify how organizations adopt OSS, classify the literature according to these ways of adopting OSS, and with a focus on software development evaluate the research on adoption of OSS in organizations. Method Based on the systematic literature review method we reviewed publications from 24 journals and seven conference and workshop proceedings, published between 1998 and 2008. From a population of 24,289 papers, we identified 112 papers that provide empirical evidence on how organizations actually adopt OSS. Results We show that adopting OSS involves more than simply using OSS products. We moreover provide a classification framework consisting of six distinctly different ways in which organizations adopt OSS. This framework is used to illustrate some of the opportunities and challenges organizations meet when approaching OSS, to show that OSS can be adopted successfully in different ways, and to organize and review existing research. We find that existing research on OSS adoption does not sufficiently describe the context of the organizations studied, and it fails to benefit fully from related research fields. While existing research covers a large number of topics, it contains very few closely related studies. To aid this situation, we offer directions for future research. Conclusion The implications of our findings are twofold. On the one hand, practitioners should embrace the many opportunities OSS offers, but consciously evaluate the consequences of adopting it in their own context. They may use our framework and the success stories provided by the literature in their own evaluations. On the other hand, researchers should align their work, and perform more empirical research on topics that are important to organizations. Our framework may be used to position this research and to describe the context of the organization they are studying.}, keywords = {open source software, organizations, software development, Systematic literature review}, issn = {09505849}, doi = {10.1016/j.infsof.2010.05.008}, url = {http://www.sciencedirect.com/science/article/pii/S0950584910000972}, author = {Hauge, {\O}yvind and Ayala, Claudia and Conradi, Reidar} } @conference {Yatani:2009:UWO:1518701.1518853, title = {Understanding how and why open source contributors use diagrams in the development of Ubuntu}, booktitle = {Proceedings of the 27th international conference on Human factors in computing systems}, series = {CHI {\textquoteright}09}, year = {2009}, note = {"To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort{\textemdash}Ubuntu." "Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants{\textquoteright} OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants."}, pages = {995{\textendash}1004}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.}, keywords = {developers, diagramming, interviews, open source software (oss), software development, Ubuntu, visual representation}, isbn = {978-1-60558-246-7}, doi = {http://doi.acm.org/10.1145/1518701.1518853}, url = {http://doi.acm.org/10.1145/1518701.1518853}, author = {Yatani, Koji and Chung, Eunyoung and Jensen, Carlos and Truong, Khai N.} } @conference {Gurbani:2006:CSC:1134285.1134352, title = {A case study of a corporate open source development model}, booktitle = {Proceedings of the 28th international conference on Software engineering}, series = {ICSE {\textquoteright}06}, year = {2006}, pages = {472{\textendash}481}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Open source practices and tools have proven to be highly effective for overcoming the many problems of geographically distributed software development. We know relatively little, however, about the range of settings in which they work. In particular, can corporations use the open source development model effectively for software projects inside the corporate domain? Or are these tools and practices incompatible with development environments, management practices, and market-driven schedule and feature decisions typical of a commercial software house? We present a case study of open source software development methodology adopted by a significant commercial software project in the telecommunications domain. We extract a number of lessons learned from the experience, and identify open research questions.}, keywords = {architecture, case study, open source, session initiation protocol, software development, vkg}, isbn = {1-59593-375-1}, doi = {10.1145/1134285.1134352}, url = {http://doi.acm.org/10.1145/1134285.1134352}, author = {Gurbani, Vijay K. and Garvert, Anita and Herbsleb, James D.} } @conference {708, title = {Social dynamics of free and open source team communications}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing }, volume = {203/2006}, year = {2006}, month = {06/2006}, pages = {319 - 330}, publisher = {Springer}, organization = {Springer}, abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers. }, keywords = {bug fixing, bug reports, bug tracker, bug tracking, bugs, communications, Dynamic social networks, FLOSS teams, Human Factors, social network analysis, software development, sourceforge}, issn = {978-0-387-34225-2}, doi = {http://dx.doi.org/10.1007/0-387-34226-5_32}, attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20dynamics\%20of\%20free\%20and\%20open\%20source\%20team.pdf}, author = {Howison, James and Inoue, Keisuke and Kevin Crowston} } @conference {798, title = {An International Master Programme in Free Software in the European Higher Education Space}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {349-352}, abstract = {The Universitat Oberta de Catalunya (Open University of Catalonia, UOC) offers an International Master programme in Free Software. The first edition of this master programme began on November 2003 and there are about 240 students currently enrolled at the different specialities offered by the program. In this paper, the design, the methodology and the first few conclusions drawn from this higher education experience are discussed and summarized. After this master programme was changed to accomplish with European Higher Education Space (EHES).}, keywords = {education, free software, FS community, GNU/Linux, learning, master programme, software development, university}, url = {http://pascal.case.unibz.it/handle/2038/713}, author = {Meg{\'\i}as, David and Serra, Jordi and Macau, Rafael} } @conference {791, title = {Looking at Free and Open Source Software: A Study about F/OSS Developers{\textquoteright} Culture}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {324-325}, abstract = {My work will be a cultural study of a F/OSS development project, mixing a symmetric approach with the interaction analysis by Erving Goffman. Methodologically I will approach cyber {\textendash} ethnography.}, keywords = {cultural analysis, cultural study, cyber, F/OSS developers, open source, software development}, url = {http://pascal.case.unibz.it/handle/2038/968}, author = {Teli, Maurizio} } @article {capiluppi:23, title = {Improving comprehension and cooperation through code structure}, journal = {IEE Seminar Digests}, volume = {2004}, number = {908}, year = {2004}, note = {"In this study we measured source code size in three different forms (LOCs, SLOCs, and Kbs of code)." "Pilot Project: The ARLA System" }, pages = {23-28}, publisher = {IEE}, abstract = {Defining a relationship between a software system{\textquoteright}s architecture and the process{\textquoteright} efforts is one of the most fascinating questions of software engineering. Apparently, when a system{\textquoteright}s architecture is complex, the process to improve and evolve it will be more difficult. We try to tackle this question from a different point of view: given an open source system, in all the phases of its evolution, we focus on both the aspects of software developers, and the obtained software product. More we observe one of the possible architectures of this system, based on the tree structure derived from source components. First conclusions show that some patterns of tree evolution are recognizable: some branches may appear more promising than other, and are extensively evolved, while other remains in the same status for all the life cycle. More, when the tree structure reaches some status, the process of joining as a core developer seems to forestall. }, keywords = {arla, code structure, contributors, developers, open source system, scm, software development, software engineering, software process, software product, software system architecture, source code, source components, tree evolution, tree structure}, doi = {10.1049/ic:20040260}, url = {http://link.aip.org/link/abstract/IEESEM/v2004/i908/p23/s1}, attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2004.pdf}, author = {A. Capiluppi} }