@proceedings {1898, title = {Challenges in Validating FLOSS Configuration}, volume = {496}, year = {2017}, month = {05/2017}, pages = {101-114}, publisher = {Springer}, abstract = {Developers invest much effort into validating configuration during startup of free/libre and open source software (FLOSS) applications. Nevertheless, hardly any tools exist to validate configuration files to detect misconfigurations earlier. This paper aims at understanding the challenges to provide better tools for configuration validation. We use mixed methodology: (1) We analyzed 2,683 run-time configuration accesses in the source-code of 16 applications comprising 50 million lines of code. (2) We conducted a questionnaire survey with 162 FLOSS contributors completing the survey. We report our experiences about building up a FLOSS community that tackles the issues by unifying configuration validation with an external configuration access specification. We discovered that information necessary for validation is often missing in the applications and FLOSS developers dislike dependencies on external packages for such validations.}, doi = {10.1007/978-3-319-57735-7_11}, url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_11}, author = {Raab, M and Barany, G} } @proceedings {1910, title = {Charting the market disruptive nature of Open Source: Experiences from Sony Mobile }, year = {2017}, month = {05/2017}, pages = {175-176}, abstract = {Open Source Software (OSS) has substantial impact on how software-intensive firms develop products and deliver value to the customers. These companies need both strategic and operational support on how to adapt OSS as a part of their products and how to adjust processes and organizations to increase the benefits from OSS participation. This work presents the key insights from the journey that Sony Mobile has made from a company developing proprietary software to a respected member of OSS communities. We framed the experiences into an Open Source Maturity Model that includes two scenarios: engineering-driven and business-driven open source. We outline the most important decisions, roles, processes and implications. }, keywords = {ecosystem, poster, software business}, author = {Mols, CE and Wnuk, K} } @proceedings {1915, title = {Classifying code comments in Java open-source software systems}, year = {2017}, note = {"we conducted an in-depth analysis of the comments in the source code files of six major OSS systems in Java"}, month = {05/2017}, pages = {227-237}, abstract = {Code comments are a key software component containing information about the underlying implementation. Several studies have shown that code comments enhance the readability of the code. Nevertheless, not all the comments have the same goal and target audience. In this paper, we investigate how six diverse Java OSS projects use code comments, with the aim of understanding their purpose. Through our analysis, we produce a taxonomy of source code comments; subsequently, we investigate how often each category occur by manually classifying more than 2,000 code comments from the aforementioned projects. In addition, we conduct an initial evaluation on how to automatically classify code comments at line level into our taxonomy using machine learning; initial results are promising and suggest that an accurate classification is within reach.}, keywords = {java, Survey}, author = {Luca Pascarella and Bacchelli, Alberto} } @conference {Murphy:2017:CEF:3017680.3017682, title = {Community Engagement with Free and Open Source Software}, booktitle = {Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education}, series = {SIGCSE {\textquoteright}17}, year = {2017}, pages = {669{\textendash}670}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {A common refrain from Senior Exit Surveys and Alumni Surveys is the desire to work on "real-world," "practical" and "hands-on" projects using industry-ready tools and development environments. To assuage this, institutions have moved towards adopting Free and Open Source Software (FOSS) as an avenue to provide meaningful, applied learning interventions to students. Through these experiences, students benefit from engagement with various communities including: the community of contributors to the FOSS project; the community of local software developers; the community of citizens who reside in the local area; the community of students at their institution and others; and, the community of people impacted by the FOSS project. These engagements motivate students, enhance their communication and technical skills, allow them to grow and become more confident, help them form professional networks, and provide the "real-world" projects they seek. In this panel, we will discuss our experiences in engaging students with five different types of communities as part of incorporating FOSS into our courses, focusing on how other educators can provide the same benefits to their students as well. In order to satisfy the time constraints of the panel, the last two authors will present together.}, keywords = {free and open source software (FOSS), humanitarian free and open source software (HFOSS), localized free and open source software (LFOSS), under-represented minorities (URM)}, isbn = {978-1-4503-4698-6}, doi = {10.1145/3017680.3017682}, url = {http://doi.acm.org/10.1145/3017680.3017682}, author = {Murphy, Christian and Buffardi, Kevin and Dehlinger, Josh and Lambert, Lynn and Veilleux, Nanette} } @proceedings {1875, title = {Considering the use of walled gardens for FLOSS project communication}, year = {2017}, month = {05/2017}, abstract = {At its core, free, libre, and open source software (FLOSS) is defined by its adherence to a set of licenses that give various freedoms to the users of the software, for example the ability to use the software, to read or modify its source code, and to distribute the software to others. In addition, many FLOSS projects and developers also champion other values related to "freedom" and "openness", such as transparency, for example in communication and decision-making, or community-orientedness, for example in broadening access, collaboration, and participation. This paper explores how one increasingly common software development practice - communicating inside non-archived, third-party "walled gardens" - puts these FLOSS values into conflict. If communities choose to use non-archived walled gardens for communication, they may be prioritizing one type of openness (broad participation) over another (transparency). We use 18 FLOSS projects as a sample to describe how walled gardens are currently being used for intra-project communication, as well as to determine whether or not these projects provide archives of these communications. Findings will be useful to the FLOSS community as a whole as it seeks to under- stand the evolution and impact of its communication choices.}, keywords = {apache, chat, communication, email, free software, irc, mailing list, open source, Slack, Stack Overflow, teams, Wordpress}, doi = {10.1007/978-3-319-57735-7_1}, url = {https://link.springer.com/content/pdf/10.1007\%2F978-3-319-57735-7_1.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/preprint_0.pdf}, author = {Squire, Megan} } @inbook {Kalliamvakou2016, title = {Certification of Open Source Software {\textendash} A Scoping Review}, booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings}, year = {2016}, pages = {111{\textendash}122}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, chapter = {Certification of Open Source Software {\textendash} A Scoping Review}, address = {Cham}, abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic. }, isbn = {978-3-319-39225-7}, doi = {10.1007/978-3-319-39225-7_9}, url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9}, author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia}, editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman} } @inbook {Murphy2016, title = {Classifying Organizational Adoption of Open Source Software: A Proposal}, booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings}, year = {2016}, pages = {123{\textendash}133}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal}, address = {Cham}, abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways. }, isbn = {978-3-319-39225-7}, doi = {10.1007/978-3-319-39225-7_10}, url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10}, author = {Murphy, Stephen and Cox, Sharon}, editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman} } @inbook {Harzl2016, title = {Combining FOSS and Kanban: An Action Research}, booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings}, year = {2016}, pages = {71{\textendash}84}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, chapter = {Combining FOSS and Kanban: An Action Research}, address = {Cham}, abstract = {Even though Free and Open Source Software (FOSS) and Agile Software Development (ASD) have been recognized as important ways to develop software, share some similarities, and have many success stories, there is a lack of research regarding the comprehensive integration of both practices. This study attempts to consolidate these methods and to answer if FOSS and ASD can be combined successfully. Action Reseach (AR) is conducted with one sub-team of a large FOSS project. We performed two action research cycles based on the Kanban method. This paper has two main contributions; first, it describes a real world situation, where Kanban is applied to a FOSS project, and second, it suggests two new Kanban practices. These two methods are targeted specifically at FOSS projects and their characteristics. }, isbn = {978-3-319-39225-7}, doi = {10.1007/978-3-319-39225-7_6}, url = {http://dx.doi.org/10.1007/978-3-319-39225-7_6}, author = {Harzl, Annemarie}, editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman} } @inbook {Crowston2016, title = {Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects}, booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings}, year = {2016}, pages = {45{\textendash}56}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, address = {Cham}, abstract = {We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication by core (committer) and peripheral community members and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We find that core and peripheral members differ in their volume of contribution and in their use of inclusive pronouns, and that volume of communication is related to project success. }, isbn = {978-3-319-39225-7}, doi = {10.1007/978-3-319-39225-7_4}, url = {http://dx.doi.org/10.1007/978-3-319-39225-7_4}, author = {Kevin Crowston and Shamshurin, Ivan}, editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman} } @article {1802, title = {Candoia: A Platform and an Ecosystem for Building and Deploying Versatile Mining Software Repositories Tools}, year = {2015}, note = {" In terms of its focus, the Candoia platform is closer to Bevan et al.{\textquoteright}s Kenyon [9], Bajracharya et al.{\textquoteright}s Sourcerer [6], Gousios and Spinellis{\textquoteright}s Alitheia Core [32, 31], Howison et al.{\textquoteright}s FLOSSMole [39] and different from Boetticher et al.{\textquoteright}s PROMISE Repository [69], Gonz{\'a}lez-Barahona and Robles{\textquoteright}s open-access data repositories [29], Black Duck OpenHub (aka Ohloh) [13], GHTorrent [30, 33], Ossher et al.{\textquoteright}s SourcererDB [64], the SourceForge Research Data Archive (SRDA) [28], and Boa [25]. }, month = {11/2015}, institution = {Iowa State University}, abstract = {Research on mining software repositories (MSR) has shown great promise during the last decade in solving many challenging software engineering problems. There exists, however, a {\textquoteleft}valley of death{\textquoteright} between these significant innovations in the MSR research and their deployment in practice. The significant cost of converting a prototype to software; need to provide support for a wide variety of tools and technologies e.g. CVS, SVN, Git, Bugzilla, Jira, Issues, etc, to improve applicability; and the high cost of customizing tools to practitioner-specific settings are some key hurdles in transition to practice. We describe Candoia, a platform and an ecosystem that is aimed at bridging this valley of death between innovations in MSR research and their deployment in practice. We have implemented Candoia and provide facilities to build and publish MSR ideas as Candoia apps. Our evaluation demonstrates that Candoia drastically reduces the cost of converting an idea to an app, thus reducing the barrier to transitioning research findings into practice. We also see versatility, in Candoia app{\textquoteright}s ability to work with a variety of tools and technologies that the platform supports. Finally, we find that customizing Candoia app to fit project-specific needs is often well within the grasp of developers.}, keywords = {Analysis of software and its evolution, Application specific development environments, flossmole cited, msr, research to practice, software evolution, software repositories}, url = {http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1378\&context=cs_techreports}, attachments = {https://flosshub.org/sites/flosshub.org/files/Candoia-\%20A\%20Platform\%20and\%20an\%20Ecosystem\%20for\%20Building\%20and\%20Deploying\%20V.pdf}, author = {Nitin M. Tiwari and Dalton D. Mills and Ganesha Upadhyaya and Eric Lin and Rajan, Hridesh} } @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 {1774, title = {Characterization and prediction of issue-related risks in software projects}, year = {2015}, month = {05/2015}, publisher = {IEEE}, abstract = {Identifying risks relevant to a software project and planning measures to deal with them are critical to the success of the project. Current practices in risk assessment mostly rely on high-level, generic guidance or the subjective judgements of experts. In this paper, we propose a novel approach to risk assessment using historical data associated with a software project. Specifically, our approach identifies patterns of past events that caused project delays, and uses this knowledge to identify risks in the current state of the project. A set of risk factors characterizing {\textquotedblleft}risky{\textquotedblright} software tasks (in the form of issues) were extracted from five open source projects: Apache, Duraspace, JBoss, Moodle, and Spring. In addition, we performed feature selection using a sparse logistic regression model to select risk factors with good discriminative power. Based on these risk factors, we built predictive models to predict if an issue will cause a project delay. Our predictive models are able to predict both the risk impact (i.e. the extend of the delay) and the likelihood of a risk occurring. The evaluation results demonstrate the effectiveness of our predictive models, achieving on average 48\%{\textendash}81\% precision, 23\%{\textendash}90\% recall, 29\%{\textendash}71\% F-measure, and 70\%{\textendash}92\% Area Under the ROC Curve. Our predictive models also have low error rates: 0.39{\textendash}0.75 for Macroaveraged Mean Cost-Error and and 0.7{\textendash}1.2 for Macro-averaged Mean Absolute Error}, url = {http://www.uow.edu.au/~hoa/papers/msr-2015-preprint.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-preprint.pdf}, author = {Morakot Choetkiertikul and Dam, Hoa Khanh and Truyen Tran and Aditya Ghose} } @proceedings {1750, title = {Co-evolution of Infrastructure and Source Code - An Empirical Study}, year = {2015}, month = {05/2015}, abstract = {Infrastructure-as-code automates the process of configuring and setting up the environment (e.g., servers, VMs and databases) in which a software system will be tested and/or deployed, through textual specification files in a language like Puppet or Chef. Since the environment is instantiated automatically by the infrastructure languages{\textquoteright} tools, no manual intervention is necessary apart from maintaining the infrastructure specification files. The amount of work involved with such maintenance, as well as the size and complexity of infrastructure specification files, have not yet been studied empirically. Through an empirical study of the version control system of 265 OpenStack projects, we find that infrastructure files are large and churn frequently, which could indicate a potential of introducing bugs. Furthermore, we found that the infrastructure code files are coupled tightly with the other files in a project, especially test files, which implies that testers often need to change infrastructure specifications when making changes to the test framework and tests.}, keywords = {openstack}, url = {http://mcis.polymtl.ca/publications/2015/msrjojo.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/msrjojo.pdf}, author = {Yujuan Jiang and Adams, Bram} } @inbook {1619, title = {The Census of the Brazilian Open-Source Community}, booktitle = {Open Source Software: Mobile Open Source Technologies}, series = {IFIP Advances in Information and Communication Technology}, volume = {427}, year = {2014}, pages = {202-211}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, abstract = { During a long time, software engineering research has been trying to better understand open-source communities and uncover two fundamental questions: (i) who are the contributors and (i) why they contribute. Most of these researches focus on well-known OSS projects, but little is known about the OSS movement in emerging countries. In this paper, we attempt to fill this gap by presenting a picture of the Brazilian open-source contributor. To achieve this goal, we examined activities from more than 12,400 programmers on Github, during the period of a year. Subsequently, we correlate our findings with a survey that was answered by more than 1,000 active contributors. Our results show that exists an OSS trend in Brazil: most part of the contributors are active, performing around 30 contributions per year, and they contribute to OSS basically by altruism. }, keywords = {Brazilian OSS Community, github, OSS}, isbn = {978-3-642-55127-7}, doi = {10.1007/978-3-642-55128-4_30}, url = {http://dx.doi.org/10.1007/978-3-642-55128-4_30}, author = {Pinto, Gustavo and Kamei, Fernando}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.} } @conference {ValdiviaGarcia:2014:CPB:2597073.2597099, title = {Characterizing and Predicting Blocking Bugs in Open Source Projects}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {72{\textendash}81}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {As software becomes increasingly important, its quality becomes an increasingly important issue. Therefore, prior work focused on software quality and proposed many prediction models to identify the location of software bugs, to estimate their fixing-time, etc. However, one special type of severe bugs is blocking bugs. Blocking bugs are software bugs that prevent other bugs from being fixed. These blocking bugs may increase maintenance costs, reduce overall quality and delay the release of the software systems. In this paper, we study blocking-bugs in six open source projects and propose a model to predict them. Our goal is to help developers identify these blocking bugs early on. We collect the bug reports from the bug tracking systems of the projects, then we obtain 14 different factors related to, for example, the textual description of the bug, the location the bug is found in and the people involved with the bug. Based on these factors we build decision trees for each project to predict whether a bug will be a blocking bug or not. Then, we analyze these decision trees in order to determine which factors best indicate these blocking bugs. Our results show that our prediction models achieve F-measures of 15-42\%, which is a two- to four-fold improvement over the baseline random predictors. We also find that the most important factors in determining blocking bugs are the comment text, comment size, the number of developers in the CC list of the bug report and the reporter{\textquoteright}s experience. Our analysis shows that our models reduce the median time to identify a blocking bug by 3-18 days.}, keywords = {Code Metrics, Post-release Defects, Process Metrics}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597099}, url = {http://doi.acm.org/10.1145/2597073.2597099}, attachments = {https://flosshub.org/sites/flosshub.org/files/garcia.pdf}, author = {Valdivia Garcia, Harold and Shihab, Emad} } @conference {Krutz:2014:CCO:2597073.2597127, title = {A Code Clone Oracle}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {388{\textendash}391}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Code clones are functionally equivalent code segments. Detecting code clones is important for determining bugs, fixes and software reuse. Code clone detection is also essential for developing fast and precise code search algorithms. How- ever, the challenge of such research is to evaluate that the clones detected are indeed functionally equivalent, consider- ing the majority of clones are not textual or even syntactically identical. The goal of this work is to generate a set of method level code clones with a high confidence to help to evaluate future code clone detection and code search tools to evaluate their techniques. We selected three open source programs, Apache, Python and PostgreSQL, and randomly sampled a total of 1536 function pairs. To confirm whether or not these function pairs indicate a clone and what types of clones they belong to, we recruited three experts who have experience in code clone research and four students who have experience in programming for manual inspection. For confidence of the data, the experts consulted multiple code clone detection tools to make the consensus. To assist manual inspection, we built a tool to automatically load function pairs of interest and record the manual inspection results. We found that none of the 66 pairs are textual identical type- 1 clones, and 9 pairs are type-4 clones. Our data is available at: http://phd.gccis.rit.edu/weile/data/cloneoracle/. }, keywords = {clone, Clone Oracle, Code Clone Detection, msr data showcase, software engineering}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597127}, url = {http://doi.acm.org/10.1145/2597073.2597127}, attachments = {https://flosshub.org/sites/flosshub.org/files/clone_oracle.pdf}, author = {Krutz, Daniel E. and Le, Wei} } @book {1591, title = {Code Review Analytics: WebKit as Case Study}, series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Mobile Open Source Technologies. 10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings}, volume = {427}, year = {2014}, pages = {1 - 10}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, address = {Berlin, Heidelberg}, abstract = {During the last years, most of the large free / open source software projects have included code review as an usual, or even mandatory practice for changes to their code. In many cases it is implemented as a process in which a developer proposing some change needs to ask for a review by another developer before it can enter the code base. Code reviews, therefore, become a critical process for the project, which could cause delays in contributions being accepted, and risk to become a bottleneck if not enough reviewers are available. In this paper we present a methodology designed to analyze the code review process, to determine its main characteristics and parameters, and to detect potential problems with it. We also present how we have applied this methodology to the WebKit project, learning about the main characteristics of how code review works in their case.}, isbn = {978-3-642-55128-4}, issn = {1868-422X}, doi = {10.1007/978-3-642-55128-4_1}, author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Mario Gallegos}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.} } @conference {Aggarwal:2014:CPD:2597073.2597120, title = {Co-evolution of Project Documentation and Popularity Within Github}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {360{\textendash}363}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Github is a very popular collaborative software-development platform that provides typical source-code management and issue tracking features augmented by strong social-networking features such as following developers and watching projects. These features help "spread the word" about individuals and projects, building the reputation of the former and increasing the popularity of the latter. In this paper, we investigate the relation between project popularity and regular, consistent documentation updates. We found strong indicators that consistently popular projects exhibited consistent documentation effort and that this effort tended to attract more documentation collaborators. We also found that frameworks required more documentation effort than libraries to achieve similar adoption success, especially in the initial phase. }, keywords = {Cross Correlation, Documentation Change, mining challenge, msr challenge, popularity}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597120}, url = {http://doi.acm.org/10.1145/2597073.2597120}, author = {Aggarwal, Karan and Hindle, Abram and Stroulia, Eleni} } @conference {Tymchuk:2014:COP:2597073.2597093, title = {Collaboration in Open-source Projects: Myth or Reality?}, booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories}, series = {MSR 2014}, year = {2014}, pages = {304{\textendash}307}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {One of the fundamental principles of open-source projects is that they foster collaboration among developers, disregarding their geographical location or personal background. When it comes to software repositories collaboration is a rather ephemeral phenomenon which lacks a clear definition, and it must therefore be mined and modeled. This throws up the question whether what is mined actually maps to reality. In this paper we investigate collaboration by modeling it using a number of diverse approaches that we then compare to a ground truth obtained by surveying a substantial set of developers of the Pharo open-source community. Our findings indicate that the notion of collaboration must be revisited, as it is undermined by a number of factors that are often tackled in imprecise ways or not taken into account at all.}, keywords = {COLLABORATION, Software ecosystems}, isbn = {978-1-4503-2863-0}, doi = {10.1145/2597073.2597093}, url = {http://doi.acm.org/10.1145/2597073.2597093}, author = {Tymchuk, Yuriy and Mocci, Andrea and Lanza, Michele} } @article {9400325220140301, title = {COLLABORATION THROUGH OPEN SUPERPOSITION: A THEORY OF THE OPEN SOURCE WAY.}, journal = {MIS Quarterly}, volume = {38}, number = {1}, year = {2014}, pages = {29 - A9}, abstract = {This paper develops and illustrates the theory of collaboration through open superposition: the process of depositing motivationally independent layers of work on top of each other over time. The theory is developed in a study of community-based free and open source software (FLOSS) development, through a research arc of discovery (participant observation), replication (two archival case studies), and theorization. The theory explains two key findings: (1) the overwhelming majority of work is accomplished with only a single programmer working on any one task, and (2) tasks that appear too large for any one individual are more likely to be deferred until they are easier rather than being undertaken through structured team work. Moreover, the theory explains how working through open superposition can lead to the discovery of a work breakdown that results in complex, functionally interdependent, work being accomplished without crippling search costs. We identify a set of socio-technical}, keywords = {COLLABORATION, COMPUTER programmers, COMPUTER programming, COMPUTER software, coordination, FREEWARE (Computer software), INFORMATION storage \& retrieval systems, open source software, research, socio-technical system}, issn = {02767783}, author = {Howison, James and Kevin Crowston} } @inbook {1606, title = {Considerations Regarding the Creation of a Post-graduate Master{\textquoteright}s Degree in Free Software}, booktitle = {Open Source Software: Mobile Open Source Technologies}, series = {IFIP Advances in Information and Communication Technology}, volume = {427}, year = {2014}, pages = {123-132}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, abstract = { Free software has gained importance over the last few years, and can be found in almost any sphere in which {\textquoteleft}software processes{\textquoteright} are important. However, even when universities and higher education establishments include subjects concerning free programming and technologies in their curriculums, their graduates tend to attain limited technological, organisational and philosophical knowledge that limits them as regards their participation in, management and development of free software projects. This gap in skills and knowledge has recently led to a series of post-graduate studies whose objective is to offer students the possibility of acquiring competencies that will allow them to become experts in free software. This paper presents a study concerning the offers for post-graduate studies in free software that currently exist, with the intention of creating similar post-graduate studies in Ecuador. }, isbn = {978-3-642-55127-7}, doi = {10.1007/978-3-642-55128-4_17}, url = {http://dx.doi.org/10.1007/978-3-642-55128-4_17}, author = {Montes Le{\'o}n, SergioRa{\'u}l and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}sM. and S{\'a}nchez C., LuisE.}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.} } @proceedings {1685, title = {Continuous integration in a social-coding world: Empirical evidence from GitHub}, year = {2014}, pages = {5 pages}, abstract = {Continuous integration is a software engineering practice of frequently merging all developer working copies with a shared main branch, e.g., several times a day. With the advent of GITHUB, a platform well known for its {\textquotedblleft}social coding{\textquotedblright} features that aid collaboration and sharing, and currently the largest code host in the open source world, collaborative software development has never been more prominent. In GITHUB development one can distinguish between two types of developer contributions to a project: direct ones, coming from a typically small group of developers with write access to the main project repository, and indirect ones, coming from developers who fork the main repository, update their copies locally, and submit pull requests for review and merger. In this paper we explore how GITHUB developers use continuous integration as well as whether the contribution type (direct versus indirect) and different project characteristics (e.g., main programming language, or project age) are associated with the success of the automatic builds.}, keywords = {github}, url = {http://conferences.computer.org/icsme/2014/papers/6146a401.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/ICSME2014ERA.pdf}, author = {Vasilescu, Bogdan and Serebrenik, Alexander and Schuylenberg, Stef and Wulms, Jules and Brand, Mark G.J.} } @inbook {1605, title = {Crafting a Systematic Literature Review on Open-Source Platforms}, booktitle = {Open Source Software: Mobile Open Source Technologies}, series = {IFIP Advances in Information and Communication Technology}, volume = {427}, year = {2014}, pages = {113-122}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, abstract = { This working paper unveils the crafting of a systematic literature review on open-source platforms. The high-competitive mobile devices market, where several players such as Apple, Google, Nokia and Microsoft run a platforms- war with constant shifts in their technological strategies, is gaining increasing attention from scholars. It matters, then, to review previous literature on past platforms-wars, such as the ones from the PC and game-console industries, and assess its implications to the current mobile devices platforms-war. The paper starts by justifying the purpose and rationale behind this literature review on open-source platforms. The concepts of open-source software and computer-based platforms were then discussed both individually and in unison, in order to clarify the core-concept of {\textquotedblleft}open-source platform{\textquotedblright} that guides this literature review. The detailed design of the employed methodological strategy is then presented as the central part of this paper. The paper concludes with preliminary findings organizing previous literature on open-source platforms for the purpose of guiding future research in this area. }, keywords = {Ecosystems, FLOSS, open-source, Platforms, R\&D Management}, isbn = {978-3-642-55127-7}, doi = {10.1007/978-3-642-55128-4_16}, url = {http://dx.doi.org/10.1007/978-3-642-55128-4_16}, author = {Teixeira, Jose and Baiyere, Abayomi}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.} } @conference {1694, title = {Cream of the crop}, booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14}, year = {2014}, pages = {1 - 10}, publisher = {ACM Press}, organization = {ACM Press}, address = {Berlin, GermanyNew York, New York, USA}, abstract = {In open content communities like Wikipedia and StackOverflow and in open source software projects, a small proportion of users produce a majority of the content and take on much of the required community maintenance work. Understanding this class of users is crucial to creating and sustaining healthy communities. We carried out a mixed-method study of core contributors to the Cyclopath geographic wiki and bicycle routing web site. We present our findings and organize our discussion using concepts from activity theory. We found that the Cyclopath core contributors aren{\textquoteright}t the dedicated cyclists and that the characteristics of the community shape the site, the rules, and the tools for contributing. Additionally, we found that numerous aspects about the surrounding ecology of related systems and communities may help to shape how the site functions and views itself. We draw implications for future research and design from these findings. }, isbn = {9781450330169}, doi = {10.1145/2641580.2641609}, author = {Katherine Panciera and Mikhil Masli and Loren Terveen} } @inbook {1620, title = {Cuban GNU/Linux Nova Distribution for Server Computers}, booktitle = {Open Source Software: Mobile Open Source Technologies}, series = {IFIP Advances in Information and Communication Technology}, volume = {427}, year = {2014}, pages = {212-215}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, abstract = { This article presents the novelties offered by the new version of GNU / Linux Nova distribution in its server edition, exposing the new features such as network attached storage, distributed files system, charge balance for PostgreSQL database servers and thin clients, as well as the basic features of a standard server. All these developments are obtained from the integration with the server management platform Zentyal designed to facilitate the work of the end users of the variant of this Cuban distribution. }, isbn = {978-3-642-55127-7}, doi = {10.1007/978-3-642-55128-4_31}, url = {http://dx.doi.org/10.1007/978-3-642-55128-4_31}, author = {Rosales Rosa, Eugenio and Fuentes Rodr{\'\i}guez, JuanManuel and F{\'\i}rvida Don{\'e}stevez, AbelAlfonso and Garc{\'\i}a Rivas, Dairelys}, editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.} } @proceedings {1491, title = {Communication in Open Source Software Development Mailing Lists}, year = {2013}, note = {"The entire dataset used in the experiment, including the cards, the resolved aliases, and detailed statistical results, can be downloaded from ..." http://www.st.ewi.tudelft.nl/~guzzi/oss-communication/}, month = {05/2013}, pages = {277-286}, abstract = {Open source software (OSS) development teams use electronic means, such as emails, instant messaging, or forums, to conduct open and public discussions. Researchers investigated mailing lists considering them as a hub for project communication. Prior work focused on specific aspects of emails, for example the handling of patches, traceability concerns, or social networks. This led to insights pertaining to the investigated aspects, but not to a comprehensive view of what developers communicate about. Our objective is to increase the understanding of development mailing lists communication. We quantitatively and qualitatively analyzed a sample of 506 email threads from the development mailing list of a major OSS project, Lucene. Our investigation reveals that implementation details are discussed only in about 35\% of the threads, and that a range of other topics is discussed. Moreover, core developers participate in less than 75\% of the threads. We observed that the development mailing list is not the main player in OSS project communication, as it also includes other channels such as the issue repository.}, keywords = {email, lucene, mailling list}, url = {http://www.st.ewi.tudelft.nl/~guzzi/downloads/Guzzi2013msr.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/Guzzi2013msr.pdf}, author = {Guzzi, Anja and Bacchelli, Alberto and Lanza, Michele and Pinzger, Martin and van Deursen, Arie} } @book {1536, title = {Community Dynamics in Open Source Software Projects: Aging and Social Reshaping}, series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification}, volume = {404}, year = {2013}, pages = {80 - 96}, publisher = {Springer Berlin Heidelberg}, organization = {Springer Berlin Heidelberg}, address = {Berlin, Heidelberg}, abstract = { An undeniable factor for an open source software (OSS) project success is a vital community built around it. An OSS community not only needs to be established, but also to be persisted. This is not guaranteed considering the voluntary nature of participation in OSS. The dynamic analysis of the OSS community evolution can be used to extract indicators to rate the current stability of a community and to predict its future development. Despite the great amount of studies on mining project communication and development repositories, the evolution of OSS communities is rarely addressed. This paper presents an approach to analyze the OSS community history. We combine adapted demography measures to study community aging and social analysis to investigate the dynamics of community structures. The approach is applied to the communication and development history of three bioinformatics OSS communities over eleven years. First, in all three projects a survival rate pattern is identified. This finding allows us to define the minimal number of newcomers required for the further positive community growth. Second, dynamic social analysis shows that the node betweenness in combination with the network diameter can be used as an indicator for significant changes in the community core and the quality of community recovery after these modifications. }, isbn = {978-3-642-38928-3}, issn = {1868-422X}, doi = {10.1007/978-3-642-38928-3_6}, author = {Hannemann, Anna and Klamma, Ralf}, editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto} } @article {1679, title = {Carrots and Rainbows: Motivation and Social Practice in Open Source Software Development}, journal = {Management Information Systems Quarterly}, volume = {36}, year = {2012}, pages = {649-676}, abstract = {Open source software (OSS) is a social and economic phenomenon that raises fundamental questions about the motivations of contributors to information systems development. Some developers are unpaid volunteers who seek to solve their own technical problems, while others create OSS as part of their employment contract. For the past 10 years, a substantial amount of academic work has theorized about and empirically examined developer motivations. We review this work and suggest considering motivation in terms of the values of the social practice in which developers participate. Based on the social philosophy of Alasdair MacIntyre, we construct a theoretical framework that expands our assumptions about individual motivation to include the idea of a long-term, value-informed quest beyond short-term rewards. This motivation{\textendash}practice framework depicts how the social practice and its supporting institutions mediate between individual motivation and outcome. The framework contains three theoretical conjectures that seek to explain how collectively elaborated standards of excellence prompt developers to produce high-quality software, change institutions, and sustain OSS development. From the framework, we derive six concrete propositions and suggest a new research agenda on motivation in OSS. }, url = {https://sspaeth.de/uploads/CarrotsAndRainbows.pdf}, author = {Georg von Krogh and Stefan Haefliger and Sebastian Spaeth and Martin W. Wallin} } @proceedings {1443, title = {Citizen Engineering: Evolving OSS Practices to Engineering Design and Analysis}, volume = {378}, year = {2012}, month = {09/2012}, pages = {61-77}, publisher = {IFIP AICT}, abstract = {Open Source Software (OSS) development has much in common with concepts such as crowdsourcing, citizen science, collective intelligence, human-based computation, and what we call {\textquotedblleft}Citizen Engineering (CE){\textquotedblright}. We report on several pilot projects that apply these shared principles of OSS development to engineering activities beyond software engineering. CE models harness human computing power from open communities, which commonly consist of a cohort of geographically and/or institutionally scattered citizens - professionals or amateurs - to collaboratively solve real-world problems. In most cases, the problems targeted are challenging to computers, but manageable or trivial to human intelligence. In these systems, while humans play fundamental roles, whether they are project architects or problem solvers, the implementation of CE is greatly facilitated by the advance of information technology, particularly the Internet, considered as "creative mode of user interactivity, not merely a medium between messages and people" [10]. In this paper, we characterize existing citizen engineering practices into 6 major categories, followed by a discussion of 4 ongoing projects, aiming to provide new perspectives and insights for achieving successful CE project designs.}, author = {Zhai, Zhi and Kijewski-Correa, Tracy and Kareem, Ashan and Hachen, David and Madey, Gregory} } @article {1401, title = {Clones: what is that smell?}, journal = {Empirical Software Engineering}, volume = {17}, year = {2012}, month = {8/2012}, pages = {503 - 530}, abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell (Fowler et al. 1999) and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses the relationship between cloning and defect proneness. For the four medium to large open source projects that we studied, we find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Third, we find little evidence that clones with more copies are actually more error prone. Fourth, we find little evidence to support the claim that clone groups that span more than one file or directory are more defect prone than collocated clones. Finally, we find that developers do not need to put a disproportionately higher effort to fix clone dense bugs. Our findings do not support the claim that clones are really a {\textquotedblleft}bad smell{\textquotedblright} (Fowler et al. 1999). Perhaps we can clone, and breathe easily, at the same time. }, issn = {1573-7616}, doi = {10.1007/s10664-011-9195-3}, author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar} } @proceedings {1439, title = {A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes}, volume = {378}, year = {2012}, pages = {1-14}, publisher = {IFIP AICT}, abstract = {Summary. In general it is assumed that a software product evolves within the authoring company or group of developers that develop the project. However, in some cases different groups of developers make the software evolve in different directions, a situation which is commonly known as a fork. In the case of free software, although forking is a practice that is considered as a last resort, it is inherent to the four freedoms. This paper tries to shed some light on the practice of forking. Therefore, we have identified significant forks, several hundreds in total, and have studied them in depth. Among the issues that have been analyzed for each fork is the date when the forking occurred, the reason of the fork, and the outcome of the fork, i.e., if the original or the forking project are still developed. Our investigation shows, among other results, that forks occur in every software domain, that they have become more frequent in recent years, and that very few forks merge with the original project.}, keywords = {forking, forks, free software, Legal, open source, social, software evolution, sustainability}, attachments = {https://flosshub.org/sites/flosshub.org/files/paper_0.pdf}, author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.} } @conference {1485, title = {A Conceptual Framework for Open Source Software Test Process}, booktitle = {2012 IEEE 36th IEEE Annual Computer Software and Applications Conference Workshops (COMPSACW)}, year = {2012}, pages = {458 - 463}, publisher = {IEEE}, organization = {IEEE}, address = {Izmir, Turkey}, abstract = {The broad acceptance and use of Open Source Software (OSS) has underscored the necessity of investigating the means of assuring their quality. With the aim of identifying an OSS test process, three well-known OSS projects, namely Apache HTTP server, Mozilla Web browser, and NetBeans IDE were studied. In these studies, three activities were found similar to the activities of the ISO/IEC Test Process Standard. However, major differences were observed in tasks related to each of the test process activities. To systematize the OSS test process, an Open Source Software Test Process Framework (OSS-TPF) is proposed. The alignment of OSS-TPF with the ISO/IEC Test Process Standard is illustrated.}, isbn = {978-0-7695-4758-9}, doi = {10.1109/COMPSACW.2012.87}, url = {http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6341619}, author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj} } @conference {1357, title = {Content classification of developer emails}, booktitle = {Proceedings of the 34th IEEE/ACM International Conference On Software Engineering (ICSE 2012)}, year = {2012}, note = {We created a web application to manually classify email content in the chosen categories. We classified a statistically significant set of emails from four java open source software (OSS) systems, used to evaluate the accuracy of our approach. The contributions of this paper are: 1) a novel approach that fuses parsing and ML techniques for classification of email lines; 2) a web application to manually classify email content; 3) the manual classification of a statistically significant sample set of emails (for a total of 67,792 lines) from mailing lists of four different software systems{\textendash}in the form of a freely available benchmark; and 4) the empirical evaluation of our approach against the benchmark}, month = {06/2012}, abstract = {Emails related to the development of a software system contain information about design choices and issues encountered during the development process. Exploiting the knowledge embedded in emails with automatic tools is challenging, due to the unstructured, noisy and mixed language nature of this communication medium. Natural language text is often not well-formed and is interleaved with languages with other syntaxes, such as code or stack traces. We present an approach to classify email content at line level. Our technique classifies email lines in five categories (i.e., text, junk, code, patch, and stack trace) to allow one to subsequently apply ad hoc analysis techniques for each category. We evaluated our approach on a statistically significant set of emails gathered from mailing lists of four unrelated open source systems.}, keywords = {email, Emails, Empirical software engineering, mailing list, natural language, Unstructured Data Mining}, url = {http://www.inf.usi.ch/phd/bacchelli/publications.php}, attachments = {https://flosshub.org/sites/flosshub.org/files/icse2012.pdf}, author = {Bacchelli, Alberto and Dal Sasso, Tommaso and D{\textquoteright}Ambros, Marco and Lanza, Michele} } @proceedings {1289, title = {Cliff Walls: An Analysis of Monolithic Commits Using Latent Dirichlet Allocation}, year = {2011}, note = {"Our data set consists of the version control logs of almost 10,000 projects from SourceForge, acquired in late 2006"}, month = {10/2011}, pages = {282-298}, publisher = {Springer}, abstract = {Artifact-based research provides a mechanism whereby researchers may study the creation of software yet avoid many of the difficulties of direct observation and experimentation. However, there are still many challenges that can affect the quality of artifact-based studies, especially those studies examining software evolution. Large commits, which we refer to as {\textquotedblleft}Cliff Walls,{\textquotedblright} are one significant threat to studies of software evolution because they do not appear to represent incremental development. We used Latent Dirichlet Allocation to extract topics from over 2 million commit log messages, taken from 10,000 SourceForge projects. The topics generated through this method were then analyzed to determine the causes of over 9,000 of the largest commits. We found that branch merges, code imports, and auto-generated documentation were significant causes of large commits. We also found that corrective maintenance tasks, such as bug fixes, did not play a significant role in the creation of large commits.}, keywords = {artifacts, commit, cvs, LDA, lines of code, log files, scm, sloc, sourceforge, version control}, author = {Pratt, Landon J. and MacLean, Alexander C. and Knutson, Charles D. and Ringger, Eric K.} } @article {1383, title = {A comparative study of challenges in integrating Open Source Software and Inner Source Software}, journal = {Information and Software Technology}, volume = {53}, year = {2011}, month = {12/2011}, pages = {1319 - 1336}, abstract = {Context Several large software-developing organizations have adopted Open Source Software development (OSSD) practices to develop in-house components that are subsequently integrated into products. This phenomenon is also known as {\textquotedblleft}Inner Source{\textquotedblright}. While there have been several reports of successful cases of this phenomenon, little is known about the challenges that practitioners face when integrating software that is developed in such a setting. Objective The objective of this study was to shed light on challenges related to building products with components that have been developed within an Inner Source development environment. Method Following an initial systematic literature review to generate seed category data constructs, we performed an in-depth exploratory case study in an organization that has a significant track record in the implementation of Inner Source. Data was gathered through semi-structured interviews with participants from a range of divisions across the organization. Interviews were transcribed and analyzed using qualitative data analysis techniques. Results We have identified a number of challenges and approaches to address them, and compared the findings to challenges related to development with OSS products reported in the literature. We found that many challenges identified in the case study could be mapped to challenges related to integration of OSS. Conclusion The results provide important insights into common challenges of developing with OSS and Inner Source and may help organizations to understand how to improve their software development practices by adopting certain OSSD practices. The findings also identify the areas that need further research. Highlights ► We performed a case study that has adopted Open Source development practices. ► We studied the challenges encountered and approaches taken by the organization. ► We performed a systematic review to identify challenges related to Open Source. ► We compared the findings from the review to the findings from the case study. ► Most identified challenges could be mapped to the findings from the literature.}, keywords = {Open Source Software; Inner Source; Software development; Challenges; Case study; Empirical studies}, issn = {09505849}, doi = {10.1016/j.infsof.2011.06.007}, url = {http://www.sciencedirect.com/science/article/pii/S095058491100142X}, author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris and Fitzgerald, Brian} } @conference {968, title = {Can development work describe itself?}, 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 = {191 - 200}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {Work descriptions are informal notes taken by developers to summarize work achieved in a particular session. Existing studies indicate that maintaining them is a distracting task, which costs a developer more than 30 min. a day. The goal of this research is to analyze the purposes of work descriptions, and find out if automated tools can assist developers in efficiently creating them. For this, we mine a large dataset of heterogeneous work descriptions from open source and commercial projects. We analyze the semantics of these documents and identify common information entities and granularity levels. Information on performed actions, concerned artifacts, references and new work, shows the work management purpose of work descriptions. Information on problems, rationale and experience shows their knowledge sharing purpose. We discuss how work description information, in particular information used for work management, can be generated by observing developers{\textquoteright} interactions. Our findings have many implications for next generation software engineering tools.}, keywords = {developer interactions, work descriptions}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463344}, author = {Maalej, Walid and Happel, Hans-Jorg} } @conference {954, title = {Clones: What is that smell?}, 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 = {72 - 81}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses relationship between cloning and defect proneness. We find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Finally, we find little evidence that clones with more copies are actually more error prone. Our findings do not support the claim that clones are really a "bad smell". Perhaps we can clone, and breathe easy, at the same time.}, keywords = {apache, bug fix revisions, bugs, clone, evolution, gimp, nautilus, scm, source code}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463343}, attachments = {https://flosshub.org/sites/flosshub.org/files/72rahman2010cws.pdf}, author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar} } @conference {958, title = {Cloning and copying between GNOME projects}, 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 = {98 - 101}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {This paper presents an approach to automatically distinguish the copied clone from the original in a pair of clones. It matches the line-by-line version information of a clone to the pair{\textquoteright}s other clone. A case study on the GNOME Desktop Suite revealed a complex flow of reused code between the different subprojects. In particular, it showed that the majority of larger clones (with a minimal size of 28 lines or higher) exist between the subprojects and more than 60\% of the clone pairs can be automatically separated into original and copy.}, keywords = {clone, gnome, msr challenge, source code}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463290}, attachments = {https://flosshub.org/sites/flosshub.org/files/98Coning.pdf}, author = {Krinke, Jens and Gold, Nicolas and Jia, Yue and Binkley, David} } @inbook {836, title = {Collaboration Practices and Affordances in Free/Open Source Software Development}, booktitle = {Collaborative Software Engineering}, year = {2010}, pages = {307-328}, publisher = {Springer}, organization = {Springer}, abstract = {This chapter examines collaborative work practices, development processes, project and community dynamics, and other socio-technical relationships in free and open source software development (FOSSD). It also describes what kinds of collaboration affordances facilitate collaborative work in FOSSD projects. It reviews a set of empirical studies of FOSSD that articulate different levels of analysis. Finally, there is discussion of limitations and constraints in understanding what collaboration practices and affordances arise in FOSSD studies and how they work, and then to emerging opportunities for future FOSSD studies.}, attachments = {https://flosshub.org/sites/flosshub.org/files/CoSE-Scacchi-Chapter.pdf}, author = {Walt Scacchi}, editor = {Finkelstein, A. and van der Hoek, A. and Grundy, J. and Mistr{\'\i}k, I. and Whitehead, J.} } @conference {960, title = {A comparative exploration of FreeBSD bug lifetimes}, 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 = {106 - 109}, publisher = {IEEE}, organization = {IEEE}, address = {Cape Town, South Africa}, abstract = {In this paper, we explore the viability of mining the basic data provided in bug repositories to predict bug lifetimes. We follow the method of Lucas D. Panjer as described in his paper, Predicting Eclipse Bug Lifetimes. However, in place of Eclipse data, the FreeBSD bug repository is used. We compare the predictive accuracy of five different classification algorithms applied to the two data sets. In addition, we propose future work on whether there is a more informative way of classifying bugs than is considered by current bug tracking systems.}, keywords = {bug reports, bug tracking, classification, eclipse, msr challenge, prediction}, isbn = {978-1-4244-6802-7}, doi = {10.1109/MSR.2010.5463291}, attachments = {https://flosshub.org/sites/flosshub.org/files/106ChallengeGargi.pdf}, author = {Bougie, Gargi and Treude, Christoph and Daniel M. German and Storey, Margaret-Anne} } @conference {1483, title = {Creating and evolving developer documentation}, booktitle = {Proceedings of the eighteenth ACM SIGSOFT international symposium}, year = {2010}, pages = {127}, publisher = {ACM Press}, organization = {ACM Press}, address = {Santa Fe, New Mexico, USANew York, New York, USA}, abstract = {Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects{\textquoteright} community positively impacted the documentation.}, isbn = {9781605587912}, doi = {10.1145/1882291.1882312}, author = {Dagenais, Barth{\'e}l{\'e}my and Robillard, Martin P.} } @conference {609, title = {The Case Study of an F/OSS Virtualization Platform Deployment and Quantitative Results}, 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 = {367 - 367}, publisher = {Springer}, organization = {Springer}, chapter = {41}, abstract = {In this paper we present practical experiences and results from the deployment of an F/OSS virtualization platform. EKT{\textquoteright}s (NDC) core IT infrastructure was transformed to a virtualized one, using exclusively F/OSS, while severe budget and timing constraints were in place. This migration was initiated in order to better cope with EKT{\textquoteright}s services requirements, while accommodating at the same time the need for the in house development of a large scale open access infrastructure. The benefits derived from this migration were not only generic virtualization benefits, such as the quantifiable reduced power consumption and cost reduction through consolidation, but also F/OSS virtualization specific ones. }, issn = {978-3-642-02031-5}, doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_41}, attachments = {https://flosshub.org/sites/flosshub.org/files/Case\%20Study\%20of\%20an\%20F\%20OSS.pdf}, author = {Stathopoulos, Panagiotis and Soumplis, Alexandros and Houssos, Nikos} } @conference {587, title = {Challenges of the Open Source Component Marketplace in the Industry}, booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)}, series = {IFIP Advances in Information and Communication Technology }, year = {2009}, month = {2009///}, pages = {213 - 224}, publisher = {Springer}, organization = {Springer}, chapter = {19}, abstract = {The reuse of Open Source Software components available on the Internet is playing a major role in the development of Component Based Software Systems. Nevertheless, the special nature of the OSS marketplace has taken the {\textquotedblleft}classical{\textquotedblright} concept of software reuse based on centralized repositories to a completely different arena based on massive reuse over Internet. In this paper we provide an overview of the actual state of the OSS marketplace, and report preliminary findings about how companies interact with this marketplace to reuse OSS components. Such data was gathered from interviews in software companies in Spain and Norway. Based on these results we identify some challenges aimed to improve the industrial reuse of OSS components. }, issn = {978-3-642-02031-5}, doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_19}, attachments = {https://flosshub.org/sites/flosshub.org/files/Challenges\%20of\%20the\%20Open\%20Source.pdf}, author = {Ayala, Claudia and Hauge, {\O}yvind and Conradi, Reidar and Franch, Xavier and Li, Jingyue and Velle, Ketil} } @conference {582, title = {Choosing Open Source ERP Systems: What Reasons Are There For Doing So?}, 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 = {143 - 155}, publisher = {Springer}, organization = {Springer}, chapter = {14}, abstract = {Enterprise resource planning (ERP) systems attract a high attention and open source software does it as well. The question is then if, and if so, when do open source ERP systems take off. The paper describes the status of open source ERP systems. Based on literature review of ERP system selection criteria based on Web of Science articles, it discusses reported reasons for choosing open source or proprietary ERP systems. Last but not least, the article presents some conclusions that could act as input for future research. The paper aims at building up a foundation for the basic question: What are the reasons for an organization to adopt open source ERP systems. }, issn = {978-3-642-02031-5}, doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_14}, attachments = {https://flosshub.org/sites/flosshub.org/files/Choosing\%20Open\%20Source\%20ERP.pdf}, author = {Johansson, Bj{\"o}rn and Sudzina, Frantisek} } @conference {929, title = {Code siblings: Technical and legal implications of copying code between applications}, 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 = {81 - 90}, publisher = {IEEE}, organization = {IEEE}, address = {Vancouver, BC, Canada}, abstract = {Source code cloning does not happen within a single system only. It can also occur between one system and another. We use the term code sibling to refer to a code clone that evolves in a different system than the code from which it originates. Code siblings can only occur when the source code copyright owner allows it and when the conditions imposed by such license are not incompatible with the license of the destination system. In some situations copying of source code fragments are allowed - legally - in one direction, but not in the other. In this paper, we use clone detection, license mining and classification, and change history techniques to understand how code siblings - under different licenses - flow in one direction or the other between Linux and two BSD Unixes, FreeBSD and OpenBSD. Our results show that, in most cases, this migration appears to happen according to the terms of the license of the original code being copied, favoring always copying from less restrictive licenses towards more restrictive ones. We also discovered that sometimes code is inserted to the kernels from an outside source.}, keywords = {bsd, fossology, freebsd, linux, openbsd, source code}, isbn = {978-1-4244-3493-0}, doi = {10.1109/MSR.2009.5069483}, attachments = {https://flosshub.org/sites/flosshub.org/files/81CodeSiblings.pdf}, author = {Daniel M. German and Di Penta, Massimiliano and Gueheneuc, Yann-Gael and Antoniol, Giuliano} } @article {1344, title = {Collaboration in Open Source Domains}, journal = {International Journal of Open Source Software and Processes}, volume = {1}, year = {2009}, pages = {17 - 28}, abstract = {Free and open source software (F/OSS) developers have a tendency to build feature-centric projects rather than following a user-centered design, ignoring the necessity of usability in the resulting product. While there are many reasons behind this, the main cause can be stated as the lack of awareness of usability from developers{\textquoteright} point of view and little interaction of project stakeholders with Human-Computer Interaction (HCI) studies. This chapter examines different types of collaboration methods of usability experts and developers focusing particularly on open source projects, together with potential issues envisaged during the communication phases. The chapter also focuses on the collaboration trends and patterns of HCI experts, developers and users with an emphasis on concerns related to inefficient exploitation of current tools and technologies and provide an open usability engineering method which could be exploited in distributed projects}, issn = {1942-3934}, doi = {10.4018/jossp.2009070102}, author = {G{\"o}rkem {\c C}etin and G{\"o}kt{\"u}rk, Mehmet} } @article {1241, title = {Collaborative Software Development Using R-Forge}, journal = {The R Journal}, volume = {1}, number = {1}, year = {2009}, month = {05/2009}, pages = {9-14}, abstract = {Open source software (OSS) is typically created in a decentralized self-organizing process by a community of developers having the same or similar interests (see the famous essay by Raymond, 1999). A key factor for the success of OSS over the last two decades is the Internet: Developers who rarely meet face-to-face can employ new means of communication, both for rapidly writing and deploying software (in the spirit of Linus Torvald{\textquoteright}s {\textquotedblleft}release early, release often paradigm{\textquotedblright}). Therefore, many tools emerged that assist a collaborative software development process, including in particular tools for source code management (SCM) and version control. In the R world, SCM is not a new idea; in fact, the R Development Core Team has always been using SCM tools for the R sources, first by means of Concurrent Versions System (CVS, see Cederqvist et al., 2006), and then via Subversion (SVN, see Pilato et al., 2004). A central repository is hosted by ETH Zürich mainly for managing the development of the base R system. Mailing lists like R-help, R-devel and many others are currently the main communication channels in the R community. First, we present the core features that R- Forge offers to the R community. Second, we give a hands-on tutorial on how users and developers can get started with R-Forge. In particular, we illustrate how people can register, set up new projects, use R- Forge{\textquoteright}s SCM facilities, provide their packages on R-Forge, host a project-specific website, and how package maintainers submit a package to the Compre- hensive R Archive Network (CRAN, http://CRAN. R-project.org/). Finally, we summarize recent developments and give a brief outlook to future work.}, keywords = {forge, R, scm, source code repositories, statistics}, attachments = {https://flosshub.org/sites/flosshub.org/files/rjournal.pdf}, author = {Stefan Theu{\ss}l and Achim Zeileis} } @conference {1264, title = {The Commit Size Distribution of Open Source Software}, booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)}, year = {2009}, note = {"We use the database of the open source analytics firm Ohloh Inc." "This article is based on a March 2008 database snapshot, which contains 9,363 completely crawled and analyzed projects covering a time frame from January 1990 to February 2008." "The Ohloh database provides the complete configuration management history of each crawled project (to the extent available on the web). Thus, every single commit action of all the projects over their entire history is available." "We measure the size of commits in this paper in source lines of code (SLoC) using Ohloh{\textquoteright}s own open source diff too"}, pages = {1 - 8}, publisher = {IEEE}, organization = {IEEE}, address = {Waikoloa, Hawaii, USA}, abstract = {With the growing economic importance of open source, we need to improve our understanding of how open source software development processes work. The analysis of code contributions to open source projects is an important part of such research. In this paper we analyze the size of code contributions to more than 9,000 open source projects. We review the total distribution and distinguish three categories of code contributions using a size-based heuristic: single focused commits, aggregate team contributions, and repository refactorings. We find that both the overall distribution and the individual categories follow a power law. We also suggest that distinguishing these commit categories by size will benefit future analyses.}, keywords = {commits, configuration management, history, lines of code, sloc, source code}, isbn = {978-0-7695-3450-3}, doi = {10.1109/HICSS.2009.421}, attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-07.pdf}, author = {Arafat, O. and Dirk Riehle} } @article {1349, title = {Communication Network Characteristics of Open Source Communities}, journal = {International Journal of Open Source Software and Processes}, volume = {1}, year = {2009}, pages = {26 - 48}, abstract = {Empirical research has shown that social network structure is a critical success factor for various kinds of work groups. The authors extended this research to a new type of work group{\textemdash}the open source software project community{\textemdash}with the objective of exploring the role of communication networks within these intriguing projects. Using archival data from 143 open source project groups, the authors compiled six measures of social network structure and analyzed these in relation to four measures of group success. This study found that the social network structures of these project communities did not appear to be critical success factors at all, but rather they had no significant impact on success or their effect was opposite of that seen in prior studies of work groups. Various conjectures were suggested that might explain these results, offering opportunities for further research.}, issn = {1942-3934}, doi = {10.4018/jossp.2009100102}, author = {Hinds, David and Lee, Ronald M.} } @article {1414, title = {Competition and production of digital public goods}, journal = {International Journal of Intelligent Control and Systems}, volume = {14}, number = {1}, year = {2009}, pages = {77-86}, chapter = {77}, abstract = {With the Internet has come the phenomenon of people volunteering to work on digital public goods such as open source software and online encyclopedia articles. Presumably, the success of individual public goods has an effect on attracting volunteers. However, the definition of success is ill-defined. This paper explores the impact of different success metrics on a simple public goods model. The findings show that the different success metrics considered do have an impact on the behavior of the model, with the largest differences being between consumer-oriented and producer-oriented metrics. This indicates that many proposed success metrics may be mapped into one of these two categories and within a category, all success metrics measure the same phenomenon. We argue that the characteristics of producer-oriented metrics more closely match real world phenomena, indicating that public goods are driven by producer, and not consumer, interests.}, keywords = {digital public goods, FLOSS, open source software, sourceforge, success metrics, wikipedia}, url = {http://www.public.asu.edu/~majansse/pubs/ijics2009.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/ijics2009.pdf}, author = {Radtke, Nicholas P. and Janssen, Marco A.} } @article {1341, title = {Consumer Welfare and Market Structure in a Model of Competition between Open Source and Proprietary Software}, journal = {International Journal of Open Source Software and Processes}, volume = {1}, year = {2009}, pages = {43 - 65}, abstract = {I consider a Vickrey-Salop model of spatial product differentiation with quasi-linear utility functions and contrast two modes of production, the proprietary model where entrepreneurs sell software to the users, and the open source model where users participate in software development. I show that the OS model of production may be more efficient from the point of view of welfare than the proprietary model, but that an OS industry is vulnerable to entry by entrepreneurs while a proprietary industry can resist entry by OS projects. A mixed industry where OS and proprietary development methods coexist may exhibit large OS projects cohabiting with more specialized proprietary projects, and is more efficient than the proprietary model of production from the point of view of welfare.}, issn = {1942-3934}, doi = {10.4018/jossp.2009040104}, author = {Gaudeul, Alexia} } @article {1347, title = {A Cost Model of Open Source Software Adoption}, journal = {International Journal of Open Source Software and Processes}, volume = {1}, year = {2009}, pages = {60 - 82}, abstract = {A limited budget for IT may lock public bodies in obsolete inefficient solutions slowing down their process of innovation. Various actions of estimating, controlling, and reducing IT costs have been already performed at national and European levels and Open Source Software (OSS) has been often pointed as a promising alternative that may also render public services and the underlying business processes more transparent and accessible to citizens. In this chapter, we propose a model of cost of a migration to OSS as a decision making instrument that helps public bodies being autonomous and independent in the IT adoption. The model is empirically validated in the real daily operations of more than 3,500 users. If adopted systematically our model might be a powerful tool to support transformational government and to establish an empirical open knowledge base on the economic advantages of OSS on which to found future strategies of OSS adoption.}, issn = {1942-3934}, doi = {10.4018/jossp.2009070105}, author = {Russo, Barbara and Succi, Giancarlo} } @conference {581, title = {Customization of Open Source Software in Companies}, 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 = {129 - 142}, publisher = {Springer}, organization = {Springer}, chapter = {13}, abstract = {Most papers related to Open Source Software (OSS) discuss the development of OSS, licensing issues, and motivations of developers. Research in the area of customization of OSS is rare, however. The process after the deployment of an OSS within a company remains unknown. There is a danger that it is often unstructured and error-prone since OSS develops in a more complex way than proprietary software. Based on our literature study, modifications of open source code do occur also in organizations outside of the software industry. Customization of applications is more common than customization of infrastructure software in these organizations. Therefore, we examine the process of deployment and adaptation of an OSS application software over several update iterations in great detail. This examination shows that this process has similarities with the process of deployment of proprietary software but it also exhibits important differences. Based on this case study, we also suggest a process model for customization of OSS applications in user organizations. }, issn = {978-3-642-02031-5}, doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_13}, attachments = {https://flosshub.org/sites/flosshub.org/files/Customization\%20of\%20Open\%20Source\%20Software.pdf}, author = {Ke{\ss}ler, Steffen and Alpar, Paul} } @article {1391, title = {Challenges and strategies in the use of Open Source Software by Independent Software Vendors}, journal = {Information and Software Technology}, volume = {50}, year = {2008}, month = {8/2008}, pages = {991 - 1002}, abstract = {Open Source Software (OSS) has already been adopted by a large number of organizations. An important {\textendash} but sometimes neglected {\textendash} group of OSS users are Independent Software Vendors (ISVs). ISVs often develop their applications on top of OSS platform software. Frequently, this requires making several extensions and modifications to these OSS components. We identify a number of challenges that ISVs face in handling these extensions and modifications. Next, we describe several strategies ISVs can follow in maintaining these modifications. Finally, we suggest an opportunity for a closer collaboration between OSS projects and ISVs which could be mutually beneficial.}, keywords = {Contributing, Independent Software Vendor}, issn = {09505849}, doi = {10.1016/j.infsof.2007.09.001}, author = {Ven, Kris and Mannaert, Herwig} } @booklet {493, title = {Champions of Revealing - The Role of Open Source Developers in Commercial Firms}, year = {2008}, month = {Jan}, abstract = {The link between firms engaging in open source software (OSS) development and the OSS community is established by individual developers. This linkage might entail a principal-agent issue due to the developer{\textquoteright}s double allegiance to firm and OSS community, and expose the firm to the risk of losing intellectual property. Using both interviews and a large-scale survey, I substantiate the importance of the developer{\textquoteright}s role. However, neither interview data nor regression analysis show indications of commercially harmful revealing behavior induced by ""Free Software ideology."" Management, on the other hand, sometimes seems to be overly concerned about openness. I conclude that a more positive stance towards openness will allow firms to better share in the benefits of open innovation processes.}, attachments = {https://flosshub.org/sites/flosshub.org/files/Henkel_Champions_of_revealing_2008-01.pdf}, author = {Joachim Henkel} } @conference {549, title = {Channeling Firefox Developers: Mom and Dad Aren{\textquoteright}t Happy Yet}, 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 = {265 - 271}, publisher = {Springer}, organization = {Springer}, chapter = {22}, abstract = {Firefox, a browser targeted at mainstream users, has been one of the big successes of open source development in recent years. That Firefox succeeded where earlier attempts failed is undoubtedly due to the particular choices that were made in the process of development. In this paper, we look at this process in more detail. Mining bug reports and feature requests related to Firefox in Mozilla{\textquoteright}s Bugzilla bug tracker system, we find that the attention developers devoted to reports and requests was influenced by several factors. Most importantly, other things being equal, reports and requests from outsiders increasingly tend to be ignored. While such behavior may have helped to shield Firefox from the {\textquotedblleft}alpha-geek power user{\textquotedblright} in the early stages of development, it also makes it difficult for {\textquotedblleft}mom and dad{\textquotedblright} to let their voice be heard even after they have adopted Firefox. }, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_22}, attachments = {https://flosshub.org/sites/flosshub.org/files/Channeling\%20Firefox\%20Developers.pdf}, author = {Jean-Michel Dalle and den Besten, Matthijs and Masmoudi, H{\'e}la} } @booklet {517, title = {Claiming Copyleft in Open Source Software: What if the Free Software Foundation{\textquoteright}s General Public License (GPL) had been Patented?}, year = {2008}, month = {Jan}, abstract = {Patent law, by necessity, needs some way to evaluate inventiveness. Otherwise, it will grant rights to advances not worth ""the embarrassment of an exclusive patent."" The innovations of version two of the Free Software Foundation{\textquoteright}s (FSF) GNU General Public License (GPLv2), arriving in 1991, could not, under U.S. patent law at that time, have been meaningfully measured against patent law{\textquoteright}s criteria, often referred to as the five elements of patentability. The first element of patentability, statutory subject matter, would have excluded the GPLv2{\textquoteright}s copyright-based licensing technique as a ""business method."" A variety of industry developments in the decades following GPLv2{\textquoteright}s arrival, combined with the license{\textquoteright}s potent ideological force and clever use of copyright law, propelled FOSS licensing into a prominent and path-breaking place within information technology worldwide. Its force and presence, and lightning-rod character, have grown over time, with GPLv2 remaining the dominant license in mind-share, if not code-share. In addition, all of this occurred without patent protection for GPLv2{\textquoteright}s unique licensing technique. This then raises the counter-factual inquiry for this symposium article: what might have occurred differently if GPLv2{\textquoteright}s licensing method had been patentable? In other words, if the U.S. patent law of statutory subject matter in 1991 was sufficiently permissive, and if the FSF and Richard Stallman successfully patented the novel licensing approaches of GPLv2, would patent protection have altered the FOSS movement{\textquoteright}s two-decade trajectory through information technology and the Internet? If so, can we estimate in what ways? The Article{\textquoteright}s assessment is that GPLv2 could readily meet the other four elements of patentability (with non-obviousness being the closest call compared to prior sublicensing schemes), and that the FOSS trajectory would change minimally, due to a variety of factors, including practical constraints on the enforcement potency of patent claims to GPLv2, competition from other types of FOSS licensing, and strategic considerations for a variety of players and camps within the FOSS movement. However, in the counterfactual, license proliferation diminishes, and dual licensing may be foreclosed.}, attachments = {https://flosshub.org/sites/flosshub.org/files/Vetter.ClaimingCopyleftInOSS-WhatIfGPLPatented.2008Mich.St_.L.Rev_.279.pdf}, author = {Greg R Vetter} } @conference {1206, title = {Collecting data from distributed FOSS projects}, booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)}, year = {2008}, note = {"We selected three projects from the initial set of projects: Linux 2.6, an operating system kernel, gimp, a graphics program, and Blender, a 3d content creation suite." "To acquire data from each data source, we wrote special programs based on the earlier prototypes....The first program extracts information from mailing list archives....The second program obtains bug reports from bug tracking systems....The third program obtains source code from network-accessible version control systems and runs metric calculations on it."}, month = {2009}, pages = {8-13}, abstract = {A key trait of Free and Open Source Software (foss) development is its distributed nature. Nevertheless, two project-level operations, the fork and the merge of program code, are among the least well understood events in the lifespan of a foss project. Some projects have explicitly adopted these operations as the primary means of concurrent development. In this study, we examine the effect of highly distributed software development, as found in the Linux kernel project, on collection and modelling of software development data. We find that distributed development calls for sophisticated temporal modelling techniques where several versions of the source code tree can exist at once. Attention must be turned towards the methods of quality assurance and peer review that projects employ to manage these parallel source trees. Our analysis indicates that two new metrics, fork rate and merge rate, could be useful for determining the role of distributed version control systems in foss projects. The study presents a preliminary data set consisting of version control and mailing list data. }, keywords = {bitkeeper, bug tracking system, cvs, distributed, email archive, fork rate, git, life cycle, linux, linux kernel, mailing list, merge rate, subversion, svn, version control}, attachments = {https://flosshub.org/sites/flosshub.org/files/fagerholm.pdf}, author = {Fagerholm, Fabian and Taina, Juha} } @booklet {511, title = {Competitive Implications of Software Open-Sourcing}, year = {2008}, month = {Aug}, abstract = {This paper is concerned with the economic trade-offs associated with open-sourcing, the business strategy of releasing free open-source versions of commercial software products. The effect of the release of open-source versions on the customers{\textquoteright} perception of products is an important determinant of open-sourcing outcomes. We model open-sourcing as a strategic option for firms that compete in the market for software products. Of particular importance in our model is the effect of open-sourcing on customer values and the possibility for better customization offered by the open-source products. We show that open-sourcing can arise as an equilibrium outcome in our simple two-stage game. If the enhancement of customer values from open-sourcing is moderate or high, firms may find it optimal to release open-source versions of their products.}, url = {http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1185374}, author = {Jai Asundi and Octavian Carare and Kutsal Dogan} } @conference {1209, title = {Computer support for discovering oss processes}, booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)}, year = {2008}, month = {2008}, pages = {31-33}, abstract = {Large scale open source software (OSS) projects offer a wide range of documentation of the software processes that have enabled their success. Discovering these processes has been shown to be difficult to achieve. This paper describes our experiences with providing computer support for discovering OSS processes from project data. We discuss challenges of collecting and analyzing data from multiple types of project artifacts and how to address them. }, keywords = {artifacts, Firefox, process management, zotero}, attachments = {https://flosshub.org/sites/flosshub.org/files/jensen2008.pdf}, author = {Chris Jensen and Walt Scacchi} } @conference {1460670, title = {The confusion of crowds: non-dyadic help interactions}, booktitle = {CSCW {\textquoteright}08: Proceedings of the 2008 ACM conference on Computer supported cooperative work}, year = {2008}, pages = {699{\textendash}702}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Help-giving interactions in open source technical support often involve more people than the conventional help-giver help-seeker pair. Contributions include lightweight but useful me-too contributions from fellow help-seekers. Problems with the reuse of help documentation may be resolved by contextualized discussions, and those discussions themselves are found to be substantially reused. }, keywords = {help-giving, technical help}, isbn = {978-1-60558-007-4}, doi = {http://doi.acm.org/10.1145/1460563.1460670}, author = {Singh, V and Twidale, M.B} } @conference {504, title = {Continuous Integration in Open Source Software Development}, booktitle = {Fourth International Conference on Open Source Software}, year = {2008}, month = {Sept}, abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers.}, attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2008-continuous-integration-final.pdf}, author = {Amit Deshpande and Dirk Riehle} } @conference {550, title = {Continuous Integration in Open Source Software Development}, 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 = {273 - 280}, publisher = {Springer}, organization = {Springer}, chapter = {23}, abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers. }, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_23}, attachments = {https://flosshub.org/sites/flosshub.org/files/Continous\%20Integration.pdf}, author = {Amit Deshpande and Dirk Riehle} } @conference {870, title = {Crafting the initial user experience to achieve community goals}, booktitle = {ACM Conference on recommender Systems}, year = {2008}, publisher = {ACM}, organization = {ACM}, address = {Lausanne, Switzerland}, isbn = {978-1-60558-093-7}, author = {Drenner, S. and Sen, S. and Terveen, L.} } @conference {1207, title = {Cross-repository data linking with RDF and OWL}, booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)}, year = {2008}, note = {non-experimental}, month = {2009}, pages = {15-22}, abstract = {This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree.}, keywords = {data integration, flossmole, forges, integration, owl, RDF, repositories, semantic, semantic Web, sparql, srda}, attachments = {https://flosshub.org/sites/flosshub.org/files/howison2008.pdf}, author = {Howison, James} } @conference {673, title = {Can Knowledge Management be Open Source?}, 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 = {59 - 70}, publisher = {Springer}, organization = {Springer}, chapter = {5}, abstract = {As we move further into a knowledge economy where collaboration and innovation are increasingly central to organisational effectiveness, enterprises need to pay more attention to the informal networks that exist within the organisation. Wikis may provide a more appropriate knowledge management capability and environment to capture tacit knowledge. Where traditional organisational cultures see that knowledge management must be tightly protected, Wikis opt for an open source approach where knowledge is shared and distributed for innovation to continue. This paper aims to explicate more participatory organisational processes of creation, accumulation and maintenance of knowledge. It uses Activity Theory as a framework to describe the components of an activity system where a Wiki is a tool mediating employee-based knowledge management activities and thereby democratising organisational knowledge. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_5}, attachments = {https://flosshub.org/sites/flosshub.org/files/Can\%20Knowledge\%20Management.pdf}, author = {Pfaff, Charmaine and Hasan, Helen} } @conference {629, title = {Community Structure, Individual Participation and the Social Construction of Merit}, 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 = {161 - 172}, publisher = {Springer}, organization = {Springer}, chapter = {13}, abstract = {FLOSS communities are often described as meritocracies. We consider merit as a social construction that structures the community as a whole by allocating prestige to its participants on the basis of what they do. It implies a hierarchy of the different activities (web maintenance, writing code, bug report...) within the project. We present a study based on the merging of two datasets. We analyze the archive of KDE mailing lists using a social network. We also use responses to a questionnaire of KDE participants. Results bring empirical evidences showing that this hierarchy structures the community of KDE by allocating more central position to participants with more prestigious activities. We also show that this hierarchy structures individuals participation by giving greater {\textquotedblleft}membership esteem{\textquotedblright} to members involved in more prestigious activities. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_13}, attachments = {https://flosshub.org/sites/flosshub.org/files/Community\%20Structure\%20Individual.pdf}, author = {Studer, Matthias} } @conference {1005, title = {Comparing Approaches to Mining Source Code for Call-Usage Patterns}, booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)}, year = {2007}, pages = {20 - 20}, publisher = {IEEE}, organization = {IEEE}, address = {Minneapolis, MN, USA}, abstract = {Two approaches for mining function-call usage patterns from source code are compared. The first approach, itemset mining, has recently been applied to this problem. The other approach, sequential-pattern mining, has not been previously applied to this problem. Here, a call-usage pattern is a composition of function calls that occur in a function definition. Both approaches look for frequently occurring patterns that represent standard usage of functions and identify possible errors. Itemset mining produces unordered patterns, i.e., sets of function calls, whereas, sequential-pattern mining produces partially ordered patterns, i.e., sequences of function calls. The trade-off between the additional ordering context given by sequential-pattern mining and the efficiency of itemset mining is investigated. The two approaches are applied to the Linux kernel v2.6.14 and results show that mining ordered patterns is worth the additional cost.}, keywords = {function calls, functions, kernel, linux, sequence, sequencing, sequential-pattern mining}, isbn = {0-7695-2950-X}, doi = {10.1109/MSR.2007.3}, attachments = {https://flosshub.org/sites/flosshub.org/files/28300020.pdf}, author = {Kagdi, Huzefa and Collard, Michael L. and Maletic, Jonathan I.} } @conference {648, title = {Context-Dependent Evaluation Methodology for Open Source Software}, 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 = {301 - 306}, publisher = {Springer}, organization = {Springer}, chapter = {32}, abstract = {Many evaluation methodologies have been proposed to mitigate the risks of choosing Open Source Software as an effective solution to an enterprise{\textquoteright}s problem. This work extracts the shared traits from the most important and widely known evaluation models, and re-applies them to create a new methodology. This methodology has been designed both to be used for the creation of a common knowledge base, and to be specialized for application in the context of the particular breed of small and medium-size enterprises found on the Italian ground. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_32}, attachments = {https://flosshub.org/sites/flosshub.org/files/Context-Dependent\%20Evaluation.pdf}, author = {Cabano, Michele and Monti, Cesare and Piancastelli, Giulio} } @conference {626, title = {Corporate Involvement of Libre Software: Study of Presence in Debian Code over Time}, 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 = {121 - 132}, publisher = {Springer}, organization = {Springer}, chapter = {10}, abstract = {Although much of the research on the libre (free, open source) phenomenon has been focused on the involvement of volunteers, the role of companies is also important in many projects. In fact, during the last years, the involvement of companies in the libre software world seems to be raising. In this paper we present an study that shows, quantitatively, how important this involvement is in the production of the largest collection of code available for Linux: the Debian GNU/Linux distribution. By studying copyright attributions in source code, we have identified those companies with more attributed code, and the trend of corporate presence in Debian from 1998 to 2004. }, issn = {978-0-387-72485-0}, doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_10}, attachments = {https://flosshub.org/sites/flosshub.org/files/Corporate\%20Involvement\%20of\%20Libro.pdf}, author = {Gregorio Robles and Due{\~n}as, Santiago and Gonzalez-Barahona, Jesus} } @conference {996, title = {Correlating Social Interactions to Release History during Software Evolution}, booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)}, year = {2007}, pages = {7 - 7}, publisher = {IEEE}, organization = {IEEE}, address = {Minneapolis, MN, USA}, abstract = {In this paper, we propose a method to reason about the nature of software changes by mining and correlating discussion archives. We employ an information retrieval approach to find correlation between source code change history and history of social interactions surrounding these changes. We apply our correlation method on two software systems, LSEdit and Apache Ant. The results of these exploratory case studies demonstrate the evidence of similarity between the content of free-form text emails among developers and the actual modifications in the code. We identify a set of correlation patterns between discussion and changed code vocabularies and discover that some releases referred to as minor should instead fall under the major category. These patterns can be used to give estimations about the type of a change and time needed to implement it.}, keywords = {ant, apache, change management, developers, discussion, effort estimation, lsedit, mailing lists, scm, source code}, isbn = {0-7695-2950-X}, doi = {10.1109/MSR.2007.4}, attachments = {https://flosshub.org/sites/flosshub.org/files/28300007.pdf}, author = {Baysal, Olga and Malton, Andrew J.} } @article {springerlink:10.1007/s10588-006-9006-3, title = {Correlating temporal communication patterns of the Eclipse open source community with performance and creativity}, journal = {Computational \& Mathematical Organization Theory}, volume = {13}, year = {2007}, note = {"Social network data was collected from the Eclipse component development groups{\textquoteright} online mailing lists by using the online process tool (Gloor and Zhao, 2004). Data on bugs and enhancements for each group was collected from the Eclipse bugzilla database (Eclipse bugzilla, 2004). The social network data was analyzed with the TeCFlow tool (Gloor and Zhao, 2004)." "The study is based on data from the three main projects of the Eclipse open source development community, namely {\textquotedblleft}eclipse{\textquotedblright}, {\textquotedblleft}tools{\textquotedblright} and {\textquotedblleft}technology{\textquotedblright}. We have chosen thirty-three different component development groups for analysis." "The online process tool (online process tool, 2004) was utilized to collect communication data from their mailing list archives. The online process tool runs a robot that searches for URLs in the projects{\textquoteright} mailing list archives to compile a list of the possible URL links. It then extracts communication data as tuples in the form of {\textquotedblleft}sender, receiver, communication type, timestamp, communication contents{\textquotedblright} and stores it in the database. Further, bugs and enhancement data were collected from the Eclipse bugzilla database."}, pages = {17-27}, publisher = {Springer Netherlands}, abstract = {This paper studies the temporal communication patterns of online communities of developers and users of the open source Eclipse Java development environment. It measures the productivity of each community and seeks to identify correlations that exist between group communication characteristics and productivity attributes. The study uses the TeCFlow (Temporal Communication Flow) visualizer to create movie maps of the knowledge flow by analyzing the publicly accessible Eclipse developer mailing lists as an approximation of the social networks of developers and users. Thirty-three different Eclipse communities discussing development and use of components of Eclipse such as the Java Development Tools, the different platform components, the C/C++ Development Tools and the AspectJ extension have been analyzed over a period of six months. The temporal evolution of social network variables such as betweenness centrality, density, contribution index, and degree have been computed and plotted. Productivity of each development group is measured in terms of two indices, namely performance and creativity. Performance of a group is defined as the ratio of new bugs submitted compared with bugs fixed within the same period of time. Creativity is calculated as a function of new features proposed and implemented. Preliminary results indicate that there is a correlation between attributes of social networks such as density and betweenness centrality and group productivity measures in an open source development community. We also find a positive correlation between changes over time in betweenness centrality and creativity, and a negative correlation between changes in betweenness centrality and performance.}, keywords = {bug fixing, bugs, bugzilla, communication, creativity, developers, eclipse, email, email archives, feature requests, mailing lists, performance, productivity}, issn = {1381-298X}, url = {http://dx.doi.org/10.1007/s10588-006-9006-3}, attachments = {https://flosshub.org/sites/flosshub.org/files/16.pdf}, author = {Kidane, Yared and Gloor, Peter} } @conference {882, title = {Creating, Destroying, and Restoring Value in Wikipedia}, booktitle = {Conference on Supporting Group Work}, year = {2007}, author = {Reid Priedhorsky and Jilin Chen and Shyong K. Lam and Katherine Panciera and Loren Terveen and John Riedl} } @article {flosswp371, title = {The Creation of the Entrepreneurial Spirit and the Formation Of Alliances With Africa}, year = {2007}, month = {January}, abstract = {The paper argues that there are internal governance problems within the African polity which need to be resolved before a successful creation of entrepreneurial alliances between Africa and the rest of the world. It also argues that past issues such as colonialism and imperialism pale into insignificance particularly among the new generation if they observe the absence of ethics among the current political leadership in the continent. There is also some discussion about the need for the developed world, notwithstanding the internal continental problems, to brush up its act in relation to the formation of alliances in Africa. Finally the paper argues the formation of alliances with Africa should not be limited to the traditioanl alliance partners of Europe and the America, but be flexible enough to allow new entrants such as China and India.}, attachments = {https://flosshub.org/sites/flosshub.org/files/WITTENBERG.pdf}, author = {Jabulani Mzaliya} } @conference {681, title = {Call for Quality: Open Source Software Quality Observation}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {57 - 62}, publisher = {Springer}, organization = {Springer}, abstract = {This paper describes how a Software Quality Observatory works to evaluate and quantify the quality of an Open Source project. Such a quality measurement can be used by organizations intending to deploy an Open Source solution to pick one of the available projects for use. We offer a case description of how the Software Quality Observatory will be applied to the KDE project to document and evaluate its quality practices for outsiders. }, keywords = {kde, quality}, doi = {http://dx.doi.org/10.1007/0-387-34226-5_6}, attachments = {https://flosshub.org/sites/flosshub.org/files/Call\%20for\%20Quality.pdf}, author = {de Groot, Adriaan and K{\"u}gler, Sebastian and Adams, Paul and Gousios, Giorgos} } @conference {Gurbani:2006:CSC:1134285.1134352, title = {A case study of a corporate open source development model}, booktitle = {Proceedings of the 28th international conference on Software engineering}, series = {ICSE {\textquoteright}06}, year = {2006}, pages = {472{\textendash}481}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Open source practices and tools have proven to be highly effective for overcoming the many problems of geographically distributed software development. We know relatively little, however, about the range of settings in which they work. In particular, can corporations use the open source development model effectively for software projects inside the corporate domain? Or are these tools and practices incompatible with development environments, management practices, and market-driven schedule and feature decisions typical of a commercial software house? We present a case study of open source software development methodology adopted by a significant commercial software project in the telecommunications domain. We extract a number of lessons learned from the experience, and identify open research questions.}, keywords = {architecture, case study, open source, session initiation protocol, software development, vkg}, isbn = {1-59593-375-1}, doi = {10.1145/1134285.1134352}, url = {http://doi.acm.org/10.1145/1134285.1134352}, author = {Gurbani, Vijay K. and Garvert, Anita and Herbsleb, James D.} } @article {891, title = {Challenges of open innovation: the paradox of firm investment in open-source software}, journal = {R\&D Management}, volume = {36}, year = {2006}, month = {06/2006}, pages = {319 - 331}, abstract = {

Open innovation is a powerful framework encompassing the generation, capture, and employment of intellectual property at the firm level. We identify three fundamental challenges for firms in applying the concept of open innovation: finding creative ways to exploit internal innovation, incorporating external innovation into internal development, and motivating outsiders to supply an ongoing stream of external innovations. This latter challenge involves a paradox, why would firms spend money on R\&D efforts if the results of these efforts are available to rival firms? To explore these challenges, we examine the activity of firms in open-source software to support their innovation strategies. Firms involved in open-source software often make investments that will be shared with real and potential rivals. We identify four strategies firms employ

}, author = {Joel West and Gallagher, Scott} } @conference {Beyer:2006:CVA:1137983.1138023, title = {Co-change visualization applied to PostgreSQL and ArgoUML: (MSR challenge report)}, booktitle = {Proceedings of the 2006 international workshop on Mining software repositories}, series = {MSR {\textquoteright}06}, year = {2006}, pages = {165{\textendash}166}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Co-change visualization is a method to recover the subsystem structure of a software system from the version history, based on common changes and visual clustering. This paper presents the results of applying the tool CCVisu which implements co-change visualization, to the two open-source software systems PostgreSQL and ArgoUML The input of the method is the co-change graph, which can be easily extracted by CCVisu from a Cvs version repository. The output is a graph layout that places software artifacts that were often commonly changed at close positions, and artifacts that were rarely co-changed at distant positions. This property of the layout is due to the clustering property of the underlying energy model,which evaluates the quality of a produced layout. The layout can be displayed on the screen, or saved to a file in SVG or VRML format.}, keywords = {argouml, ccvisu, cvs, force-directed graph layout, graph, mining challenge, msr challenge, postgresql, software clustering, software structure analysis, software visualization, version control, visualization}, isbn = {1-59593-397-2}, doi = {http://doi.acm.org/10.1145/1137983.1138023}, url = {http://doi.acm.org/10.1145/1137983.1138023}, attachments = {https://flosshub.org/sites/flosshub.org/files/165Co-Change.pdf}, author = {Beyer, Dirk} } @conference {682, title = {Collaborative Maintenance in Large Open-Source Projects}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {233 - 244}, publisher = {Springer}, organization = {Springer}, abstract = {The paper investigates collaborative work among maintainers of open source software by analyzing the logs of a set of 10 large projects. We inquire whether teamwork can be influenced by several characteristics of code. Preliminary results suggest that collaboration among maintainers in most large open-source projects seems to be positively influenced by file vintage and by Halstead volume of files, and negatively by McCabe complexity and size measured in SLOCs. These results could be consistent with an increased attractivity of files created early in the history of a project, and with maintainers being less attracted by more verbose code and by more complex code, although in this last case it might also reflect the fact that more complex files would be de facto more exclusive in terms of maintenance. }, keywords = {apache, COLLABORATION, complexity, cvs, gaim, gcc, ghostscript, halstead, lines of code, loc, mccabe, mozilla, netbsd, openssh, postgresql, python, sloc}, doi = {http://dx.doi.org/10.1007/0-387-34226-5_23}, attachments = {https://flosshub.org/sites/flosshub.org/files/Collaborative\%20Maintenance.pdf}, author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice} } @unpublished {flosswp336, title = {Commons Identity: A Conceptual Model for Designing Brand Identity in Free and Open Source Software Projects}, year = {2006}, month = {September}, abstract = {Purpose: Open Source is a popular term to describe a development and production method based on the free sharing of information. The computer software industry has embraced Open Source practices increasingly since the nineties. Participation in Free and Open Source Software projects is commonly voluntary and there is a need for specialized knowledge surrounding the production of software. This report focuses on the topic area of designing brand identity. Objective: To create a conceptual model for designing brand identity in Free and Open Source Software projects based on Wheeler???s Brand Identity Process of 2006. Design: Participatory action research with three cycles and five interviews conducted online. Participants: Three Free and Open Source Software projects named Sociopath, OpenEats, and Jajuk. Five industry professionals with expertise in branding and Open Source development. Results: Wheeler???s brand identity process is modified towards the Open Source method and incorporates community votes and commons-based peer-review. Outcomes specific to Free and Open Source Software projects are included as exemplary brand identity assets. Furthermore, a preparation phase is added showing the entry into the project???s community. Conclusions: The created model is a practical tool for designing brand identity in Free and Open Source Software projects. Further applications of the model are needed for its evaluation.}, attachments = {https://flosshub.org/sites/flosshub.org/files/commons_identity.pdf}, author = {Nicolas Schudel} } @conference {683, title = {Communication Networks in an Open Source Software Project}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing }, volume = {203/2006}, year = {2006}, month = {2006///}, pages = {297 - 306}, publisher = {Springer}, organization = {Springer}, abstract = {This study explores the nature of the social network and the patterns of communication that exist in an open source software development project, the Apache HTTP (WEB) server project. Our analysis of archival data on email communications between developers in the Apache HTTP server project suggests an interesting pattern of communication. We find that the core developers self-organize into three sub-groups that communicate intensely in completing the project. Our analysis also reveals that a few prominent developers who are centrally located in the network are driving communications within the project. We identify the implications of our findings and suggest areas for further research. }, keywords = {apache, core, developers, email, email archive, mailing list, participation, social network analysis}, issn = {978-0-387-34225-2}, doi = {http://dx.doi.org/10.1007/0-387-34226-5_30}, attachments = {https://flosshub.org/sites/flosshub.org/files/Communication\%20Networks\%20in\%20an\%20Open\%20Source.pdf}, author = {Roberts, Jeffrey and Il-Horn Hann and Sandra Slaughter} } @conference {684, title = {Comparing macro development for personal productivity tools: an experience in validating accessibility of Talking Books}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {247 - 252}, publisher = {Springer}, organization = {Springer}, abstract = {We describe an experience in developing macros for both Power Point and Impress, to be used in accessibility validation for educational multimedia (Talking Books) designed for visually impaired people. Minor disadvantages in the use of Impress are outlined, which however do not constitute a serious obstacle to adoption of Open Source tools for our purposes. }, doi = {http://dx.doi.org/10.1007/0-387-34226-5_24}, attachments = {https://flosshub.org/sites/flosshub.org/files/Comparing\%20macro\%20development.pdf}, author = {Dodero, Gabriella and Lupi, Katia and Piffero, Erika} } @conference {Herraiz:2006:CSN:1116163.1116405, title = {Comparison Between SLOCs and Number of Files As Size Metrics for Software Evolution Analysis}, booktitle = {Proceedings of the Conference on Software Maintenance and Reengineering}, series = {CSMR {\textquoteright}06}, year = {2006}, pages = {206{\textendash}213}, publisher = {IEEE Computer Society}, organization = {IEEE Computer Society}, address = {Washington, DC, USA}, keywords = {empirical studies, libre software, metrics, software evolution}, isbn = {0-7695-2536-9}, url = {http://dl.acm.org/citation.cfm?id=1116163.1116405}, author = {Herraiz, Israel and Gregorio Robles and Gonzalez-Barahon, Jes us M.} } @conference {685, title = {Conceptual Modelling as a New Entry in the Bazaar: The Open Model Approach}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {9 - 20}, publisher = {Springer}, organization = {Springer}, abstract = {The present contribution proposes to transfer the main principles of open source software development to a new context: conceptual modelling; an activity closely related to software development. The goal of the proposed {\textquotedblleft}open model{\textquotedblright} approach is to collaboratively develop reference models for everyone to copy, use and refine in a public process. We briefly introduce conceptual modelling and reference models, discuss the cornerstones of an open modelling process, and propose a procedure for initiating, growing and sustaining an open model project. The paper concludes with a discussion of potential benefits and pitfalls. }, doi = {http://dx.doi.org/10.1007/0-387-34226-5_2}, attachments = {https://flosshub.org/sites/flosshub.org/files/Conceptual\%20Modelling\%20as\%20a\%20New\%20Entry.pdf}, author = {Koch, Stefan and Strecker, Stefan and Frank, Ulrich} } @conference {686, title = {Contributor Turnover in Libre Software Projects}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {273 - 286}, publisher = {Springer}, organization = {Springer}, abstract = {A common problem that management faces in software companies is the high instability of their staff. In libre (free, open source) software projects, the permanence of developers is also an open issue, with the potential of causing problems amplified by the self-organizing nature that most of them exhibit. Hence, human resources in libre software projects are even more difficult to manage: developers are in most cases not bound by a contract and, in addition, there is not a real management structure concerned about this problem. This raises some interesting questions with respect to the composition of development teams in libre software projects, and how they evolve over time. There are projects lead by their original founders (some sort of {\textquotedblleft}code gods{\textquotedblright}), while others are driven by several different developer groups over time (i.e. the project {\textquotedblleft}regenerates{\textquotedblright} itself). In this paper, we propose a quantitative methodology, based on the analysis of the activity in the source code management repositories, to study how these processes (developers leaving, developers joining) affect libre software projects. The basis of it is the analysis of the composition of the core group, the group of developers most active in a project, for several time lapses. We will apply this methodology to several large, well-known libre software projects, and show how it can be used to characterize them. In addition, we will discuss the lessons that can be learned, and the validity of our proposal. }, keywords = {apache, committers, core, cvs, cvsanaly, developers, evolution, freebsd, gimp, gnome, kde, mono, mozilla}, doi = {http://dx.doi.org/10.1007/0-387-34226-5_28}, attachments = {https://flosshub.org/sites/flosshub.org/files/Contributor\%20Turnover\%20in\%20Libre\%20Software\%20Projects.pdf}, author = {Gregorio Robles and Gonzalez-Barahona, Jesus} } @article {90, title = {Core and periphery in Free/Libre and Open Source software team communications}, journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06}, year = {2006}, abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.}, keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team}, author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James} } @conference {687, title = {Critical Success Factors for Migrating to OSS-on-the-Desktop: Common Themes across Three South African Case Studies}, booktitle = {OSS2006: Open Source Systems (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, year = {2006}, pages = {287 - 293}, publisher = {Springer}, organization = {Springer}, abstract = {This paper investigates the critical success factors associated with the migration from proprietary desktop software to an open source software (OSS) desktop environment in a South African context. A comparative case study analysis approach was adopted whereby three organisations that have migrated to desktop OSS were analysed. For diversity, one case study each was drawn from government, private industry and the educational sector. Most of the findings agree with those in the available literature though there are notable differences in the relative importance of certain factors. }, doi = {http://dx.doi.org/10.1007/0-387-34226-5_29}, attachments = {https://flosshub.org/sites/flosshub.org/files/Critical\%20Success\%20Factors\%20for\%20Migrating.pdf}, author = {Brink, Daniel and Roos, Llewelyn and Weller, James and Van Belle, Jean-Paul} } @conference {752, title = {The calm before the storm? Legal challenges to open source licences}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {215-219}, abstract = {This paper will concentrate on presenting a legal analysis of two of the main challenges to open source software: SCO{\textquoteright}s litigation and software patents. The paper discusses the validity of such challenges, their possible impact to the future of open source software, and the possible legal defences used against them.}, author = {Gonzalez, Andres Guadamuz} } @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} } @conference {795, title = {The challenges of creating open source education software: the Gild experience}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {338-340}, keywords = {COMMUNITY, eclipse, learning environment, novice programmers, open source, programming environment}, url = {http://pascal.case.unibz.it/handle/2038/1539}, author = {Daniel M. German and Rigby, Peter and Cubranic, Davor and Storey, Margaret-Anne and Thomson, Suzanne} } @conference {722, title = {A Cluster Analysis of Open Source Licenses}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {50-53}, abstract = {Licenses of open source software (OSS) are quiet various but is said to be categorised into three. That is GPL (GNU general Public License) like, LGPL (GNU Lesser general Public License) like, or MPL (Mozilla Public License) like. We check this classification by using our new framework and cluster analysis. And we find another three categories for OSS Licenses.}, url = {http://pascal.case.unibz.it/handle/2038/618} } @conference {78, title = {Collaboration Using OSSmole: A repository of FLOSS data and analyses}, booktitle = {Symposium on Mining Software Repositories}, year = {2005}, month = {17 May}, address = {St. Louis}, author = {Conklin, Megan and James Howison and Kevin Crowston} } @conference {729, title = {Communication, coordination and control in distributed development: an OSS case study}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {88-92}, abstract = {It has been claimed that distributed development practices in OSS development may be a model for enterprise development practices of the future. With this in mind, we have conducted a study of one OSS project, namely ArgoUML, with a view to understanding development practice within the project, and specifically to considering possible differences from traditional (non-OSS) distributed development conducted in a commercial project. We do this by explicitly considering issues of communication, coordination and control. Our findings suggest that primary differences lie in control and resulting project structures, motivated through differing goals. We comment on the open question of how the advantages of one development context can be realised in the other.}, url = {http://pascal.case.unibz.it/handle/2038/769}, author = {Persson, Anna and Lings, Brian and Lundell, Bj{\"o}rn and Mattsson, Anders and {\"A}rlig, Ulf} } @conference {743, title = {Communication from scratch: towards accessible open source information systems}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {179-186}, abstract = {This paper is intended to provide an overview of a unifying and inclusive approach to open source information systems. In this respect the paper matches the fundamental aims of the Open Source Systems (2005) Conference. This approach can be characterised as communication from scratch. Firstly, we will provide an explanation of our approach to inclusive design and consider emerging perspectives on the nature of accessibility in the wider sense. Secondly, we will introduce the concept of communication from scratch and provide an explanation of the benefits of a convergent gradualism. Thirdly we will explain how these ideas have helped to shape our understanding of open source information processing, a concept which encompasses several of the conference themes and provides a unifying interface to our earlier work on accessible system design. Lastly, we will provide some concrete examples of the communication from scratch approach (crossing several domains) and introduce, ...}, url = {http://pascal.case.unibz.it/handle/2038/759}, author = {Crombie, David and Lenoir, Roger and McKenzie, Neil} } @article {10.1109/TSE.2005.89, title = {Comparing High-Change Modules and Modules with the Highest Measurement Values in Two Large-Scale Open-Source Products}, journal = {IEEE Transactions on Software Engineering}, volume = {31}, year = {2005}, pages = {625-642}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, abstract = {Identifying change-prone modules can enable software developers to take focused preventive actions that can reduce maintenance costs and improve quality. Some researchers observed a correlation between change proneness and structural measures, such as size, coupling, cohesion, and inheritance measures. However, the modules with the highest measurement values were not found to be the most troublesome modules by some of our colleagues in industry, which was confirmed by our previous study of six large-scale industrial products. To obtain additional evidence, we identified and compared high-change modules and modules with the highest measurement values in two large-scale open-source products, Mozilla and OpenOffice, and we characterized the relationship between them. Contrary to common intuition, we found through formal hypothesis testing that the top modules in change-count rankings and the modules with the highest measurement values were different. In addition, we observed that high-change modules had fairly high places in measurement rankings, but not the highest places. The accumulated findings from these two open-source products, together with our previous similar findings for six closed-source products, should provide practitioners with additional guidance in identifying the change-prone modules.}, keywords = {mozilla, openoffice}, issn = {0098-5589}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2005.89}, author = {G{\"u}nes Koru, A. and Tian, Jeff (Jianhui)} } @conference {746, title = {Competition between Open Source and Proprietary Software, and the Scope for Public Policy}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {196-199}, abstract = {Open source software (OSS) has become a remarkable competitor of traditional, proprietary software in many markets. This has led advocates of OSS to demand public policy interventions in favor of OSS. The main argument is that OSS mitigates market failures associated with typical features of software markets: economies of scale, direct network effects, switching costs, and systems competition. We study the impact of several policy instruments on social welfare in a duopoly model which incorporates all of the aforementioned features of software markets. Overall, we do not find much support for interventions in favor of OSS. However, systems competition may lead to a situation in which the subsidization of OSS complements increases welfare.}, url = {http://pascal.case.unibz.it/handle/2038/758}, author = {Gutsche, Joerg} } @inbook {900, title = {A Conceptual Model for Enterprise Adoption of Open Source Software}, booktitle = {The Standards Edge: Open Season}, year = {2005}, pages = {51-62}, publisher = {Sheridan Books}, organization = {Sheridan Books}, address = {Ann Arbor, Mich.}, author = {Kwan, Stephen K. and Joel West}, editor = {Bolin, Sherrie} } @proceedings {89, title = {Coordination of Free/Libre Open Source Software development}, year = {2005}, note = {"The data used for the study were interactions on the main developer communication venue, either a developer mailing list or online forum" sourceforge }, address = {Las Vegas, NV, USA}, abstract = {The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, we use coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. We examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. We found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, we found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, we found that {\textquotedblleft}self-assignment{\textquotedblright} was the most common mechanism across three FLOSS projects. This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.}, keywords = {case study, compiere, coordination, egroupware, email, email archives, FLOSS, gaim, mailing list}, attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonWeiLiEseryelHowison.pdf}, author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and Howison, James} } @article {flosswp215, title = {Coordination Processes in Open Source Software Development: The Linux Case Study}, year = {2005}, month = {April}, abstract = {Although open source projects have been subject to extensive study, their coordination processes are still poorly understood. Drawing on organization theory, this paper sets out to remedy this imbalance by showing that large-scale open source projects exhibit three main coordination mechanisms, namely standardization, loose coupling and partisan mutual adjustment. Implications in terms of electronically-mediated communications and networked interdependencies are discussed in the final sections where a new light is cast on the concept of structuring as a by-product of localized adjustments.}, attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci3.pdf}, author = {Federico Iannaci} } @conference {761, title = {Criteria for the non invasive transition to OpenOffice}, booktitle = {OSS2005: Open Source Systems }, year = {2005}, pages = {250-253}, abstract = {Open Source Software (OSS) is receiving an increasing attention as a possible alternative to proprietary solutions. There are supporters of both the alternatives that stress advantages and disadvantages, but what is missing is an empirical view of a transition with the aid of case studies and controlled experiments. The aim of the paper is to report the results of an empirical investigation in the field of office automation in the Public Administration (PA). The available OSS in the field is introduced in the existing environment while preserving the proprietary solution. The analysis is supported by both qualitative and quantitative data. The effects on productivity and on users{\textquoteright} attitude towards OSS and the emerging criteria for a possible transition are exposed.}, url = {http://pascal.case.unibz.it/handle/2038/789}, author = {Rossi, Bruno and Scotto, Marco and Sillitti, Alberto and Succi, Giancarlo} } @proceedings {905, title = {Collaboration, Leadership, Control, and Conflict Negotiation in the NetBeans.org Community}, year = {2004}, month = {May 25}, address = {Edinburgh, Scotland, UK}, keywords = {netbeans}, attachments = {https://flosshub.org/sites/flosshub.org/files/jensen.pdf}, author = {Chris Jensen and Walt Scacchi} } @proceedings {1191, title = {Collaboration, Leadership, Control, and Conflict Negotiation in the Netbeans.org Community}, year = {2004}, pages = {48-52}, abstract = {Large open source software development communities are quickly learning that, to be successful, they must integrate efforts not only among the organizations investing developers within the community and unaffiliated volunteer contributors, but also negotiate relationships with external groups hoping to sway the social and technical direction of the community and its products. Leadership and control sharing across organizations and individuals in and between communities are common sources of conflict. Such conflict often leads to breakdowns in collaboration. This paper seeks to explore the negotiation of these conflicts, collaborative efforts, and leadership and control structures in the Netbeans.org community.}, keywords = {conflict, leadership, netbeans}, attachments = {https://flosshub.org/sites/flosshub.org/files/jensen_0.pdf}, author = {Chris Jensen and Walt Scacchi} } @article {flosswp221, title = {The Collaborative Integrity of Open-Source Software}, year = {2004}, month = {August}, abstract = {This Article analyzes legal protection for open-source software by comparing it to the venerable civil law tradition of moral rights. The comparison focuses on the moral right of integrity, with which one may object to mutilations of her work, even after having parted with the copyright and the object that embodies the work. The parallel apparatus in open-source licensing is conditional permission to use a copyrighted work. The conditions include that source code be available and that software use be royalty-free. These conditions facilitate open-source collaborative software development. At the heart of both systems is the right for creators to control the view that a work presents. In the open-source system, this is the Collaborative Integrity of open-source software. The history and legacy of moral rights help us better understand Collaborative Integrity in open-source software. The right of integrity in some international jurisdictions may apply to software, thus raising questions whether it hurts or helps open-source software. Building from these insights, this Article evaluates whether the Collaborative Integrity in open-source software deserves protection as a separate right, just as the right of integrity developed separately from pecuniary copyright in civil law jurisdictions.}, attachments = {https://flosshub.org/sites/flosshub.org/files/vetter1.pdf}, author = {Greg R Vetter} } @proceedings {1188, title = {Communication and Conflict Issues in Collaborative Software Research Projects}, year = {2004}, pages = {14-17}, abstract = {The Open Source Component Artefact Repository (OSCAR) was developed under the auspices of the GENESIS project to store data produced during the software development process. Significant problems were encountered during the course of the project in both the development itself and management of the project. The reasons for and potential solutions to these problems are examined with the intention of developing a set of guidelines to enable participants in other collaborative projects to avoid these pitfalls. We wish to make it clear that we attach no opprobrium to any of the participants in the GENESIS project as many of the issues we outline below have solutions only visible with hindsight. Instead, we seek to provide a fair-minded critique of our role and the mistakes we made in a fairly typical two-year EU research project, and to provide a set of recommendations for other similar projects, in order that they can (attempt to) avoid suffering similarly.}, keywords = {artefact, cvs, genesis, oscar}, attachments = {https://flosshub.org/sites/flosshub.org/files/boldyreff15-18.pdf}, author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen} } @article {flosswp174, title = {Community structure of modules in the Apache project}, year = {2004}, month = {June}, abstract = {The relationships among modules in a software project of a certain size can give us much information about its internal organization and a way to control and monitor development activities and evolution of large libre software projects. In this paper, we show how information available in CVS repositories can be used to study the structure of the modules in a project when they are related by the people working in them, and how techniques taken from the social networks fields can be used to highlight the characteristics of that structure. As a case example, we also show some results of applying this methodology to the Apache project in several points in time. Among other facts, it is shown how the project evolves and is self-structuring, with developer communities of modules corresponding to semantically related families of modules.}, attachments = {https://flosshub.org/sites/flosshub.org/files/barahona-apache_structure.pdf}, author = {Jesus M. Gonzalez-Barahona} } @proceedings {1190, title = {Community structure of modules in the Apache project}, year = {2004}, pages = {44-48}, abstract = {The relationships among modules in a software project of a certain size can give us much information about its internal organization and a way to control and monitor development activities and evolution of large libre software projects. In this paper, we show how information available in CVS repositories can be used to study the structure of the modules in a project when they are related by the people working in them, and how techniques taken from the social networks fields can be used to highlight the characteristics of that structure. As a case example, we also show some results of applying this methodology to the Apache project in several points in time. Among other facts, it is shown how the project evolves and is self-structuring, with developer communities of modules corresponding to semantically related families of modules.}, keywords = {apache, cvs, source code}, attachments = {https://flosshub.org/sites/flosshub.org/files/gonzalezBarahona44-48.pdf}, author = {Jesus M. Gonzalez-Barahona and Luis Lopez and Gregorio Robles} } @article {flosswp146, title = {A Comparative Study of Online User Communities Involvement In Product Innovation and Development}, year = {2004}, month = {February}, abstract = {The literature lacks a conceptual understanding on how different types of online user communities can influence the product innovation and development. Therefore, this research attempts to understand this phenomenon by re-classifying the current online user communities from the perspective of product innovation and development and has resulted in five different models of user communities. We compare and discuss of the five models. Lastly, we will further discuss the deficiencies of the User Collaboration Innovation Communities, theoretically and practically, to suggest the feasibility of the research direction in the future.}, attachments = {https://flosshub.org/sites/flosshub.org/files/chanlee.pdf}, author = {Tzu-Ying Chan} } @proceedings {1198, title = {A Conflict Detected Earlier is a Conflict Resolved Easier}, year = {2004}, pages = {82-86}, abstract = {Open Source development is highly distributed and parallel in nature. There are no definite boundaries, either for people or from where they work. This high level of parallel, distributed development leads to conflicting changes made concurrently by different developers. Be- cause OSS developers lack the kinds of informal coordination opportunities that collocation offers, OSS developers must rely on mailing lists, discussion groups, and tools such as CM and bug tracking systems to try to man- age their parallel efforts such that conflicts do not occur. Unfortunately, these coordination mechanisms are not adequate: it still regularly happens that parallel changes interfere, either via direct overlap or indirect, semantic conflicts. In this paper, we build upon our previous work in raising awareness as a mechanism to support better coordination among developers, and introduce a new integration of our Palantír tool with Eclipse as well as a new visualization of parallel work that we believe is especially useful in Open Source settings.}, attachments = {https://flosshub.org/sites/flosshub.org/files/sarma83-87.pdf}, author = {Sarma, A. and van der Hoek, A.} } @article {flosswp195, title = {The contestation of code: A preliminary investigation into the discourse of the free/libre and open source movements}, year = {2004}, month = {April}, abstract = {This paper uses discourse analysis to examine the free/libre and open source movements. It analyses how they fix elements within the order of discourse of computer code production. It attempts to uncover the key signifiers in their discourses and trace linkages between the sedimented discourses of wider society. Using discourse theory and critical discourse analysis, the theoretical foundations underpinning each of the movements are critically examined and the effect on the wider developer and Internet community is discussed. Additionally, this paper seeks to recommend discursive strategies that could be employed to avoid the threat of colonization by neoliberal discourse and the consequent challenge this has for the ideas of freedom, liberty and community within the developer communities? own discourses.}, attachments = {https://flosshub.org/sites/flosshub.org/files/berry1.pdf}, author = {David M. Berry} } @article {flosswp166, title = {Contrasting Community Building in Sponsored and Community Founded Open Source Projects}, year = {2004}, month = {September}, abstract = {Prior characterizations of open source projects have been based on the model of a community-founded project. More recently, a second model has emerged, where organizations spinout internally developed code to a public forum. Based on field work on open source projects, we compare the lifecycle differences between these two models. We identify problems unique to spinout projects, particularly in attracting and building an external community. We illustrate these issues with a feasibility analysis of a proposed open source project based on VistA, the primary healthcare information system of the U.S. Department of Veterans Affairs. This example illuminates the complexities of building a community after a code base has been developed and suggests that open source software can be used to transfer technology to the private sector.}, attachments = {https://flosshub.org/sites/flosshub.org/files/westomahony.pdf}, author = {Joel West} } @proceedings {1185, title = {Contributing to OS Projects. A Comparison between Individual and Firms}, year = {2004}, note = {"Following the approach used in previous surveys on Open Source developers, we prepared an on-line questionnaire;"}, pages = {18-22}, abstract = {This paper studies the contributions software firms make to Open Source (OS) projects. Our goal is to ascertain whether they follow the same regularity of pattern seen for individual programmer An exhaustive empirical analysis was carried out using data on project membership1 , project coordination and the contributions made by 146 Italian firms that do business with OS software. We compare our findings with the results of the surveys taken on OS programmers. The availability of the data gathered by Hertel et al. ([10]) on 141 developers of the Linux kernel allowed a direct comparison to be carried out between the two sets2 .}, keywords = {Survey}, attachments = {https://flosshub.org/sites/flosshub.org/files/19-23.pdf}, author = {Andrea Bonaccorsi and Cristina Rossi} } @proceedings {1202, title = {Control Objectives in Open Source Projects}, year = {2004}, pages = {100-104}, abstract = {Many studies on Open Source Software Development (OSSD) have been published in the past years. In these studies, OSSD has received positive comments and is proposed as a new way of developing software. We investigate how project management is used in Open Source Software (OSS) projects to exercise control of development activities. Project management in OSSD is worth studying, because research has shown that project management is a critical success factor in traditional software development. We use the COBIT framework to audit project management practices commonly found in OSS projects with the aim of determining which practices are currently missing or can be further improved upon. The framework identifies several potential threats to the long term continuity of OSS projects.}, keywords = {cobit, project management}, attachments = {https://flosshub.org/sites/flosshub.org/files/ven101-105.pdf}, author = {Ven, Kris and Verelst, Jan} } @conference {Crowston:2004, title = {Coordination practices for bug fixing within FLOSS development teams}, booktitle = {1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems}, year = {2004}, note = {"First, we chose projects for which data we need for our analysis are publicly available (not all projects allow public access to the bug tracking system). Second, we chose teams with more than 8 members...we tried to select more and less suc- cessful development teams. To this aim we used the definitions of success proposed by [9], who suggest that a project is successful if it is active, the resulting software is downloaded and used and the code matures" "Kicq, Gaim and PhPmyAdmin were chosen" - effective DynAPI was chosen as an example of a less effective project" "We collected data indicative of the success of each project, such as its level of activity, number of downloads and development status. We then collected data from the archives of the bug tracking system, the tool used to support the bug fixing process"}, address = {Porto, Portugal}, abstract = {Free/Libre Open Source Software (FLOSS) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards. FLOSS development teams some how profit from the advantages and evade the challenges of distributed software development. Despite the relevance of the FLOSS both for research and practice, few studies have investigated the work practices adopted by these development teams. In this paper we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.}, keywords = {activity, bug fixing, bug reports, bug tracker, coordination, downloads, dynapi, FLOSS, gaim, kicq, phpmyadmin, status}, attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi04coordination.pdf}, author = {Kevin Crowston and Barbara Scozzi} } @article {flosswp203, title = {The critical delusion of the condition of digitisation}, year = {2004}, month = {December}, abstract = {This essay analyses how digital media prosthetics, institutionalisation (in particular the manifestations of copyright and patent law which lurk behind vested interests in controlling the transition to a vastly more powerful new world), and the imperatives of corporate planning have come into a conflict so fierce that shared lived experience, increasingly, is forced to undergo a rapid process of commodification. This struggle, which can no longer be defined through the lens of geography or class alone, in turn, points to a not too distant future in which commons-based peer production/consumption is exploited within the context of intense social taylorism and digital fordism with the ultimate goal to turn culture into a paid-for experience, and hence moving the terrain of struggle away from the surplus value of labour to the legitimacy of knowledge sharing and pervasive networking, and how the latter can be monetised and controlled in accordance with anarcho-capitalist agendas. Obviously, the question which we ought to pose to ourselves is how the revolutionary demands of hacking can be guided, assembled, and reproduced, so that this process of commodification is consciously resisted by technology developers and users alike, artists, and all those whose creativity and desire for socially conscious technological innovation and emergent social co-operation have been enhanced by the digital condition we{\textquoteright}re increasingly in the centre of.}, attachments = {https://flosshub.org/sites/flosshub.org/files/dafermos_ccc.pdf}, author = {George Dafermos} } @article {flosswp132, title = {Capability Coordination in Modular Organization: Voluntary FS/OSS Production and the Case of Debian GNU/Linux}, year = {2003}, month = {November}, abstract = {The paper analyzes voluntary Free Software/Open Source Software (FS/OSS) organization of work. The empirical setting considered is the Debian GNU/Linux operating system. The paper finds that the production process is hierarchical notwithstanding the modular (nearly decomposable) architecture of software and of voluntary FS/OSS organization. But voluntary FS/OSS project organization is not hierarchical for the same reasons suggested by the most familiar theories of economic organization: hierarchy is justified for coordination of continuous change, rather than for the direction of static production. Hierarchy is ultimately the overhead attached to the benefits engendered by modular organization.}, attachments = {https://flosshub.org/sites/flosshub.org/files/garzarelligaloppini.pdf}, author = {Giampaolo Garzarelli} } @inbook {flosswp89, title = {Chapter 1- Networks of Innovation: Change and Meaning in the Age of the Internet (Oxford University Press)}, year = {2003}, month = {June}, abstract = {Integrating concepts from multiple theoretical disciplines and detailed analyses of the evolution of Internet-related innovations (including computer networking, the World Wide Web and the Linux open source operating system), this book develops foundations for a new theoretical and practical understanding of innovation. It includes a detailed analysis of the Linux open source development model." The table of contents, references, and other related material is available here}, attachments = {https://flosshub.org/sites/flosshub.org/files/tuomi2.pdf}, author = {Ilkka Tuomi} } @conference {DBLP:conf/csmr/CapiluppiLM03, title = {Characteristics of Open Source Projects}, booktitle = {7th European Conference on Software Maintenance and Reengineering (CSMR{\textquoteright}03)}, year = {2003}, note = {"We analyze a sample of around 400 projects from a popular OS project repository. " no pdf to confirm what projects these are or what the repository is.[ms]}, pages = {317-}, abstract = {Most empirical studies about Open Source (OS)projects or products are vertical and usually deal with the flagship, successful projects. There is a substantial lack of horizontal studies to shed light on the whole population of projects, including failures. This paper presents a horizontal study aimed at characterizing OS projects. We analyze a sample of around 400 projects from a popular OS project repository. Each project is characterized by a number of attributes. We analyze these attributes statically and over time. The main results show that few projects are capable of attracting a meaningful community of developers. The majority of projects is made by few (in many cases one) person with a very slow pace of evolution.}, keywords = {evolution, project success, repository}, author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio} } @article {flosswp84, title = {Clustering and Dependencies in Free/Open Source Software Development: Methodology and Tools}, year = {2003}, note = {source code is the artifact used}, month = {April}, abstract = {This paper addresses the problem of measurement of non-monetary economic activity, specifically in the area of free/open source software communities. It describes the problems associated with research on these communities in the absence of measurable monetary transactions, and suggests possible alternatives. A class of techniques using software source code as factual documentation of economic activity is described and a methodology for the extraction, interpretation and analysis of empirical data from software source code is detailed, with the outline of algorithms for identifying collaborative authorship and determining the identity of coherent economic actors in developer communities. Finally, conclusions are drawn from the application of these techniques to a base of software.}, keywords = {scm, source code, source code analysis}, url = {http://dxm.org/papers/toulouse2/cluster-final.pdf}, attachments = {https://flosshub.org/sites/flosshub.org/files/cluster-final.pdf}, author = {Rishab Ayer Ghosh} } @article {flosswp109, title = {Code, Coding and Coded Perspectives}, year = {2003}, month = {January}, abstract = {Building on computer science I consider code (as opposed to the Web, an instantiation of code) as a new technology of communication. Using the historical and sociological analyses of others, which have examined the results of print on perspectives and society, I offer four scenarios for the results of code. The four scenarios focus on the results of code on quantitative thought: the divergence of scientific perspective with popular reasoning resulting in reduced innovation; a broad-based popular explosion in innovation expanding the basis of reasoning; cypto-anarchy with those empowered by science corrupted with the power; and a loss of certainty of information with a return to tribalism. The last suggests a new era of ignorance, a moment in modern Dark Ages {\textendash} in that an excess of the light of information causes blindness as effectively as its absence. The openness of code is a determinant in the resulting social structure.}, attachments = {https://flosshub.org/sites/flosshub.org/files/aoir.html}, author = {L. Jean Camp} } @article {flosswp127, title = {Collective Action and Communal Resources in Open Source Software Development:The Case of Freenet}, year = {2003}, month = {November}, abstract = {Building on resource mobilization theory, we explore three distinct rewards for individuals to engage in innovative collective action, namely open source software development. The three rewards, which we term communal resources, are reputation, control over technology, and learning opportunities. The collective action (the open source software development project) produces the communal resources in parallel with the actual product (software) and mobilizes programmers to spend time and effort, and contribute their knowledge to the project. Communal resources appear as a byproduct to the production process and represent a public good of second order. We show that they increase in value for individuals along with their involvement in the community. Empirical data from Freenet, an open source software project for peer-to-peer software, illustrates both the levels of involvement and the communal resources.}, attachments = {https://flosshub.org/sites/flosshub.org/files/vonkroghhaefligerspaeth.pdf}, author = {Georg von Krogh} } @article {146, title = {Community, joining, and specialization in open source software innovation: a case study}, journal = {Research Policy}, volume = {32}, number = {7}, year = {2003}, note = {first, telephone interviews "Secondly, we collected the project{\textquoteright}s public email conversations stored in the projects{\textquoteright} mailing lists which is archived on Freenet{\textquoteright}s website" "The third source of data included the history of changes to the software code available via the project{\textquoteright}s software repository within the CVS ({\textquoteleft}Concurrent Versioning System{\textquoteright}) source code management tool" "Fourthly, in order obtain contextual understanding of the project we collected publicly available documents related to open source in general and to the project in particular. Among the most important sources were the Freenet project web pages (e.g. the Frequently Asked Questions (FAQ)7), Ian Clarke{\textquoteright}s master thesis (1999), newspaper interviews with the core developers, and a technical paper (Clarke, Sandberg, Wiley, \& Hong, 2000) describing the Freenet project written by some of the developers."}, pages = {1217-1241}, abstract = {This paper develops an inductive theory of the open source software innovation process by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. We are particularly interested in the strategies and processes by which new people join the existing community of software developers, and how they initially contribute code. Analyzing data from multiple sources on the Freenet software development process, we generate the constructs of "joining script", We are grateful to helpful comments from two anonymous reviewers. We also thank Chris Argyris, John Seely Brown, Eric von Hippel, Stefan Haefliger, Petra Kugler, Heike Bruch, Simon Gchter, Simon Peck, and Hari Tsoukas for helpful comments and suggestions. Ben Ho and Craig Lebowitz provided technical assistance with data importation and parsing. We would like to thank Ian Clarke and the Freenet developers for their willingness to participate in our study and providing key insights into the open source development process. Karim R. Lakhani would like to acknowledge the generous support of The Boston Consulting Group and Canada{\textquoteright}s Social Science and Humanities Research Council doctoral fellowship. Georg von Krogh and Sebastian Spaeth acknowledge the generous support from the Research Foundation at the University of St. Gallen.}, keywords = {cvs, email, email archives, freenet, INNOVATION, mailing lists, roles, source code}, doi = {http://dx.doi.org/10.1016/S0048-7333(03)00050-7}, attachments = {https://flosshub.org/sites/flosshub.org/files/krogh03.pdf}, author = {Georg von Krogh and Spaeth, S. and Karim R Lakhani} } @article {flosswp74, title = {Community, Joining, and Specialization in Open Source Software Innovation: A Case Study}, journal = {RP Special Issue}, year = {2003}, month = {February}, abstract = {This paper develops an inductive theory of the open source software innovation process by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. We are particularly interested in the strategies and processes by which new people join the existing community of software developers, and how they initially contribute code. Analyzing data from multiple sources on the Freenet software development process, we generate the constructs of "joining script", "specialization", "contribution barriers", and "feature gifts", and propose relationships among these. Implications for theory and research are discussed.}, attachments = {https://flosshub.org/sites/flosshub.org/files/rp-vonkroghspaethlakhani.pdf}, author = {Georg von Krogh} } @article {flosswp120, title = {Comparing motivations of individual programmers and firms to take part in the Open Source movement. From community to business}, year = {2003}, month = {October}, abstract = {A growing body of economic literature is addressing the incentives of the individuals that take part to the Open Source movement. However, empirical analyses focus on individual developers and neglect firms that do business with Open Source software (OSS). During 2002, we conducted a large-scale survey on 146 Italian firms supplying Open Source solutions in Italy. In this paper our data on firms? motivations are compared with data collected by the surveys made on individual programmers. We aim at analysing the role played by different classes of motivations (social, economic and technological) in determining the involvement of different groups of agents in Open Source activities.}, attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossimotivationlong.pdf}, author = {Andrea Bonaccorsi} } @article {908, title = {Continuous Design of Free/Open Source Software: Workshop Report and Research Agenda}, year = {2003}, month = {October 15}, institution = {UCI-UIUC Workshop on Continuous Design of Open Source Software}, author = {Gasser, Les and Walt Scacchi} } @article {flosswp103, title = {Contributing to the common pool resources in Open Source software. A comparison between individuals and firms}, year = {2003}, month = {August}, abstract = {This paper studies the contributions to Open Source projects of software firms. Our goal is to analyse whether they follow the same regularities that characterize the behaviour of individual programmers. An exhaustive empirical analysis is carried out using data on project membership, project coordination and contribution efforts of 146 Italian firms that do business with Open Source software. We follow a meta-analytic approach comparing our findings with the results of the surveys conducted on Free Software programmers. Moreover, the availability of the data gathered by Hertel et al. (2003) on 141 developers of the Linux kernel will allow direct comparisons between the two sets.}, keywords = {developers, linux, linux kernel, Survey}, attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossidevelopers.pdf}, author = {Andrea Bonaccorsi} } @article {flosswp136, title = {The Contribution of Free Software to Software Evolution}, year = {2003}, month = {September}, abstract = {t is remarkable to think that even without any interest in finding suitable methods and concepts that would allow complex software systems to evolve and remain manageable, the ever growing open source movement has silently managed to establish highly successful evolution techniques over the last two decades. These concepts represent best practices that could be applied equally to a number of today?s most crucial problems concerning the evolution of complex commercial software systems. In this paper, the authors state and explain some of these principles from the perspective of experienced open source developers, and give the rationale as to why the highly dynamic free software development process, as a whole, is entangled with constantly growing code bases and changing project sizes, and how it deals with these successfully.}, attachments = {https://flosshub.org/sites/flosshub.org/files/bauerpizka.pdf}, author = {Andreas Bauer} } @unpublished {flosswp196, title = {A critical approach to Open Source Software}, year = {2003}, month = {June}, abstract = {The purpose of this masters{\textquoteright} thesis was to discuss a number of assumptions regarding the benefits of Open Source software projects. By studying what has been written about Open Source combined with a number of own data collections, this thesis argues that: Brooks law is still valid in Open Source projects; Many Open Source projects are failures; Open Source culture is a product of the 90s, not the 70s Open Source is no guarantee for reduced lock-in effects; Our most famous Open Source projects are not built up by nerds working for free, but professionals, employed by commercial companies to contribute to the projects; Large Open Source projects are often hierarchical and bureaucratic Opening your source does not automatically lead to a large number of contributors; Open Source breeds diversity, not a single winner; Open Source projects often targets the community itself, rather than external actors; Companies benefiting from Open Source are often based on traditional business models rather than revolutionary visions. Open Source is not necessarily an efficient way to develop software.}, attachments = {https://flosshub.org/sites/flosshub.org/files/gorling.pdf}, author = {Stefan Gorling} } @book {122, title = {Cyberscience: Research in the Age of the Internet}, year = {2003}, publisher = {Austrian Academy of Sciences}, organization = {Austrian Academy of Sciences}, address = {Vienna}, author = {Michael Nentwich} } @article {flosswp40, title = {Cave or Community? An Empirical Examination of 100 Mature Open Source Projects}, journal = {First Monday}, volume = {7}, number = {6}, year = {2002}, note = {The author conducts an empirical study of the top 100 mature projects on SourceForge.net to develop an understanding of the F/OSS community. The author sought empirical evidence that would help us understand which is more common- the cave (i.e., lone producer) or the community in F/OSS development. Some key findings include: first, most F/OSS programs are developed by individuals, rather than communities. Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project is unrelated to the age of the project.}, month = {06/2002}, abstract = {Starting with Eric Raymond{\textquoteright}s groundbreaking work, "The Cathedral and the Bazaar", open-source software (OSS) has commonly been regarded as work produced by a community of developers. Yet, given the nature of software programs, one also hears of developers with no lives that work very hard to achieve great product results. In this paper, I sought empirical evidence that would help us understand which is more common - the cave (i.e., lone producer) or the community. Based on a study of the top 100 mature products on Sourceforge, I find a few surprising things. First, most OSS programs are developed by individuals, rather than communities. The median number of developers in the 100 projects I looked at was 4 and the mode was 1 - numbers much lower than previous numbers reported for highly successful projects! Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project was positively correlated to the age of the project. Fifth, the larger the project, the smaller the percent of project administrators.}, keywords = {age, contributors, developers, project success, registration, sourceforge}, attachments = {https://flosshub.org/sites/flosshub.org/files/krishnamurthy.pdf}, author = {Sandeep Krishnamurthy} } @unpublished {flosswp65, title = {Characteristics and Applicability of Open Source-Based Product Development Model in Other than Software Industries}, year = {2002}, month = {October}, abstract = {The main objective of this research is to examine the Open Source product development paradigm and its applicability to other than software industries. First part of this paper examines the NPD process, its evolution and main characteristics during years. Than approaches to product development adopted in Open Source projects are presented, with emphasis on the managerial and knowledge related issues, as those are focal to NPD. In the second part Open Source-based Product Development Model is being constructed and its applicability to other than open source software industry verified.}, attachments = {https://flosshub.org/sites/flosshub.org/files/siedlok.pdf}, author = {Franciszek Siedlok} } @conference {1153, title = {Characterizing the OSS process}, booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source}, year = {2002}, note = {"We have considered two well-known Open Source portals (FreshMeat [1] and SourceForge [2] )." "Using pseudo-random sampling we have selected a sample of 400 projects (mostly from FreshMeat). Each project is described by several variables (programming language, type of license, size of source code, type of documentation available and others). By indirect means (analysis of the Changelog file, or CVS) it is also possible to compute the number of people working on the project, and the number of external contributors. From FreshMeat we get both a vitality index, that considers the number of releases per time period, and a popularity index, which is a first measure of the interest of users to the project (project URL hits, mixed with subscriptions to it)."}, abstract = {The Open Source model of software development has gained the attention of both the business, the practitioners{\textquoteright} and the research communities. The Open Source process has been described by the seminal paper by Eric Raymond [4] and [5]. However, sound empirical studies are still very limited [3], [6]. Our goal is to investigate the OS process by empirical means, to analyze, characterize it, and possibly model it with quantitative models. It should be noted that the Open Source process provides open process and product data, and therefore is a rare opportunity for empirical research. Our initial research focus is on the characterization of the process, starting from the evolution of OS projects. In traditional projects, a significant number of releases in a short time is usually considered an instability factor [7] and [8], while in the OSS community, it is an evidence of vitality, shows the commitment of the authors and the power of attraction of other programmers [9]. Is it possible to characterize the vitality of projects? And, can vitality be traced to some other characteristics of a project?}, keywords = {bugs, change log, classification, cvs, downloads, freshmeat, metadata, patches, popularity, project success, release history, sourceforge, vitality}, attachments = {https://flosshub.org/sites/flosshub.org/files/CapiluppiLagoMorisio.pdf}, author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio} } @article {70, title = {Coase{\textquoteright}s penguin, or, Linux and The Nature of the Firm}, journal = {Yale Law Journal}, volume = {112}, number = {3}, year = {2002}, month = {Dec}, pages = {369-+}, abstract = {For decades our common understanding of the organization of economic production has been that individuals order their productive activities in one of two ways: either as employees in firms, following the directions of managers, or as individuals in markets, following price signals. This dichotomy was first identified in the early work of Ronald Coase and was developed most explicitly in the work of institutional economist Oliver Williamson. Recently, public attention has focused on a fifteen-year-old phenomenon called free software or open source software. This phenomenon involves thousands, or even tens of thousands, of computer programmers who collaborate on large- and small-scale projects without traditional firm-based or market-based ownership of the resulting product. This Article explains why free software is only one example of a much broader social-economic phenomenon emerging in the digitally networked. environment, a third mode of production that the author calls "commons-based peer production." The Article begins by demonstrating the widespread use of commons-based peer production on the Internet through a number of detailed examples, such as Wikipedia, Slashdot the Open Directory Project, and Google. The Article uses these examples to reveal fundamental characteristics of commons-based peer production that distinguish it from the property- and contract-based modes of firms and markets. The central distinguishing characteristic. is that groups of individuals successfully collaborate on large-scale projects following a diverse cluster of motivational drives and social signals rather than market prices or managerial commands. The Article then explains why this mode has systematic advantages over markets and managerial hierarchies in the digitally networked environment when the object of production is information or culture. First, peer production has an advantage in what the author calls "information opportunity cost," because it loses less information about who might be the best person for a given job. Second, there are substantial increasing allocation gains to be captured from allowing large clusters of potential contributors to interact with large clusters of information resources in search of new projects and opportunities for collaboration. The Article concludes with an overview of how these models use a variety of technological, social, and formal strategies to overcome the collective action problems usually solved in managerial and market-based systems by property, contract, and managerial commands.}, isbn = {0044-0094}, author = {Benkler, Y.} } @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} } @conference {1161, title = {The Coming Software Revolution}, booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source}, year = {2002}, abstract = {The growing adoption of collaborative software development will change the global software industry by altering its economics of scale, location, and price. The growth of non-proprietary code will depress prices in the proprietary sector, and the possession of source code will enable the growth of more software industrial centers around the world; their emergence will threaten the business of current leaders. National governments which see themselves as disadvantaged or even threatened by the current software powers will encourage collaborative software development and the services that this development model drives. Only world-wide draconic legislation by the current software powers has any hope of preserving the status quo.}, keywords = {ECONOMICS, management, open source, politics}, attachments = {https://flosshub.org/sites/flosshub.org/files/Rosenberg.pdf}, author = {Rosenberg, D.K.} } @article {flosswp37, title = {Community Effort in Online Groups? Who Does the Work and Why?}, year = {2002}, month = {February}, abstract = {In this paper, the authors consider how the formal leadership role, personal and community benefits, and community characteristics influence the effort members put into helping their online groups. Results from a survey of Internet listserv owners and other members suggest that though owners, who have a formal leadership role, do more of the effortful community building work than do regular members, other members also take on some of the work. Moreover, members who value different benefits are likely to contribute to the development on an online community in different ways.}, attachments = {https://flosshub.org/sites/flosshub.org/files/butler.pdf}, author = {Brian Butler} } @article {flosswp38, title = {Competing on Open Source: Strategies and Practise}, year = {2002}, month = {January}, abstract = {This paper seeks to address the following issues: How do firms compete with open source? What resources become critical in managing their growth? What strategies do they adopt to co-exist with dominant proprietary software firms? How do they interface with communities of practice to exploit network externalities? What strategies do they adopt to lock-in developers? Based on a multiple case analysis the authors seek to draw initial conclusions about the key strategic aspects that underlie the open source initiatives. Finally they describe how for-profit firms can establish and sustain open source practice.}, attachments = {https://flosshub.org/sites/flosshub.org/files/madanmohan.pdf}, author = {T.R. Madanmohan} } @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} } @article {flosswp53, title = {Counting potatoes: The size of Debian 2.2}, year = {2002}, month = {March}, abstract = {Debian is possibly the largest free software distribution, with well over 2,800 source packages in the latest stable release (Debian 2.2) and more than 4,000 source packages in the release currently in preparation. But, how large is "the largest"? We show that Debian 2.2 includes more than 55,000,000 physical SLOC (almost twice than Red Hat 7.1, released about 8 months later), showing that the Debian development model (based on the work of a large group of voluntary developers spread around the world) is at least as capable as other development methods (like the more centralized one) to manage distributions of this size. It is also shown that if Debian had been developed using traditional proprietary methods, that its cost would be close to $1.9 billion. In addition, we offer both an analysis of the programming languages used in the distribution.}, attachments = {https://flosshub.org/sites/flosshub.org/files/counting-potatoes.html}, author = {Jesus M. Gonzalez-Barahona} } @article {54, title = {Code, Culture and Cash: The Fading Altruism of Open Source Development}, journal = {First Monday}, volume = {6}, number = {12}, year = {2001}, note = {"I collected information on the country of residence for key contributors to the two projects. In the case of Linux, I relied on information located in the CREDITS file of all major kernel releases (from version 1.0 to version 2.4.9) [22]. For Gnome, I gathered developer-contact information from the project{\textquoteright}s web-site. Where information on the home-country of developers was not explicitly available, I performed private research to ascertain said information, or - in the last-case scenario - trusted information in the provided e-mail address of developers to infer home-country from domain ownership [23]. In the case of Linux, to avoid bias that might be introduced over time as developers migrated internationally, developers are continually counted as residents of the countries they were associated with when their names first entered the CREDITS file"}, abstract = {The nexus of open source development appears to have shifted to Europe over the last ten years. This paper explains why this trend undermines cultural arguments about "hacker ethics" and "post-scarcity" gift economies. It suggests that classical economic theory offers a more succinct explanation for the peculiar international distribution of open source development: hacking rises and falls inversely to its opportunity cost. This finding throws doubt on the Schumpeterian assumption that the efficiency of industrial systems can be measured without reference to the social institutions that bind them.}, keywords = {credits, email address, european, geography, gnome, linux}, url = {http://131.193.153.231/www/issues/issue6_12/lancashire/index.html}, attachments = {https://flosshub.org/sites/flosshub.org/files/Lancashire.pdf}, author = {David Lancashire} } @conference {1144, title = {Conceptual Sociological Model for Open Source Software}, booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001}, year = {2001}, attachments = {https://flosshub.org/sites/flosshub.org/files/kishida.pdf}, author = {Kishida, Kouichi} } @conference {1136, title = {Configuration Management for Open Source Software}, booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001}, year = {2001}, month = {05/2001}, abstract = {Open Source Software (OSS) projects have a seemingly anarchistic way of organising projects and a set-up (many, distributed developers) that is usually considered difficult to handle within the field of configuration management. Still they manage to produce software that is of at least as high a quality as that produced by Conventional Software Development (CSD) projects. We have investigated more closely what they actually do, and why they are so successful. The goal of the study was to describe their underlying configuration management process, thereby making it explicit, so it can be followed in case others (like commercial companies) want to start an OSS project or a project having similar characteristics. We also analysed to what extent their success is due to a good process, good tools or simply to outstanding people participating in OSS projects. Based on this, lessons could be learned from OSS and possible transferred to conventional ways of developing software. We interviewed key people from three OSS projects (KDE, Mozilla and Linux) to obtain data for our study.}, keywords = {configuration management, interviews, project success}, attachments = {https://flosshub.org/sites/flosshub.org/files/asklundbendix.pdf}, author = {Asklund, U. and Bendix, L.} } @conference {1141, title = {Corporate Source: Applying Open Source Concepts to a Corporate Environment}, booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001}, year = {2001}, keywords = {commercial software, hewlett packard, hp, organizational sponsorship}, attachments = {https://flosshub.org/sites/flosshub.org/files/dinkelackergarg.pdf}, author = {Dinkelacker, J. and Garg, P.K.} } @conference {1138, title = {Creating a Free, Dependable Software Engineering Environment for Building Java Applications}, booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001}, year = {2001}, abstract = {As open source software engineering becomes more prevalent, employing sound software engineering practices and the tools used to implement these practices becomes more important. This paper examines the current status of free software engineering tools. For each set of tools, we determined the important attributes that would best assist a developer in each stage of the waterfall model. We rated each tool based on predetermined attributes. We used the creation of a graphical user interface based email client in Java to assist in evaluating each tool. Our findings show that there is still a need for free tools to extract UML diagrams, test graphical user interfaces, make configuring Emacs easier, and profile Java applications. In other areas there are free tools that provide satisfactory functionality such as Concurrent Versions System (CVS), GVim, JUnit, JRefactory, GNU Make, Jakarta Ant, Javadoc, and Doc++.}, keywords = {applications, cvs, Doc++, GNU Make, GVim, Jakarta Ant, java, Javadoc, jrefactory, junit, tools}, attachments = {https://flosshub.org/sites/flosshub.org/files/bittman.pdf}, author = {Bittman, M. and Roos, R. and Kapfhammer, G.M.} } @article {flosswp26, title = {A Case Study of Open Source Software Development: The Apache Server}, journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)}, year = {2000}, note = {We used the following archival sources of data: Developer email list (EMAIL). Concurrent Version Control archive (CVS). Problem reporting database (BUGDB).}, month = {June}, abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.}, keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size}, attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf}, author = {Audris Mockus and Roy Fielding and Herbsleb, James} } @conference {Yamauchi:2000:CLM:358916.359004, title = {Collaboration with Lean Media: how open-source software succeeds}, booktitle = {Proceedings of the 2000 ACM conference on Computer supported cooperative work (CSCW)}, series = {CSCW {\textquoteright}00}, year = {2000}, pages = {329{\textendash}338}, publisher = {ACM}, organization = {ACM}, address = {New York, NY, USA}, abstract = {Open-source software, usually created by volunteer programmers dispersed worldwide, now competes with that developed by software firms. This achievement is particularly impressive as open-source programmers rarely meet. They rely heavily on electronic media, which preclude the benefits of face-to-face contact that programmers enjoy within firms. In this paper, we describe findings that address this paradox based on observation, interviews and quantitative analyses of two open-source projects. The findings suggest that spontaneous work coordinated afterward is effective, rational organizational culture helps achieve agreement among members and communications media moderately support spontaneous work. These findings can imply a new model of dispersed collaboration.}, keywords = {cooperative work, cvs, distributed work, electronic media, INNOVATION, open-source, software engineering}, isbn = {1-58113-222-0}, doi = {10.1145/358916.359004}, url = {http://doi.acm.org/10.1145/358916.359004}, author = {Yamauchi, Yutaka and Yokozawa, Makoto and Shinohara, Takeshi and Ishida, Toru} } @book {55, title = {Code and Other Laws of Cyberspace}, year = {1999}, publisher = {Basic Books}, organization = {Basic Books}, author = {Lessig, L.} } @article {flosswp24, title = {Changing Competitive Dynamics in Network Industries: An Exploration of SUN Microsystems{\textquoteright} Open Systems Strategy}, year = {1993}, month = {Unspecified}, abstract = {An integral part of competition is to deny rivals access to proprietary technical knowledge. Yet, SUN Microsystems provides rivals with easy access to its technical knowledge and encourages them to enter its workstation market. This paper employs theoretical insights on technological systems and network externalities to understand SUN{\textquoteright}s open systems strategy. The paper also explores the changing nature of competition in network industries.}, author = {Raghu Garud} }