@proceedings {1896, title = {Addressing Lock-in, Interoperability, and Long-Term Maintenance Challenges Through Open Source: How Can Companies Strategically Use Open Source?}, volume = {496}, year = {2017}, month = {05/2017}, pages = {80-88}, publisher = {Springer}, abstract = {This industry paper reports on how strategic use of open source in company contexts can provide effective support for addressing the fundamental challenges of lock-in, interoperability, and longevity of software and associated digital assets. The fundamental challenges and an overview of an ongoing collaborative research project are presented. Through a conceptual model for open source usage in company contexts we characterise how companies engage with open source and elaborate on how the fundamental challenges can be effectively addressed through open source usage in company contexts. }, doi = {10.1007/978-3-319-57735-7_9}, url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_9}, author = {Lundell, Bj{\"o}rn and Gamalielsson, Jonas and Stefan Tengblad and Bahram Hooshyar Yousefi and Thomas Fischer and Gert Johansson and Bengt Rodung and Mattsson, Anders and Johan Oppmark and Gustavsson, Tomas and Feist, Jonas and Stefan Landemoo and Erik L{\"o}nroth} } @proceedings {1908, title = {How Open Source Projects use Static Code Analysis Tools in Continuous Integration Pipelines}, year = {2017}, note = {Data: the paper studies the use of ASCATs (Automated Static Code Analysis Tools) within CI pipelines of 20 popular Java open source projects hosted on GitHub and using Travis CI to support CI activities}, month = {05/2017}, pages = {334-344}, abstract = {Static analysis tools are often used by software developers to entail early detection of potential faults, vulnerabilities, code smells, or to assess the source code adherence to coding standards and guidelines. Also, their adoption within Continuous Integration (CI) pipelines has been advocated by researchers and practitioners. This paper studies the usage of static analysis tools in 20 Java open source projects hosted on GitHub and using Travis CI as continuous integration infrastructure. Specifically, we investigate (i) which tools are being used and how they are configured for the CI, (ii) what types of issues make the build fail or raise warnings, and (iii) whether, how, and after how long are broken builds and warnings resolved. Results indicate that in the analyzed projects build breakages due to static analysis tools are mainly related to adherence to coding standards, and there is also some attention to missing licenses. Build failures related to tools identifying potential bugs or vulnerabilities occur less frequently, and in some cases such tools are activated in a {\textquotedblleft}softer{\textquotedblright} mode, without making the build fail. Also, the study reveals that build breakages due to static analysis tools are quickly fixed by actually solving the problem, rather than by disabling the warning, and are often properly documented.}, keywords = {continuous integration, empirical study, static analysis}, doi = {10.1109/MSR.2017.2}, author = {Zampetti, Fiorella and Scalabrino, Simone and Oliveto, Rocco and Canfora, Gerardo and Di Penta, Massimiliano} } @article {1920, title = {Process Aspects and Social Dynamics of Contemporary Code Review: Insights from Open Source Development and Industrial Practice at Microsoft}, journal = {IEEE Transactions on Software Engineering}, volume = {43}, year = {2017}, note = {" We sent the survey to code review participants from 36 popular OSS projects and received 287 responses"}, month = {1/2017}, pages = {56 - 75}, abstract = {Many open source and commercial developers practice contemporary code review, a lightweight, informal, tool-based code review process. To better understand this process and its benefits, we gathered information about code review practices via surveys of open source software developers and developers from Microsoft. The results of our analysis suggest that developers spend approximately 10-15 percent of their time in code reviews, with the amount of effort increasing with experience. Developers consider code review important, stating that in addition to finding defects, code reviews offer other benefits, including knowledge sharing, community building, and maintaining code quality. The quality of the code submitted for review helps reviewers form impressions about their teammates, which can influence future collaborations. We found a large amount of similarity between the Microsoft and OSS respondents. One interesting difference is that while OSS respondents view code review as an important method of impression formation, Microsoft respondents found knowledge dissemination to be more important. Finally, we found little difference between distributed and co-located Microsoft teams. Our findings identify the following key areas that warrant focused research: 1) exploring the non-technical benefits of code reviews, 2) helping developers in articulating review comments, and 3) assisting reviewers{\textquoteright} program comprehension during code reviews.}, keywords = {code review, commercial projects, peer impressions, Survey}, issn = {1939-3520}, doi = {10.1109/TSE.2016.2576451}, url = {https://amiangshu.com/papers/CodeReview-TSE-2016.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/CodeReview-TSE-2016.pdf}, author = {Bosu, Amiangshu and Carver, Jeffrey C. and Christian Bird and Orbeck, Jonathan and Chockley, Christopher} } @conference {Hata:2015:CSO:2819321.2819325, title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study}, booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering}, series = {CHASE {\textquoteright}15}, year = {2015}, note = {Slideshare: http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study}, pages = {15{\textendash}21}, publisher = {IEEE Press}, organization = {IEEE Press}, address = {Piscataway, NJ, USA}, abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.}, url = {http://dl.acm.org/citation.cfm?id=2819321.2819325}, author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Kenichi Matsumoto} } @proceedings {1763, title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports}, year = {2015}, month = {05/2015}, publisher = {IEEE}, abstract = {The importance of supporting test and maintenance activities in software development has been increasing, since recent software systems have become large and complex. Although in the field of Mining Software Repositories (MSR) there are many promising approaches to predicting, localizing, and triaging bugs, most of them do not consider impacts of each bug on users and developers but rather treat all bugs with equal weighting, excepting a few studies on high impact bugs including security, performance, blocking, and so forth. To make MSR techniques more actionable and effective in practice, we need deeper understandings of high impact bugs. In this paper we introduced our dataset of high impact bugs which was created by manually reviewing four thousand issue reports in four open source projects (Ambari, Camel, Derby and Wicket).}, keywords = {ambari, camel, derby, wicket}, url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141}, attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf}, author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto} } @inbook {1730, title = {An Empirical Study of the Relation Between Strong Change Coupling and Defects Using History and Social Metrics in the Apache Aries Project}, booktitle = {Open Source Systems: Adoption and Impact}, series = {IFIP Advances in Information and Communication Technology}, volume = {451}, year = {2015}, pages = {3-12}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, abstract = {Change coupling is an implicit relationship observed when artifacts change together during software evolution. The literature leverages change coupling analysis for several purposes. For example, researchers discovered that change coupling is associated with software defects and reveals relationships between software artifacts that cannot be found by scanning code or documentation. In this paper, we empirically investigate the strongest change couplings from the Apache Aries project to characterize and identify their impact in software development. We used historical and social metrics collected from commits and issue reports to build classification models to identify strong change couplings. Historical metrics were used because change coupling is a phenomenon associated with recurrent co-changes found in the software history. In turn, social metrics were used because developers often interact with each other in issue trackers to accomplish the tasks. Our classification models showed high accuracy, with 70-99 \% F-measure and 88-99 \% AUC. Using the same set of metrics, we also predicted the number of future defects for the artifacts involved in strong change couplings. More specifically, we were able to predict 45.7 \% of defects where these strong change couplings reoccurred in the post-release. These findings suggest that developers and projects managers should detect and monitor strong change couplings, because they can be associated with defects and tend to happen again in the subsequent release.}, isbn = {978-3-319-17836-3}, doi = {10.1007/978-3-319-17837-0_1}, url = {http://dx.doi.org/10.1007/978-3-319-17837-0_1}, author = {Wiese, Igor Scaliante and Kuroda, Rodrigo Takashi and Re, Reginaldo and Oliva, Gustavo Ansaldi and Gerosa, MarcoAur{\'e}lio}, editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.} } @inbook {1740, title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption}, booktitle = {Open Source Systems: Adoption and Impact}, series = {IFIP Advances in Information and Communication Technology}, volume = {451}, year = {2015}, pages = {124-133}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in. }, keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform}, isbn = {978-3-319-17836-3}, doi = {10.1007/978-3-319-17837-0_12}, url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12}, author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.}, editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.} } @proceedings {1767, title = {Toward Reusing Code Changes}, year = {2015}, month = {05/2015}, publisher = {IEEE}, abstract = {Existing techniques have succeeded to help developers implement new code. However, they are insufficient to help to change existing code. Previous studies have proposed techniques to support bug fixes but other kinds of code changes such as function enhancements and refactorings are not supported by them. In this paper, we propose a novel system that helps developers change existing code. Unlike existing techniques, our system can support any kinds of code changes if similar code changes occurred in the past. Our research is still on very early stage and we have not have any implementation or any prototype yet. This paper introduces our research purpose, an outline of our system, and how our system is different from existing techniques.}, keywords = {apache}, url = {http://sdl.ist.osaka-u.ac.jp/~higo/data/ICSE15-MSR-05-p052.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/ICSE15-MSR-05-p052.pdf}, author = {Higo, Yoshiki and Akio Ohtani and Shinpei Hayashi and Hata, Hideaki and Kusumoto Shinji} } @conference {Saini:2014:DMA:2597073.2597134, title = {A Dataset for Maven Artifacts and Bug Patterns Found in Them}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {416{\textendash}419}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {In this paper, we present data downloaded from Maven, one of the most popular component repositories. The data includes the binaries of 186,392 components, along with source code for 161,025. We identify and organize these components into groups where each group contains all the versions of a library. In order to asses the quality of these components, we make available report generated by the FindBugs tool on 64,574 components. The information is also made available in the form of a database which stores total number, type, and priority of bug patterns found in each component, along with its defect density. We also describe how this dataset can be useful in software engineering research. }, keywords = {Empirical Research, Empirical software engineering, findbugs, maven, software quality}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597134}, url = {http://doi.acm.org/10.1145/2597073.2597134}, author = {Saini, Vaibhav and Sajnani, Hitesh and Ossher, Joel and Lopes, Cristina V.} } @conference {Murgia:2014:DFE:2597073.2597086, title = {Do Developers Feel Emotions? An Exploratory Analysis of Emotions in Software Artifacts}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {262{\textendash}271}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Software development is a collaborative activity in which developers interact to create and maintain a complex software system. Human collaboration inevitably evokes emotions like joy or sadness, which can affect the collaboration either positively or negatively, yet not much is known about the individual emotions and their role for software development stakeholders. In this study, we analyze whether development artifacts like issue reports carry any emotional information about software development. This is a first step towards verifying the feasibility of an automatic tool for emotion mining in software development artifacts: if humans cannot determine any emotion from a software artifact, neither can a tool. Analysis of the Apache Software Foundation issue tracking system shows that developers do express emotions (in particular gratitude, joy and sadness). However, the more context is provided about an issue report, the more human raters start to doubt and nuance their interpretation of emotions. More investigation is needed before building a fully automatic emotion mining tool. }, keywords = {Emotion Mining, Empirical Software Engineer- ing, Issue Report}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597086}, url = {http://doi.acm.org/10.1145/2597073.2597086}, attachments = {https://flosshub.org/sites/flosshub.org/files/murgia.pdf}, author = {Murgia, Alessandro and Tourani, Parastou and Adams, Bram and Ortu, Marco} } @conference {1720, title = {Evaluating Software Product Quality: A Systematic Mapping Study}, booktitle = {2014 Joint Conference of the International Workshop on Software Measurement IWSM-MENSURA}, year = {2014}, pages = {141 - 151}, publisher = {IEEE}, organization = {IEEE}, address = {Rotterdam, Netherlands}, abstract = {Evaluating software product quality (SPQ) is an important task to ensure the quality of software products. In this paper a systematic mapping study was performed to summarize the existing SPQ evaluation (SPQE) approaches in literature and to classify the selected studies according to seven classification criteria: SPQE approaches, research types, empirical types, data sets used in the empirical evaluation of these studies, artifacts, SQ models, and SQ characteristics. Publication channels and trends were also identified. 57 papers were selected. The results show that the main publication sources of the papers identified were journals. Data mining techniques are the most frequently approaches reported in literature. Solution proposals were the main research type identified. The majority of the selected papers were history-based evaluations using existing data, which were mainly obtained from open source software projects and domain specific projects. Source code was the main artifacts used by SPQE approaches. Well-known SQ models were mentioned by half of the selected papers and reliability is the SQ characteristic through which SPQE was mainly achieved. SPQE-related subjects seem to attract more interest from researchers since the past years. }, doi = {10.1109/IWSM.Mensura.2014.30}, url = {http://www.scielo.org.mx/pdf/cys/v19n3/v19n3a11.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/v19n3a11.pdf}, author = {Ouhbi, Sofia and Idri, Ali and Aleman, Jose Luis Fernandez and Toval, Ambrosio} } @inbook {1598, title = {FOSS Service Management and Incidences}, booktitle = {Open Source Software: Mobile Open Source Technologies}, series = {IFIP Advances in Information and Communication Technology}, volume = {427}, year = {2014}, pages = {76-79}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, abstract = { The Free Open Source Software (FOSS) solutions have been reaching a high demand, usage and global recognition, not only in the development of applications for companies and institutions also in the management of services and incidents. With the upswing of Information Technology (IT), the development of tools that enable the reporting of problems and incidents on any organization or company is necessary. Every day you need more applications, software generally, that make easier the user{\textquoteright}s actions. This paper describes the need to use these tools and recount the development of a web application that allows the management of reports and incidents from users of Nova, the GNU/Linux Cuban distribution. }, keywords = {FOSS, service management and incidences}, isbn = {978-3-642-55127-7}, doi = {10.1007/978-3-642-55128-4_9}, url = {http://dx.doi.org/10.1007/978-3-642-55128-4_9}, author = {Ortiz, SusanaS{\'a}nchez and P{\'e}rez Benitez, Alfredo}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.} } @conference {Bloemen:2014:GPD:2597073.2597131, title = {Gentoo Package Dependencies over Time}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {404{\textendash}407}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Open source distributions such as Gentoo need to accurately track dependency relations between software packages in order to install working systems. To do this, Gentoo has a carefully authored database containing those relations. In this paper, we extract the Gentoo package dependency graph and its changes over time. The final dependency graph spans 15 thousand open source projects and 80 thousand dependency relations. Furthermore, the development of this graph is tracked over time from the beginning of the Gentoo project in 2000 to the first quarter of 2012, with monthly resolution. The resulting dataset provides many opportunities for research. In this paper we explore cluster analysis to reveals meaningful relations between packages and in a separate paper we analyze changes in the dependencies over time to get insights in the innovation dynamics of open source software. }, keywords = {dependencies, gentoo, graph, INNOVATION}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597131}, url = {http://doi.acm.org/10.1145/2597073.2597131}, author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo} } @conference {Bloemen:2014:IDO:2597073.2597079, title = {Innovation Diffusion in Open Source Software: Preliminary Analysis of Dependency Changes in the Gentoo Portage Package Database}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {316{\textendash}319}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {In this paper we make the case that software dependencies are a form of innovation adoption. We then test this on the time-evolution of the Gentoo package dependency graph. We find that the Bass model of innovation diffusion fits the growth of the number of packages depending on a given library. Interestingly, we also find that low-level packages have a primarily imitation driven adoption and multimedia libraries have primarily innovation driven growth. }, keywords = {dependencies, gentoo, graph, INNOVATION}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597079}, url = {http://doi.acm.org/10.1145/2597073.2597079}, attachments = {https://flosshub.org/sites/flosshub.org/files/bloeman.pdf}, author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo} } @article {1716, title = {Sourcerer: An infrastructure for large-scale collection and analysis of open-source code}, journal = {Science of Computer Programming}, volume = {79}, year = {2014}, month = {1/2014}, pages = {241 - 259}, abstract = {A large amount of open source code is now available online, presenting a great potential resource for software developers. This has motivated software engineering researchers to develop tools and techniques to allow developers to reap the benefits of these billions of lines of source code. However, collecting and analyzing such a large quantity of source code presents a number of challenges. Although the current generation of open source code search engines provides access to the source code in an aggregated repository, they generally fail to take advantage of the rich structural information contained in the code they index. This makes them significantly less useful than Sourcerer for building state-of-the-art software engineering tools, as these tools often require access to both the structural and textual information available in source code.We have developed Sourcerer, an infrastructure for large-scale collection and analysis of open source code. By taking full advantage of the structural information extracted from source code in its repository, Sourcerer provides a foundation upon which state-of-the-art search engines and related tools can easily be built. We describe the Sourcerer infrastructure, present the applications that we have built on top of it, and discuss how existing tools could benefit from using Sourcerer.}, issn = {01676423}, doi = {10.1016/j.scico.2012.04.008}, author = {Bajracharya, Sushil and Ossher, Joel and Lopes, Cristina} } @article {gonzalez2013studying, title = {Studying the laws of software evolution in a long-lived FLOSS project}, journal = {Journal of Software: Evolution and Process}, year = {2013}, publisher = {Wiley Online Library}, abstract = {Some free, open-source software projects have been around for quite a long time, the longest living ones dating from the early 1980s. For some of them, detailed information about their evolution is available in source code management systems tracking all their code changes for periods of more than 15 years. This paper examines in detail the evolution of one of such projects, glibc, with the main aim of understanding how it evolved and how it matched Lehman{\textquoteright}s laws of software evolution. As a result, we have developed a methodology for studying the evolution of such long-lived projects based on the information in their source code management repository, described in detail several aspects of the history of glibc, including some activity and size metrics, and found how some of the laws of software evolution may not hold in this case.}, url = {http://oa.upm.es/21355/1/smr1615.pdf}, author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Herraiz, Israel and Ortega, Felipe} } @proceedings {1475, title = {Discussion on the Problems to be Solved toward the Migration to OSS Productivity Software in the Business Enterprises}, volume = {378}, year = {2012}, month = {09/2012}, pages = {377-382}, publisher = {IFIP AICT, Springer}, address = {Eighth International Conference on Open Source Systems}, abstract = {In recent years, there is a tendency to migrate from proprietary productivity software to open-source productivity software, especially in government offices and municipal offices. ODPG (OpenOffice.org \& OpenDocument Format Promotion Group, Japan) is an organization founded in order to promote the migration to the OSS productivity software in private enterprises as well. In the case evaluation work group of ODPG, business solutions about use of OpenOffice.org have been discussed many times, for the purpose of supporting the migration to OpenOffice.org, by collecting and feeding back the information of case studies useful for the member companies. This paper reports several subjects and solutions, such as promotion strategy for OpenOffice.org to be widely used, the problem in file exchange with the other stakeholders, preparation of use environment, and security issues, which were discussed in the work group.}, author = {Iio, Jun and Ogawa, Tomotaka} } @proceedings {1465, title = {Forking the Commons: Developmental Tensions and Evolutionary Patterns in Open Source Software}, volume = {378}, year = {2012}, month = {09/2012}, pages = {310-315}, publisher = {IFIP AICT, Springer}, abstract = {Open source software (OSS) presents opportunities and challenges for developers to exploit its commons based licensing regime by creating specializations of a software technology to address plurality of goals and priorities. By {\textquoteleft}forking{\textquoteright} a new branch of development separate from the main project, development diverges into a path in order to relieve tensions related to specialization, which later encounters new tensions. In this study, we first classify forces and patterns within this divergence process. Such tensions may stem from a variety of sources including internal power conflicts, emergence of new environmental niches such as demand for specialized uses of same software, or differences along stability vs. development speed trade-off. We then present an evolutionary model which combines divergence options available to resolve tensions, and how further tensions emerge. In developing this model we attempt to define open software evolution at the level of systems of software, rather than at individual software project level.}, keywords = {divergence, forking, software evolution, specialization}, author = {Gen{\c c}er, Mehmet and {\"O}zel, B{\"u}lent} } @proceedings {1273, title = {Developing Architectural Documentation for the Hadoop Distributed File System}, year = {2011}, month = {10/2011}, pages = {50-61}, publisher = {Springer}, abstract = {Many open source projects are lacking architectural documentation that describes the major pieces of the system, how they are structured, and how they interact. We have produced architectural documentation for the Hadoop Distributed File System (HDFS), a major open source project. This paper describes our process and experiences in developing this documentation. We illustrate the documentation we have produced and how it differs from existing documentation by describing the redundancy mechanisms used in HDFS for reliability.}, author = {Bass, Len and Kazman, Rick and Ozkaya, Ipek} } @article {1398, title = {The search for a research method for studying OSS process innovation}, journal = {Empirical Software Engineering}, volume = {16}, year = {2011}, month = {8/2011}, pages = {514 - 537}, abstract = {Medium-sized, open-participation Open Source Software (OSS) projects do not usually perform explicit software process improvement on any routine basis. It would be useful to understand how to get such a project to accept a process improvement proposal and hence to perform process innovation. We want to determine an effective and feasible qualitative research method for studying the above question. We present (narratively) a case study of how we worked towards and eventually found such a research method. The case involves four attempts at collecting suitable data about innovation episodes (direct participation (twice), polling developers for episodes, manually finding episodes in mailing list archives) and the adaptation of the Grounded Theory data analysis methodology. Direct participation allows gathering rather rich data, but does not allow for observing a sufficiently large number of innovation episodes. Polling developers for episodes did not prove to be useful. Using mailing list archives to find data to be analyzed is both feasible and effective. We also describe how the data thus found can be analyzed based on the Grounded Theory Method with suitable adjustments. By-and-large, our findings ought to apply to studying various phenomena in OSS development processes that are similarly heavyweight and infrequent. However, specific details may block this possibility and we cannot predict which details that might be. The amount of effort involved in direct participation approaches to qualitative research can easily be underestimated. Also, survey approaches are not well-suited for many process issues in OSS, because too few developers are sufficiently process-conscious. An approach based on passive observation is a viable alternative in the OSS context due to the availability of large amounts of fairly complete archival data. }, keywords = {argouml, Bochs, bugzilla, Flyspray, FreeDOS, gEDA, grounded theory, Grub, Innovation introduction, KVM, mailing list, Methodology, MonetDB, open source, Request Tracket, Rox, U-Boot, Xfce}, issn = {1573-7616}, doi = {10.1007/s10664-011-9160-1}, author = {Prechelt, Lutz and Oezbek, Christopher} } @conference {963, title = {Automated dependency resolution for open source software}, booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)}, year = {2010}, pages = {130 - 140}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {Opportunities for software reuse are plentiful, thanks in large part to the widespread adoption of open source processes and the availability of search engines for locating relevant artifacts. One challenge presented by open source software reuse is simply getting a newly downloaded artifact to build/run in the first place. The artifact itself likely reuses other artifacts, and so depends on their being located to function properly. While merely tedious in the individual case, this can cause serious difficulties for those seeking to study open source software. It is simply not feasible to manually resolve dependencies for thousands of projects, and many forms of analysis require declarative completeness. In this paper we present a method for automatically resolving dependencies for open source software. It works by cross-referencing a project{\textquoteright}s missing type information with a repository of candidate artifacts. We have implemented this method on top of the Sourcerer, an infrastructure for the large-scale indexing and analysis of open source code. The performance of our resolution algorithm was evaluated in two parts. First, for a small number of popular open source projects, we manually examined the artifacts suggested by our system to determine if they were appropriate. Second, we applied the algorithm to the 13,241 projects in the Sourcerer managed repository to evaluate the rate of resolution success. The results demonstrate the feasibility of this approach, as the algorithm located all of the required artifacts needed by 3,904 additional projects, increasing the percentage of declaratively complete projects in Sourcerer from 39\% to 69\%.}, keywords = {dependencies, java, source code, sourcerer}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463346}, author = {Ossher, Joel and Bajracharya, Sushil and Lopes, Cristina} } @conference {Oezbek:2010:OCS:1833272.1833274, title = {The onion has cancer: some social network analysis visualizations of open source project communication}, booktitle = {Proceedings of the 3rd International Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development (FLOSS {\textquoteright}10)}, series = {FLOSS {\textquoteright}10}, year = {2010}, note = {paper d/l from www.inf.fu-berlin.de/~oezbek/pub/OezThiPre10-SNA.pdf "We study the introduction of process innovations in Open Source projects [33] by manually extracting innovation episodes from arch- ives of mailing-lists and analyzing these episodes qualitatively by the Grounded Theory Method [38]." "we took all messages from the mailing-list archives in 2007 of the projects we were studying, turned each participant into a node (unifying multi- ple e-mail addresses where needed [6]), and computed relationship strength between A and B as the number of e-mails that are a reply of B to a message from A or vice versa, according to the in-reply-to header of the e-mail." Our data set covers 11 of the 13 projects (from 7 different do- mains, selected from mailing-list archive Gmane to build a diverse set of projects) for which we analyzed innovation episodes. They include three workflow applications (Bugzilla, Flyspray, Request Tracker), two desktop environments (Rox, Xfce), two design tools (ArgoUML, a UML CASE tool; gEDA, a set of electronic design automation tools), one bootloader (Grub), one hardware emulator (Bochs), one operating system (FreeDOS), and one database man- agement system (MonetDB).}, pages = {5{\textendash}10}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Background: People contribute to OSS projects in wildly different degrees, from reporting a single defect once and never coming back to spending many hours each workday on the project over several years - or anything in between. It is a common conception that these degrees of participation sort the participants into a number of similar groups which are layered like the peels of an onion: The onion model. Objective: We check whether this model of gradually different degrees of participation is valid with respect to the participation in OSS project mailing-list traffic. Methods: We perform social network analysis based on replies to mailing-list messages and use visualization to check the nature of three different groups of participants. Results: There appears to be a discontinuity with respect to core members: The degree to which very active core members (as opposed to less active co-developers) react to e-mails of senders from the project{\textquoteright}s periphery is significantly higher than would be expected from their level of activity in general. Limitations: The effect might be an artifact of the assumption that each mailing-list message can be treated the same. Conclusions: We conclude that core member status may be qualitatively (rather than just quantitatively) different and the transition of individual mailing-list participants towards ever higher participation is qualitatively discontinuous.}, keywords = {argouml, Bochs, bugzilla, communication structure, Flyspray, gEDA, Grub, MonetDB, open source process, request tracker, Rox, social network analysis, Xfce}, isbn = {978-1-60558-978-7}, doi = {10.1145/1833272.1833274}, url = {http://doi.acm.org/10.1145/1833272.1833274}, attachments = {https://flosshub.org/sites/flosshub.org/files/OezThiPre10-SNA.pdf}, author = {Oezbek, Christopher and Prechelt, Lutz and Thiel, Florian} } @conference {835, title = {Paying attention to each other in visible work communities: Modeling bursty systems of multiple activity streams}, booktitle = {SocialCom/PASSAT(2010)}, year = {2010}, note = {Uses open source projects to study, but this is not about open source, per se.}, month = {2010}, pages = {276-281}, abstract = {Online work projects, from open source to wikipedia, have emerged as an important phenomenon. These communities offer exciting opportunities to investigate social processes because they leave traces of their activity over time. Unlike traditional work teams, the participants in these communities are widely dispersed and work without centralized management. The question arises, then, as to the extent to which these are in fact communities: is the group simply the sum of the individuals that make it up, or does the group function as a social unit? We explore this question in the temporal domain. We argue that the rapid visibility of others{\textquoteright} work afforded by the information systems used by these projects reaches out and attracts the attention of others who are peripherally aware of the group{\textquoteright}s online space, prompting them to begin or intensify their participation, binding separate individual streams of activity into a social entity. Previous work has suggested that for certain types of bursty social behavior (e.g. email), the frequency of the behavior is not homogeneously distributed but rather can be divided into two generative mechanisms: active sessions and passive background participation. We extend this work for the case of multiple conditionally independent streams of behavior, where each stream is generated by these two generative mechanisms. Our model can characterized by a double-chain hidden Markov model, allowing efficient inference using expectation-maximization. We apply this model to visible work communities by modeling each participant as a single stream of behavior, assessing transition probabilities between active sessions of different participants. This allows us to examine the extent to which the various members of the community are influenced by the active participation of others. Our results indicate that an active session by a participant at least triples the likelihood of another participant beginning an active session.}, attachments = {https://flosshub.org/sites/flosshub.org/files/olson2010paying-attentio.pdf}, author = {Olson, Jamie F and Howison, James and Carley, Kathleen} } @conference {1809, title = {On the Analysis of Contributions from Privileged Users in Virtual Open Communities}, booktitle = {2009 42nd Hawaii International Conference on System Sciences}, year = {2009}, pages = {1 - 10}, publisher = {IEEE}, organization = {IEEE}, address = {Waikoloa, Hawaii, USA}, abstract = {Collaborative projects built around virtual communities on the Internet have gained momentum over the last decade. Nevertheless, their rapid growth rate rises some questions:which is the most effective approach to manage and organize their content creation process? Can these communities scale, controlling their projects as their size continues to grow over time? To answer these questions, we undertake a quantitative analysis of privileged users in FLOSS development projects and in Wikipedia. From our results, we conclude that the inequality level of user contributions in both types of initiatives is remarkably distinct, even though both communities present almost identical patterns regard-ing the number of distinct contributors per file (in FLOSS projects) or per article (in Wikipedia). As a result, totally open projects like Wikipedia can effectively deal with faster growing rates, while FLOSS projects may be affected by bottlenecks on committers who play critical roles.}, isbn = {978-0-7695-3450-3}, doi = {10.1109/HICSS.2009.328}, author = {Ortega, Felipe and Izquierdo-Cort{\'a}zar, Daniel and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles} } @conference {608, title = {Libre Software in Spanish Public Administrations}, booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)}, series = {IFIP Advances in Information and Communication Technology }, volume = {299/2009}, year = {2009}, month = {2009///}, pages = {366 - 366}, publisher = {Springer}, organization = {Springer}, chapter = {40}, abstract = {Libre software started to be used in Public Administrations in Spain during the 1990s, in some isolated but interesting experiences.During the early 2000s, and specially in some regional governments, libre software started to be considered as an integral part of ITrelated policies. In 2007, it was evident that many experiences related to libre software were running in Public Administrations with different levels of success. However, no study had looked into the details of these experiences, and no comprehensive analysis had been performed to better understand the different factors that affect them. }, issn = {978-3-642-02031-5}, doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_40}, attachments = {https://flosshub.org/sites/flosshub.org/files/Libre\%20Software.pdf}, author = {Ortega, Felipe and Lafuente, Isabel and Gato, Jose and Gonz{\'a}lez-Barahona, Jes{\'u}s} } @conference {945, title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects}, booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories}, year = {2009}, pages = {183 - 186}, publisher = {IEEE}, organization = {IEEE}, address = {Vancouver, BC, Canada}, abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential resuse. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.}, keywords = {apache, integration, java, java.net, project, repository, sourceforge, SourcererDB}, isbn = {978-1-4244-3493-0}, doi = {10.1109/MSR.2009.5069501}, author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina} } @conference {1066, title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects}, booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)}, year = {2009}, pages = {183 - 186}, publisher = {IEEE}, organization = {IEEE}, address = {Vancouver, BC, Canada}, abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential re-use. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.}, keywords = {apache, java, java.net, source code, sourceforge, sourcerer}, isbn = {978-1-4244-3493-0}, doi = {10.1109/MSR.2009.5069501}, author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina} } @conference {Orsila:2009:TIO:1527033.1527037, title = {Trust issues in open source software development}, booktitle = {Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010}, series = {WUP {\textquoteright}09}, year = {2009}, note = {"We have selected two highly reusable libraries, zlib and FFmpeg. The software repository of the projects were downloaded, but mining the information is not an easy task and we considered various sources {\textemdash} such as bug reports, mailing lists, IRC conversations, and source code comments {\textemdash} in addition to the revision history. "}, pages = {9{\textendash}12}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Open source software and the associated development model holds great promise, but the issue of trust is a major challenge. This applies to companies wishing to adopt the open source model but also within open source projects. We investigate this issue by data mining open source repositories to study two related phenomena: update propagation and distributed version control.}, keywords = {ffmpeg, trust, version control, zlib}, isbn = {978-1-60558-565-9}, doi = {10.1145/1527033.1527037}, url = {http://doi.acm.org/10.1145/1527033.1527037}, author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed} } @article {10.1109/HICSS.2009.1014, title = {Using Software Archaeology to Measure Knowledge Loss in Software Projects Due to Developer Turnover}, journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)}, year = {2009}, pages = {1-10}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, abstract = {Developer turnover can result in a major problem when developing software. When senior developers abandon a software project, they leave a knowledge gap that has to be managed. In addition, new (junior) developers require some time in order to achieve the desired level of productivity. In this paper, we present a methodology to measure the effect of knowledge loss due to developer turnover in software projects. For a given software project, we measure the quantity of code that has been authored by developers that do not belong to the current development team, which we define as orphaned code. Besides, we study how orphaned code is managed by the project. Our methodology is based on the concept of software archaeology, a derivation of software evolution. As case studies we have selected four FLOSS (free, libre, open source software) projects, from purely driven by volunteers to company-supported. The application of our methodology to these case studies will give insight into the turnover that these projects suffer and how they have managed it and shows that this methodology is worth being augmented in future research.}, keywords = {attrition, case study, developers, evince, evolution, gimp, growth, knowledge collaboration, lines of code, nautilus, quality, sloc, turnover}, isbn = {978-0-7695-3450-3}, doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1014}, attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-08.pdf}, author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Ortega, Felipe and Jesus M. Gonzalez-Barahona} } @conference {534, title = {Analysis of Coordination Between Developers and Users in the Apache Community}, 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 = {81 - 92}, publisher = {Springer}, organization = {Springer}, chapter = {7}, abstract = {Coordination is one of the keys for the success of open source software (OSS) communities because geographically distributed members need to collaborate on their work using communication tools (e.g., mailing lists, bulletin board systems, bug tracking systems, and so on). In this paper, we investigated the informal social structure among developers and users by analyzing two mailing lists of developers and users in the Apache community based on betweenness centrality, one centrality measure proposed by Freeman. From the analysis results, we found that (1) participants with high betweenness coordinated activities between developers and users and (2) some participants have been functioning as coordinators in the community for a long time. }, keywords = {apache, email, mailing list}, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_7}, attachments = {https://flosshub.org/sites/flosshub.org/files/Analysis\%20of\%20Coordination.pdf}, author = {Kamei, Yasutaka and Matsumoto, Shinsuke and Maeshima, Hirotaka and Onishi, Yoji and Ohira, Masao and Matsumoto, Ken-ichi} } @article {863, title = {The Role of Participation Architecture in Growing Sponsored Open Source Communities}, journal = {Industry \& Innovation}, volume = {15}, year = {2008}, month = {4/2008}, pages = {145 - 168}, author = {Joel West and Siobhan O{\textquoteright}Mahony} } @conference {540, title = {Update Propagation Practices in Highly Reusable Open Source Components}, 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 = {159 - 170}, publisher = {Springer}, organization = {Springer}, chapter = {13}, abstract = {In today{\textquoteright}s business and software arena, more and more companies are adopting open source software. An example of this rising phenomenon is to base software products on highly reusable open source components. In this scenario, the evolution of the software product is coupled with the evolution of the open source component. A common assumption is that component updates are immediately and regularly propagated to the project. This paper investigates this assumption empirically by studying update propagation practices in two popular open source libraries, zlib and FFmpeg. For each library, we analyze various repository sources with information such as bug reports, revision history, and source code. The results of the case studies suggest that update propagation is subject to several technical and non-technical factors including the way the open source library is used, the extent to which updates are documented, and the degree of community involvement. Based on these findings, we propose a set of recommendations that would allow better follow-up of updates and smoother update propagation. }, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_13}, attachments = {https://flosshub.org/sites/flosshub.org/files/Update\%20Propagation\%20Practice.pdf}, author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed} } @conference {541, title = {Using Social Network Analysis Techniques to Study Collaboration between a FLOSS Community and a Company}, 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 = {171 - 186}, publisher = {Springer}, organization = {Springer}, chapter = {14}, abstract = {Because of the sheer volume of information available in FLOSS repositories, simple analysis have to face the problems of filtering the relevant information. Hence, it is essential to apply methodologies that highlight that information for a given aspect of the project. In this paper, some techniques from the social sciences have been used on data from version control systems to extract information about the development process of FLOSS projects with the aim of highlighting several processes that occur in FLOSS projects and that are difficult to obtain by other means. In particular, the collaboration between the FLOSS community and a company has been studied by selecting two projects as case studies. The results highlight aspects such as efficiency in the development process, release management and leadership turnover. }, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_14}, attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20Social\%20Network.pdf}, author = {Martinez-Romo, Juan and Gregorio Robles and Gonzalez-Barahona, Jesus and Ortu{\~n}o-Perez, Miguel} } @conference {650, title = {Introducing Usability Practices to OSS: The Insiders{\textquoteright} Experience}, booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)}, series = {IFIP International Federation for Information Processing }, volume = {234/2007}, year = {2007}, month = {2007///}, pages = {313 - 318}, publisher = {Springer}, organization = {Springer}, chapter = {34}, abstract = {This paper presents a case study of introducing usability practices to a small open source project called Carrot2. We describe our experiences from a point of view of an active Carrot2 developer, who is at the same time a usability enthusiast and practitioner. We perform a critical analysis of the system{\textquoteright}s original user interface and describe the steps we took to improve it. We also analyse the success factors and the impact of the whole redesign process. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_34}, attachments = {https://flosshub.org/sites/flosshub.org/files/Introducing\%20Usability\%20Practices.pdf}, author = {Osi{\'n}ski, Stanis{\l}aw and Weiss, Dawid} } @article {126, title = {Investigating recognition-based performance in an open content community: A social capital perspective}, journal = {Information \& Management}, volume = {44}, number = {3}, year = {2007}, note = {Times Cited: 0}, month = {Apr}, pages = {240-252}, abstract = {As the open source movement grows, it becomes important to understand the dynamics that affect the motivation of participants who contribute their time freely to such projects. One important motivation that has been identified is the desire for formal recognition in the open source community. We investigated the impact of social capital in participants{\textquoteright} social networks on their recognition-based performance; i.e., the formal status they are accorded in the community. We used a sample of 465 active participants in the Wikipedia open content encyclopedia community to investigate the effects of two types of social capital and found that network closure, measured by direct and indirect ties, had a significant positive effect on increasing participants{\textquoteright} recognition-based performance. Structural holes had mixed effects on participants{\textquoteright} status, but were generally a source of social capital. (C) 2007 Elsevier B.V. All rights reserved.}, keywords = {open content, recognition-based performance, social capital, social networks, social status, virtual communities}, isbn = {0378-7206}, author = {Okoli, C. and Oh, Wonseok} } @article {125, title = {Membership herding and network stability in the open source community: The Ising perspective}, journal = {Management Science}, volume = {53}, number = {7}, year = {2007}, month = {Jul}, pages = {1086-1101}, abstract = {The aim of this paper is twofold: (1) to conceptually understand membership dynamics in the open source software (OSS) community, and (2) to explore how different network characteristics (i.e., network size and connectivity) influence the stability of an OSS network. Through the lens of Ising theory, which is widely accepted in physics, we investigate basic patterns of interaction and present fresh conceptual insight into dynamic and reciprocal relations among OSS community members. We also perform computer simulations based on empirical data collected from two actual OSS communities. Key findings include: (1) membership herding is highly present when external influences (e.g., the availability of other OSS projects) are weak, but decreases significantly when external influences increase, (2) propensity for membership herding is most likely to be seen in a large network with random connectivity, and (3) for large networks, when external influences are weak, random connectivity will result in higher network strength than scale-free connectivity (as external influences increase, however, the reverse phenomenon is observed). In addition, scale-free connectivity appears to be less volatile than random connectivity in response to an increase in the strength of external influences. We conclude with several implications that may be of significance to OSS stakeholders in particular, and to a broader range of online communities in general.}, keywords = {BEHAVIOR, DYNAMICS, ECONOMICS, INNOVATION, INVESTMENT, Ising theory, membership herding, MODEL, MOTIVATION, network connectivity, network stability, open source, PHASE-TRANSITION, UNCERTAINTY}, isbn = {0025-1909}, author = {Oh, Wonseok and Jeon, Sangyong} } @conference {651, title = {Perceptions on F/OSS Adoption}, booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)}, series = {IFIP International Federation for Information Processing }, volume = {234/2007}, year = {2007}, month = {2007///}, pages = {319 - 324}, publisher = {Springer}, organization = {Springer}, chapter = {35}, abstract = {This paper aims to reveal results of a survey run by the tOSSad1 project. The majority of survey variables devised to capture perception of public administrators around Europe regarding the importance they attach to the factors such as F/OSS product quality, availability of support, expertise and documentation, TCO, vendor lock-in, political influence, administrative attitudes, productivity, and training costs, all of which intermingle with financial, technical, legal, and personal issues. The analysis consist of depiction of respondents{\textquoteright} administration profile in terms of their F/OSS usage and adoption, descriptive summary and analyses of factors mentioned above, and statistical inferential analyses of survey items. Some valid statistical tests are conducted to understand, to discuss and to see the extend and significance of any F/OSS adoption generalizations for Europe based on the findings of this particular survey. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_35}, attachments = {https://flosshub.org/sites/flosshub.org/files/Perceptions\%20on\%20F\%20OSS.pdf}, author = {Ozel, Bulent and Jovanovic, Uros and Oba, Beyza and van Leeuwen, Manon} } @conference {1724, title = {On Understanding How to Introduce an Innovation to an Open Source Project}, booktitle = {First International Workshop on Emerging Trends in FLOSS Research and Development (FLOSS{\textquoteright}07: ICSE Workshops 2007)First International Workshop on Emerging Trends in FLOSS Research and Development (FLOSS{\textquoteright}07: ICSE Workshops 2007)}, year = {2007}, pages = {12 - 12}, publisher = {IEEE}, organization = {IEEE}, address = {Minneapolis, MN, USA}, abstract = {We propose to research the introduction of Software Engineering inventions into Open Source projects (1) to help researchers with creating opportunities for evaluating their tools, methods and process designs in real-life settings, and (2) to help Open Source projects with improving their processes based on state-of-the-art knowledge. Such research will go beyond diffusion and dissemination of inventions to active introduction, and thus increase the chances of adoption. We will discuss the research approach, our preliminary insights, limitations of the approach, and why researchers interested in evaluating their own inventions should be interested in this research. }, isbn = {0-7695-2961-5}, doi = {10.1109/FLOSS.2007.11}, author = {Oezbek, Christopher and Prechelt, Lutz} } @article {Yu:2006:MKO:1150566.1150571, title = {Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD}, journal = {J. Syst. Softw.}, volume = {79}, year = {2006}, note = {"Data regarding the number and total number of lines of code of kernel and nonkernel modules in the four operating systems are provided in Table 1" loc, kloc, number of kernel modules, number of nonkernel modules size c files .h files}, month = {June}, pages = {807{\textendash}815}, publisher = {Elsevier Science Inc.}, address = {New York, NY, USA}, abstract = {We compared and contrasted the maintainability of four open-source operating systems: Linux, FreeBSD, NetBSD, and OpenBSD. We used our categorization of common coupling in kernel-based software to highlight future maintenance problems. An unsafe definition is a definition of a global variable that can affect a kernel module if that definition is changed. For each operating system we determined a number of measures, including the number of global variables, the number of instances of global variables in the kernel and overall, as well as the number of unsafe definitions in the kernel and overall. We also computed the value of each our measures per kernel KLOC and per KLOC overall. For every measure and every ratio, Linux compared unfavorably with FreeBSD, NetBSD, and OpenBSD. Accordingly, we are concerned about the future maintainability of Linux. }, keywords = {abiword, Common coupling, coupling, Definition-use analysis, freebsd, kernel, lines of code, linux, linux kernel, loc, Maintainability, modules, netbsd, Open-source software, openbsd, source code}, issn = {0164-1212}, doi = {http://dx.doi.org/10.1016/j.jss.2005.08.014}, url = {http://dx.doi.org/10.1016/j.jss.2005.08.014}, attachments = {https://flosshub.org/sites/flosshub.org/files/YuSchachChen.pdf}, author = {Yu, Liguo and Schach, Stephen R. and Chen, Kai and Heller, Gillian Z. and Offutt, Jeff} } @conference {702, title = {Organization of Internet Standards}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {267 - 272}, publisher = {Springer}, organization = {Springer}, abstract = {In this study we look at a body of standards documents in RFCs(Request For Comments) of IETF (Internet Engineering Task Force). The cross references between these documents form a network. Approaches from social network analysis are deployed to assess centrality of artifacts in this network and identify cohesive subgroups and levels of cohesion. Our results demonstrate major groups centered around key standard tracks, and application of network metrics reflect different levels of cohesion for these groups. As application of these techniques in such domains is unusual, possible uses in open source projects for strategizing are discussed. }, doi = {http://dx.doi.org/10.1007/0-387-34226-5_27}, attachments = {https://flosshub.org/sites/flosshub.org/files/Organization\%20of\%20Internet\%20Standards.pdf}, author = {Gen{\c c}er, Mehmet and Oba, Beyza and {\"O}zel, B{\"u}lent and Tunal{\i}o{\u g}lu, V.} } @conference {892, title = {tagging, community, vocabulary, evolution}, booktitle = {Computer Supported Cooperative Work}, year = {2006}, month = {04/11/2006}, pages = {181-190}, publisher = {ACM}, organization = {ACM}, address = {Banff, Alberta, Canada}, isbn = {1-59593-249-6}, author = {Shilad Sen and Shyong K. Lam and Dan Cosley and Al Mamunur Rashid and Dan Frankowski and Franklin Harper and Jeremy Osterhouse and John Riedl} } @conference {Ohira:2005:ACK:1083142.1083163, title = {Accelerating cross-project knowledge collaboration using collaborative filtering and social networks}, booktitle = {Proceedings of the 2005 international workshop on Mining software repositories}, series = {MSR {\textquoteright}05}, year = {2005}, pages = {111-115}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Vast numbers of free/open source software (F/OSS) development projects use hosting sites such as Java.net and SourceForge.net. These sites provide each project with a variety of software repositories (e.g. repositories for source code sharing, bug tracking, discussions, etc.) as a media for communication and collaboration. They tend to focus on supporting rich collaboration among members in each project. However, a majority of hosted projects are relatively small projects consisting of few developers and often need more resources for solving problems. In order to support cross-project knowledge collaboration in F/OSS development, we have been developing tools to collect data of projects and developers at SourceForge, and to visualize the relationship among them using the techniques of collaborative filtering and social networks. The tools help a developer identify {\textquotedblleft}who should I ask?{\textquotedblright} and {\textquotedblleft}what can I ask?{\textquotedblright} and so on. In this paper, we report a case study of applying the tools to F/OSS projects data collected from SourceForge and how effective the tools can be used for helping cross-project knowledge collaboration.}, keywords = {collaborative filtering, developers, knowledge collaboration, projects, social networks, sourceforge, visualization tool}, isbn = {1-59593-123-6}, doi = {http://doi.acm.org/10.1145/1082983.1083163}, url = {http://doi.acm.org/10.1145/1082983.1083163}, attachments = {https://flosshub.org/sites/flosshub.org/files/111Accelerating.pdf}, author = {Ohira, Masao and Ohsugi, Naoki and Ohoka, Tetsuya and Matsumoto, Ken-ichi} } @conference {779, title = {Carrot2 Clustering Framework}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {298-299}, abstract = {Carrot2 is an Open Source framework for research experiments with querying various textual data sources, processing and presentation of the results. Its main goal is to promote component reuse in order to reduce the effort involved in the development of Information Retrieval software. So far, the most successful and popular application of Carrot2 has been organizing results of Internet searches into easy to browse thematic groups called clusters. In this area, the project successfully competes with commercial counterparts like Vivisimo or iBoogie.}, keywords = {BSD license, cluster, clustering framework, open source, research, result}, url = {http://pascal.case.unibz.it/handle/2038/788}, author = {Weiss, Dawid and Osi{\textasciiacute}nski, Stanis{\l}aw} } @proceedings {897, title = {Experiences in Discovering, Modeling, and Reenacting Open Source Software Development Processes}, year = {2005}, month = {May}, publisher = {Springer-Verlag}, address = {Beijing, China}, author = {Chris Jensen and Walt Scacchi}, editor = {Li, Mingshu and Boehm, Barry and Osterweil, Leon J.} } @conference {769, title = {An Hypergraph Based Approach for Unlocking Power Relations in Rhizomatic Open Source Software Communities}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {272}, abstract = {This study, first, points the rhizomatic nature of open source software (OSS) communities. Then, it proposes an hypergraph based research methodology both to capture and to analyze dynamics of OSS communities. An exemplary hypergraph theoretical analysis of power antecedence within rhizomatic network of an OSS community is illustrated.}, url = {http://pascal.case.unibz.it/handle/2038/626}, author = {{\"O}zel, B{\"u}lent} } @conference {Fischer:2005:MED:1083142.1083145, title = {Mining evolution data of a product family}, booktitle = {Proceedings of the 2005 international workshop on Mining software repositories}, series = {MSR {\textquoteright}05}, year = {2005}, pages = {12-16}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Diversification of software assets through changing requirements impose a constant challenge on the developers and maintainers of large software systems. Recent research has addressed the mining for data in software repositories of single products ranging from fine- to coarse grained analyses. But so far, little attention has been payed to mining data about the evolution of product families. In this work, we study the evolution and commonalities of three variants of the BSD (Berkeley Software Distribution), a large open source operating system. The research questions we tackle are concerned with how to generate high level views of the system discovering and indicating evolutionary highlights. To process the large amount of data, we extended our previously developed approach for storing release history information to support the analysis of product families. In a case study we apply our approach on data from three different code repositories representing about 8.5GB of data and 10 years of active development.}, keywords = {bsd, change analysis, change history, cvs, evolution, freebsd, netbsd, openbsd, release history, source code, text mining}, isbn = {1-59593-123-6}, doi = {http://doi.acm.org/10.1145/1082983.1083145}, url = {http://doi.acm.org/10.1145/1082983.1083145}, attachments = {https://flosshub.org/sites/flosshub.org/files/12MiningEvolution.pdf}, author = {Fischer, Michael and Oberleitner, Johann and Ratzinger, Jacek and Gall, Harald} } @conference {754, title = {Open Source and Business Model Innovation. The Funambol case}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {224-227}, abstract = {A comprehensive theoretical framework about open source business models is still missing, notwithstanding a growing number of contributions. This lack of literature is mainly due to the relative newness of the phenomena. This paper aims at giving a contribution to the ongoing discussion about open source business implications. The research hypothesis is that open source represents a disruptive innovation for the software industry. The purpose is to understand, through case study research, how open source companies can develop successful business models. Funambol provides an interesting example of an optimized business model, able to leverage the open source advantage in an emerging market. The paper is structured in three main parts: the first one aims at outlining the research hypothesis and methodology. The second part identifies the unique competitive factors distinguishing open source business and the main business implications. The final part focuses on the analys...}, url = {http://pascal.case.unibz.it/handle/2038/967}, author = {Onetti, Alberto and Capobianco, Fabrizio} } @conference {1482, title = {Group awareness in distributed software development}, booktitle = {2004 ACM conference on Computer supported cooperative work - CSCW {\textquoteright}04}, year = {2004}, pages = {72-81}, publisher = {ACM Press}, organization = {ACM Press}, address = {New York, New York, USA}, abstract = {Open-source software development projects are almost always collaborative and distributed. Despite the difficulties imposed by distance, these projects have managed to produce large, complex, and successful systems. However, there is still little known about how open-source teams manage their collaboration. In this paper we look at one aspect of this issue: how distributed developers maintain group awareness. We interviewed developers, read project communication, and looked at project artifacts from three successful open source projects. We found that distributed developers do need to maintain awareness of one another, and that they maintain both a general awareness of the entire team and more detailed knowledge of people that they plan to work with. Although there are several sources of information, this awareness is maintained primarily through text-based communication (mailing lists and chat systems). These textual channels have several characteristics that help to support the maintenance of awareness, as long as developers are committed to reading the lists and to making their project communication public.}, keywords = {email, email archive, mailing list}, isbn = {1581138105}, doi = {10.1145/1031607.1031621}, author = {Schneider, Kevin and Gutwin, Carl and Penner, Reagan} } @article {flosswp191, title = {Hacking Alone? The Effects of Online and Offline Participation on Open Source Community Leadership}, year = {2004}, month = {September}, abstract = {Research on computer mediated communication has examined how a lack of social presence affects participation, communication and leadership in online groups, but until recently, has not examined offline relations or emergent social structures. The few studies examining these issues have not been integrated with research on open source communities. Online communities producing open source software face even greater problems of governance than affinity or interest based online communities, as leadership responsibilities extend beyond mailing list management to managing release dates, public relations, and collaborations with firms. With data from one open source community{\textquoteright}s online and offline networks over three consecutive years, we assess factors affecting voting participation and leadership. We find that the more developers one has met face to face, the more likely one was to vote in a leadership election. Controlling for contributions of code, developers are more likely to hold a top leadership position when they participate more in online discussions. However, online participation in technical discussions did not affect leadership as much as occupying a structurally advantaged position in the community{\textquoteright}s social network. We conclude with theoretical implications that consider the dynamics of online and offline networks for governing distributed online communities.}, attachments = {https://flosshub.org/sites/flosshub.org/files/omahonyferraro2.pdf}, author = {Siobhan O{\textquoteright}Mahony} } @proceedings {124, title = {Membership dynamics and network stability in the open-source community: the ising perspective}, year = {2004}, note = {"simulations with the empirical network data that were collected from two actual OSS communities, Linux and Hypermail." "we initially downloaded nearly 100,000 archived (between 1997 and 2003) LINUX Kernel and Hypermail newsgroup messages posted in a UNIX mailbox format" "Specific information was obtained regarding the characteristics of these two OSS communities, including the size, the number of average connections per participant, and the hierarchy of each community."}, abstract = {In this paper, we address the following two questions: (1)How does a participant{\textquoteright}s membership decision affect the others (neighbors) with whom he has collaborated over an extended period of time in an open source software (OSS) network? (2) To what extent do network characteristics (i.e, size and connectivity) mediate the impact of external factors on the OSS participants{\textquoteright} dynamic membership decisions and hence the stability of the network? From the Ising perspective, we present fresh theoretical insight into the dynamic and reciprocal membership relations between OSS participants. We also performed simulations based on empirical data that were collected from two actual OSS communities. Some of the key findings include that (1) membership herding is highly present when the external force is weak, but decreases significantly when the force increases, (2) the propensity for membership herding is most likely to be seen in a large network with a random connectivity, and (3) for large networks, at low external force a random connectivity will perform better than a scale-free counterpart in terms of the network strength. However, as the temperature (external force) increases, the reverse phenomenon is observed. In addition, the scale-free connectivity appears to be less volatile than with the random connectivity in response to the increase in the temperature. We conclude with several implications that may be of significance to OSS stakeholders.}, keywords = {email, email archive, hypermail, linux, mailing list, membership, membership herding, newsgroup, open source, participants, social network analysis, stakeholders, team size}, attachments = {https://flosshub.org/sites/flosshub.org/files/OhJeon.pdf}, author = {Oh, Wonseok and Jeon, Sangyong} } @article {Chen:2004:OCL:990374.990391, title = {Open-Source Change Logs}, journal = {Empirical Softw. Engg.}, volume = {9}, year = {2004}, note = {"We decided to compare actual differences in the source code with entries in the ChangeLog file. We used lxr, the Linux cross-referencing tool..., to determine the precise differences between two successive software versions. We then compared these differences with the records in the ChangeLog file to check the completeness of the ChangeLog file." }, month = {September}, pages = {197{\textendash}210}, publisher = {Kluwer Academic Publishers}, address = {Hingham, MA, USA}, abstract = {A recent editorial in Empirical Software Engineering suggested that open-source software projects offer a great deal of data that can be used for experimentation. These data not only include source code, but also artifacts such as defect reports and update logs. A common type of update log that experimenters may wish to investigate is the ChangeLog, which lists changes and the reasons for which they were made. ChangeLog files are created to support the development of software rather than for the needs of researchers, so questions need to be asked about the limitations of using them to support research. This paper presents evidence that the ChangeLog files provided at three open-source web sites were incomplete. We examined at least three ChangeLog files for each of three different open-source software products, namely, GNUJSP, GCC-g++, and Jikes. We developed a method for counting changes that ensures that, as far as possible, each individual ChangeLog entry is treated as a single change. For each ChangeLog file, we compared the actual changes in the source code to the entries in the ChangeLog file and discovered significant omissions. For example, using our change-counting method, only 35 of the 93 changes in version 1.11 of Jikes appear in the ChangeLog file{\textemdash}that is, over 62\% of the changes were not recorded there. The percentage of omissions we found ranged from 3.7 to 78.6\%. These are significant omissions that should be taken into account when using ChangeLog files for research. Before using ChangeLog files as a basis for research into the development and maintenance of open-source software, experimenters should carefully check for omissions and inaccuracies.}, keywords = {change log, gcc, GCC-g, GNUJSP, Jikes, log files, Open-source software, source code}, issn = {1382-3256}, doi = {10.1023/B:EMSE.0000027779.70556.d0}, url = {http://portal.acm.org/citation.cfm?id=990374.990391}, attachments = {https://flosshub.org/sites/flosshub.org/files/chen.pdf}, author = {Chen, Kai and Schach, Stephen R. and Yu, Liguo and Offutt, Jeff and Heller, Gillian Z.} } @article {flosswp77, title = {Guarding the Commons: How Community Managed Software Projects Protect Their Work}, journal = {Research Policy}, volume = {32}, year = {2003}, note = {"Data was collected from three primary sources: 1) observation at project and user group meetings, technical presentations and conferences; 2) informant interviews; and 3) project data archived on the Internet that detailed project interactions and structural developments." "Project data was collected from online archives and included documents such as: mission statements, charters, bylaws, meeting minutes, and mailing list archives."}, month = {February}, pages = {1179-1198}, edition = {7}, abstract = {Theorists often speculate why open source and free software project contributors give their work away. Although contributors make their work publicly available, they do not forfeit their rights to it. Community managed software projects protect their work by using several legal and normative tactics, which should not be conflated with a disregard for or neglect of intellectual property rights. These tactics allow a project?s intellectual property to be publicly and freely available and yet, governable. Exploration of this seemingly contradictory state may provide new insight into governance models for the management of digital intellectual property.}, keywords = {Common Pool Resources, email, email archives, intellectual property, mailing list, open source, Public Goods, Software, Survey}, attachments = {https://flosshub.org/sites/flosshub.org/files/rp-omahony.pdf}, author = {Siobhan O{\textquoteright}Mahony} } @article {flosswp122, title = {Managing the Boundary of an {\textquoteright}Open{\textquoteright} Project}, year = {2003}, month = {October}, abstract = {In the past ten years, the boundaries between public and open science and commercial research efforts have become more porous. Scholars have thus more critically examined ways in which these two institutional regimes intersect. Large open source software projects have also attracted commercial collaborators and now struggle to develop code in an open public environment that still protects their communal boundaries. This research applies a dynamic social network approach to understand how one community managed software project, Debian, develops a membership process. We examine the project{\textquoteright}s face-to-face social network during a five-year period (1997-2001) to see how changes in the social structure affect the evolution of membership mechanisms and the determination of gatekeepers. While the amount and importance of a contributor{\textquoteright}s work increases the probability that a contributor will become a gatekeeper, those more central in the social network are more likely to become gatekeepers and influence the membership process. A greater understanding of the mechanisms open projects use to manage their boundaries has critical implications for research and knowledge producing communities operating in pluralistic, open and distributed environments.}, keywords = {debian, membership, social network analysis}, attachments = {https://flosshub.org/sites/flosshub.org/files/omahonyferraro.pdf}, author = {Siobhan O{\textquoteright}Mahony} } @article {Stamelos02codequality, title = {Code quality analysis in open source software development}, journal = {Information Systems Journal}, volume = {12}, year = {2002}, note = {"For our case study, we have used Logiscope{\quotesinglbase} (Telelogic, 2000), a comprehensive set of tools able to perform, automatically, code measurement and comparison with user-defined programming standards" "Using Logiscope, we examined a sample of 100 C programs found in the SUSE Linux 6.0 release." metrics collected: number of statements cyclomatic complexity maximum levels number of paths unconditional jumps comment frequency vocabulary frequency program length average size number of inputs/outputs}, pages = {43{\textendash}60}, abstract = {Proponents of open source style software development claim that better software is produced using this model compared with the traditional closed model. However, there is little empirical evidence in support of these claims. In this paper, we present the results of a pilot case study aiming: (a) to understand the implications of structural quality; and (b) to figure out the benefits of structural quality analysis of the code delivered by open source style development. To this end, we have measured quality characteristics of 100 applications written for Linux, using a software measurement tool, and compared the results with the industrial standard that is proposed by the tool. Another target of this case study was to investigate the issue of modularity in open source as this characteristic is being considered crucial by the proponents of open source for this type of software development. We have empirically assessed the relationship between the size of the application components and the delivered quality measured through user satisfaction. We have determined that, up to a certain extent, the average component size of an application is negatively related to the user satisfaction for this application.}, keywords = {C, Code quality characteristics, functions, linux, metrics, open source development, software measurement, structural code analysis, Suse, user satisfaction}, author = {Ioannis Stamelos and Lefteris Angelis and Apostolos Oikonomou and Georgios L. Bleris} } @article {flosswp57, title = {A contribution to the understanding of illegal copying of software: empirical and analytical evidence against conventional wisdom}, year = {2002}, month = {June}, abstract = {The paper analyzes different variables that affect the dynamics among copyrights, illegal copying and software market creation. There is empirical and analytical evidence supporting three major findings. First, proprietary source companies use illegal copying as a source of market creation in the early stages of development of the market. Second, this strategy has positive effects in the software market in the long-term. Third, in presence of an Open Source alternative, proprietary source companies need to use their illegal user base in order to compete better and this strategy becomes optimal.}, attachments = {https://flosshub.org/sites/flosshub.org/files/osorio.pdf}, author = {Carlos Osorio-Urzua} } @unpublished {flosswp49, title = {The Emergence of a new commercial actor: community managed software projects (Please contact the author for the dissertation)}, year = {2002}, month = {June}, abstract = {Institutional theory has matured to the point where we know a great deal about how institutions, once formed, are reproduced. We know less about how they are constructed. This study examines how social movements might inspire the creation of new organizing mechanisms. If new organizational forms result from recombination of existing elements, how might challenging and defending groups affect their construction? An inductive, ethnographic approach was used to examine interactions between community managed software projects from the free software and open source social movements (challengers) and established firms in the software industry (defenders). With interviews of seventy contributors and close examination of the practices used by four projects to manage their interactions with firms., I find that both community projects and firms made changes in their practices and form to better collaborate.}, author = {Siobhan O{\textquoteright}Mahony} } @article {flosswp41, title = {Knowing in Practice: Enacting a Collective Capability in Distributed Organizing}, journal = {Organization Science}, volume = {13}, number = {3}, year = {2002}, month = {05/2002}, abstract = {In this paper, I outline a perspective on knowing in practice which highlights the essential role of human action in knowing how to get things done in complex organizational work. The perspective suggests that knowing is not a static embedded ca- pability or stable disposition of actors, but rather an ongoing social accomplishment, constituted and reconstituted as actors engage the world in practice. In interpreting the findings of an empirical study conducted in a geographically dispersed high- tech organization, I suggest that the competence to do global product development is both collective and distributed, grounded in the everyday practices of organizational members. I conclude by discussing some of the research implications of a perspective on organizational knowing in practice.}, attachments = {https://flosshub.org/sites/flosshub.org/files/orlikowski.pdf}, author = {Wanda Orlikowski} } @conference {1163, title = {On the Nonmaintainability of Open-Source Software}, booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source}, year = {2002}, note = {"We downloaded 365 versions of Linux. For each version in turn, we examined the 17 kernel modules and counted the number of lines of code in each module. Then we counted the number of instances of common (global) coupling between each of the kernel modules and all the other modules in that version of Linux. We obtained two primary results."}, keywords = {Common coupling, coupling, lines of code, linux, linux kernel, loc, metrics}, attachments = {https://flosshub.org/sites/flosshub.org/files/SchachOffutt.pdf}, author = {Schach, Stephen R. and Offutt, Jeff} } @article {flosswp67, title = {Open Source Software Production: Climbing on the Shoulders of Giants}, year = {2002}, month = {November}, abstract = {Open source software production is a successful new production model in which a public good is voluntarily provided. We argue that by studying this new production model we gain valuable insight for organization theory beyond software production. Under specific conditions this model can be generalized, contingent on the interplay of motivational, situational, and institutional factors. It is argued that a production model building on the shoulders of predecessors and peers depends on a well balanced portfolio of intrinsic and extrinsic motivation, low costs for contributors and governance mechanisms that do not crowd out intrinsic motivation.}, attachments = {https://flosshub.org/sites/flosshub.org/files/osterlohrotakuster.pdf}, author = {Margit Osterloh and Sandra Rota} } @article {106, title = {Working for free? Motivations for participating in open-source projects}, journal = {International Journal of Electronic Commerce}, volume = {6}, number = {3}, year = {2002}, note = {Times Cited: 24}, pages = {25-39}, abstract = {The success of the Linux operating system has demonstrated the viability of open-source software, an alternative form of software development that challenges traditional assumptions about software markets. Understanding why developers participate in open-source projects is crucial for assessing the impact of open-source software. Their motivations fall into two broad categories: internal factors (e.g., intrinsic motivation, altruism) and external rewards (e.g., expected future returns, personal needs). The results of a survey administered to open-source programmers are summarized.}, author = {Hars, A. and Ou, S. S.} } @article {flosswp383, title = {Knee-jerk Anti-LOOPism and other E-mail Phenomena: Oral, Written, and Electronic Patterns in Computer-Mediated Communication}, number = {WP \3578-93}, year = {1993}, month = {June}, institution = {Massachusetts Institute of Technology}, type = {Technical Report}, address = {Cambridge, MA}, abstract = {This paper reports on an empirical investigation into the on-going electronic interaction of a natural distributed group. Prior organizational research into use of electronic media has focused primarily on usage patterns and only occasionally on a few linguistic features, while linguistics researchers have looked more closely at certain technical aspects of language use in electronic communication. Interested in a broader range of linguistic and textual features that might be exhibited in the electronic mail medium, we conducted an exploratory study of the electronic communication of a task-oriented group over a 27-month period. Using qualitative and quantitative techniques, we found that the electronic mail messages displayed features normally associated with both speech and written discourse, as well as features that seem new to the electronic medium. The use of all three patterns was influenced by characteristics of the medium, the group, and its task.}, author = {JoAnne Yates and Wanda Orlikowski} }