<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Validity Issues in the Use of Social Network Analysis with Digital Trace data</style></title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Online Communities</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">Submitted</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/HowisonSNADigitalTraceData-WorkingPaper.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">FLOSSHub</style></publisher><work-type><style face="normal" font="default" size="100%">Working Paper</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Squire, Megan</style></author><author><style face="normal" font="default" size="100%">Williams, David</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Describing the Software Forge Ecosystem</style></title><secondary-title><style face="normal" font="default" size="100%">45th Hawai'i International Conference on System Sciences</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2012</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">3416-3425</style></pages><abstract><style face="normal" font="default" size="100%">Code forges are online software systems that are designed to support teams doing software development work. There have been few if any attempts in the research literature to describe the web of people, projects, and tools that make up the free, libre, and open source (FLOSS) forge ecosystem. The main contributions of this paper are (1) to introduce a classification of FLOSS-oriented forges according to their characteristics; (2) to describe the forge-level and project-level data and artifacts currently available at each FLOSS forge; (3) to show various patterns already discovered in the FLOSS forge ecosystem, such as timelines of creation or arrangements by size or feature; (4) to make some recommendations to forge providers and data collectors about how to expose the structure and information in the forges; and (5) to describe the effort needed to extend our publicly- available information about the FLOSS forge ecosystem into the future.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu, Yiqing</style></author><author><style face="normal" font="default" size="100%">Benlian, Alexander</style></author><author><style face="normal" font="default" size="100%">Hess, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study of Volunteer Members' Perceived Turnover in Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">45th Hawai'i International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">launchpad</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2012</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">3396-3405</style></pages><abstract><style face="normal" font="default" size="100%">Turnover of volunteer members and the ensuing instability bring about severe problems to open source software (OSS) projects. To better understand it, we based our study on Herzberg ́s two-factor theory to investigate the influence of hygiene factors on volunteer members ́ dissatisfaction and perceived turnover. After empirically testing the research model, we found shortcomings in project regulation and administration are the key reason for volunteer members ́ dissatisfaction, followed by future rewards and personal needs for software functionalities. By contrast, a possible lack of supportive working relationship among OSS developers was not found to be a trigger for developer dissatisfaction. Dissatisfaction was confirmed to be a significant predictor of perceived turnover. The results demonstrates generalized hygiene factors cannot unreflectively be transferred into the OSS context because volunteer members ́ personal expectation has a weaker influence on perceived turnover than objective attributes of OSS project. Our study further makes suggestions for project administrators.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;After designing the questionnaire, we conducted a web-based survey by inviting developers working in sourceforge.net and launchpad.net.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Le, Qize</style></author><author><style face="normal" font="default" size="100%">Panchal, Jitesh H.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Network-Based Analysis of the Structure and Evolution of an Open Source Software Product</style></title><secondary-title><style face="normal" font="default" size="100%">45th Hawai'i International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">drupal</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2012</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">3436-3445</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, an analysis of product structures in open source software (OSS) at both product level and module level is presented. At the product level, the product structures are modeled as complex networks, and the evolutionary characteristics of product structures are analyzed by using network analysis metrics. At the module level, linking mechanisms, which describe how a module is attached with other modules, are proposed. The linking mechanisms are modeled as probability functions dependent on the degrees of linking modules. A case study from an open source software project, Drupal, is presented. The evolutionary trends of Drupal product structures are analyzed and discussed. Finally, a model is presented to illustrate the effects of linking mechanisms at the module level on the product structures at the system level. The results indicate that the model built using the proposed linking mechanisms generates networks whose evolutionary characteristics are close to that of the original network.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;raw data about the product structure is extracted from the source code&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schilling, A.</style></author><author><style face="normal" font="default" size="100%">Laumer, S.</style></author><author><style face="normal" font="default" size="100%">Weitzel, T.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">45th Hawai'i International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">google summer of code</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">students</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2012</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2012</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">3446-3455</style></pages><abstract><style face="normal" font="default" size="100%">Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals' subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Kangning Wei</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Libre Open Source Software: What We Know and What We Do Not Know</style></title><secondary-title><style face="normal" font="default" size="100%">ACM Computing Surveys</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2012</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/floss_review_paper.pdf</style></url></related-urls></urls><edition><style face="normal" font="default" size="100%">2</style></edition><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><volume><style face="normal" font="default" size="100%">44</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We review the empirical research on Free/Libre Open Source Software (FLOSS) development and assess the state of the literature. Our review is organized around an input-mediator-output-input (IMOI) model. We start with a description of the articles selected for the review. We then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest research questions, including methodological and theoretical issues, to guide future inquiry in this area.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Petrinja, Etiel</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Adoption of OSS Development Practices by the Software Industry: A Survey</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">qualipso</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">233-243</style></pages><abstract><style face="normal" font="default" size="100%">The paper presents a survey of aspects related to the adoption of Open Source Software by the software industry. The aim of this study was to collect data related to practices and elements in the development process of companies that influence the trust in the quality of the product by potential adopters. The work is part of the research done inside the QualiPSo project and was carried out using a qualitative study based on a structured questionnaire focused on perceptions of experts and development practices used by companies involved in the Open Source Software industry. The results of the survey confirm intuitive concerns related to the adoption of Open Source Software as: the selection of the license, the quality issues addressed, and the development process tasks inside Open Source Software projects. The study uncovered specific aspects related to trust and trustworthiness of the Open Source Software development process that we did not find in previous studies as: the standards implemented by the OSS project, the project's roadmap is respected, and the communication channels that are available.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Taylor, Quinn C.</style></author><author><style face="normal" font="default" size="100%">Krein, Jonathan L.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Analysis of Author Contribution Patterns in Eclipse Foundation Project Source Code</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">COLLABORATION</style></keyword><keyword><style  face="normal" font="default" size="100%">contribution</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">269-281</style></pages><abstract><style face="normal" font="default" size="100%">Collaborative development is a key tenet of open source software, but if not properly understood and managed, it can become a liability. We examine author contribution data for the newest revision of 251,633 Java source files in 592 Eclipse projects. We use this observational data to analyze collaboration patterns within files, and to explore relationships between file size, author count, and code authorship. We calculate author entropy to characterize the contributions of multiple authors to a given file, with an eye toward understanding the degree of collaboration and the most common interaction patterns.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We conducted an observational study on existing Eclipse projects by extracting author attribution data for Java source code files from git repositories.&quot;

&quot;Specifically, we consider entropy of source code by counting the number of lines attributed to each author.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kilamo, Terhi</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author><author><style face="normal" font="default" size="100%">Kairamo, Ville</style></author><author><style face="normal" font="default" size="100%">Rasanen, Petri</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Applying Open Source Practices and Principles in Open Innovation: The Case of the Demola Platform</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">307-311</style></pages><abstract><style face="normal" font="default" size="100%">In numerous fields, businesses have to rely on rapid development and release cycles. Variant new ideas and concepts can emerge through open innovation as the participants are not limited to the company scope. This makes open innovation an increasingly appealing option for the industry. One such open innovation platform, Demola, allows university students to work on real life industrial cases of their own interest. We have identified similarities with its way of operation to open source software development and find that it offers a viable motivational, organizational and collaborative solution to open innovation.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Arantes, Flavia Linhalis</style></author><author><style face="normal" font="default" size="100%">Freire, Fernanda Maria Pereira</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Aspects of an Open Source Software Sustainable Life Cycle</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Financial Resources</style></keyword><keyword><style  face="normal" font="default" size="100%">OSS Communities</style></keyword><keyword><style  face="normal" font="default" size="100%">OSS Sustainability</style></keyword><keyword><style  face="normal" font="default" size="100%">software maintenance</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">325-329</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we present a literature overview about OSS sustainability, considering not only financial resources, but also community growth, source code and tools management. Based on these aspects, we define an OSS life cycle that may contribute to OSS projects sustainability.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mulazzini, Fabio</style></author><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Steff, Maximilian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Building Knowledge in Open Source Software Research in Six Years of Conferences</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Cross-citations</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">graph</style></keyword><keyword><style  face="normal" font="default" size="100%">literature review</style></keyword><keyword><style  face="normal" font="default" size="100%">network</style></keyword><keyword><style  face="normal" font="default" size="100%">research</style></keyword><keyword><style  face="normal" font="default" size="100%">Systematic Mapping Study</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">123-141</style></pages><abstract><style face="normal" font="default" size="100%">Since its origins, the diffusion of the OSS phenomenon and the information about it has been entrusted to the Internet and its virtual communities of developers. This public mass of data has attracted the interest of researchers and practitioners aiming at formalizing it into a body of knowledge. To this aim, in 2005, a new series of conferences on OSS started to collect and convey OSS knowledge to the research and industrial community. Our work mines articles of the OSS conference series to understand the process of knowledge grounding and the community surrounding it. As such, we propose a semi-automated approach for a systematic mapping study on these articles. We automatically build a map of cross-citations among all the papers of the conferences and then we manually inspect the resulting clusters to identify knowledge building blocks and their mutual relationships. We found that industry-related, quality assurance, and empirical studies often originate or maintain new streams of research.</style></abstract><notes><style face="normal" font="default" size="100%">RQ1. Is there any social network underlying the research production at the OSS conference series?
RQ2. What are the major streams of research proposed at the OSS conference series?</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Pratt, Landon J.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Ringger, Eric K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Cliff Walls: An Analysis of Monolithic Commits Using Latent Dirichlet Allocation</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">artifacts</style></keyword><keyword><style  face="normal" font="default" size="100%">commit</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">LDA</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">282-298</style></pages><abstract><style face="normal" font="default" size="100%">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 “Cliff Walls,” 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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Our data set consists of the version control logs of almost 10,000 projects from SourceForge, acquired in late 2006&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bass, Len</style></author><author><style face="normal" font="default" size="100%">Kazman, Rick</style></author><author><style face="normal" font="default" size="100%">Ozkaya, Ipek</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Developing Architectural Documentation for the Hadoop Distributed File System</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">50-61</style></pages><abstract><style face="normal" font="default" size="100%">Many open source projects are lacking architectural documentation that describes the major pieces of the system, how they are structured, and how they interact. We have produced architectural documentation for the Hadoop Distributed File System (HDFS), a major open source project. This paper describes our process and experiences in developing this documentation. We illustrate the documentation we have produced and how it differs from existing documentation by describing the redundancy mechanisms used in HDFS for reliability.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin, Guy</style></author><author><style face="normal" font="default" size="100%">Lippold, Aaron</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Forge.mil: A Case Study for Utilizing Open Source Methodologies Inside of Government</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">334-337</style></pages><abstract><style face="normal" font="default" size="100%">In late 2008, DISA (Defense Information Systems Agency), the global IT arm of the US Department of Defense, embarked upon a project to create an internal collaboration and software application lifecycle management system. Beyond simply fielding yet another tool, the Forge.mil effort was designed to fundamentally change the way the DoD developed and acquired software technology and systems. The method of this change was the application of Open Source principles inside of the larger DoD community, including ideas such as meritocracy and code sharing, as well as Agile and collaborative software development. This lightning talk will explain the rationale behind Forge.mil, how it was developed using Open Source principles, and how it continues to influence technology acquisition within the DoD in both practice and policy changes.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maha Shaikh</style></author><author><style face="normal" font="default" size="100%">Cornford, Tony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Framing the Conundrum of Total Cost of Ownership of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">benefits</style></keyword><keyword><style  face="normal" font="default" size="100%">exit costs</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">software adoption</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword><keyword><style  face="normal" font="default" size="100%">tco</style></keyword><keyword><style  face="normal" font="default" size="100%">total cost of ownership</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">208-219</style></pages><abstract><style face="normal" font="default" size="100%">This paper reflects the results of phase I of our study on the total cost of ownership (TCO) of open source software adoption. Not only have we found TCO to be an intriguing issue but it is contentious, baffling and each company approaches it in a distinctive manner (and sometimes not at all). In effect it is a conundrum that needs unpacking before it can be explained and understood. Our paper discusses the components of TCO as total cost of ownership and total cost of acquisition (and besides). Using this broad dichotomy and its various components we then analyze our data to make sense of procurement decisions in relation to open source software in the public sector and private companies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kulesza, Raoni</style></author><author><style face="normal" font="default" size="100%">Lima, Jefferson F.A.</style></author><author><style face="normal" font="default" size="100%">Guedes, Alan L.</style></author><author><style face="normal" font="default" size="100%">Junior, Lucenildo L.A.</style></author><author><style face="normal" font="default" size="100%">Meira, Silvio R.L.</style></author><author><style face="normal" font="default" size="100%">Filho, Guido L.S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Ginga-J: An Open Java-Based Application Environment for Interactive Digital Television Services</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">34-49</style></pages><abstract><style face="normal" font="default" size="100%">This paper aims to present a Ginga-J’s reference implementation. Although based on a particular platform, the implementation not only works as a proof of concept, but also raised several issues and difficulties on the software architecture project that should be taken into account to ease extensibility and porting to other platforms. Ginga is the standard middleware for the Brazilian DTV System. Its imperative environment (Ginga-J) is based on new JavaDTV specification and mandatory for fixed terrestrial receptors.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cavalini, Luciana T.</style></author><author><style face="normal" font="default" size="100%">Cook, Timothy W.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Health Informatics: The Relevance of Open Source and Multilevel Modeling</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Health informatics</style></keyword><keyword><style  face="normal" font="default" size="100%">multilevel modeling</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">338-347</style></pages><abstract><style face="normal" font="default" size="100%">Health information features significant spatial-temporal and domain complexities, which brings challenges to the implementation of patient-centered, interoperable and semantically coherent healthcare information systems. This position paper supports the idea that the multilevel modeling approach is essential to ensure interoperability at the semantic level, but true interoperability is only achieved by the adoption of open standards, and open source implementations are needed for promote competition based on software quality. The Multilevel Healthcare Information Modelling (MLHIM) specifications are presented as the fully open source multilevel modeling reference implementation, and best practices for the development of multilevel- based open source healthcare applications are suggested.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors></contributors><titles><title><style face="normal" font="default" size="100%">A Historical Account of the Value of Free and Open Source Software: From Software Commune to Commercial Commons</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Free and Open Source Software</style></keyword><keyword><style  face="normal" font="default" size="100%">Historical approach</style></keyword><keyword><style  face="normal" font="default" size="100%">Justification</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">196-207</style></pages><abstract><style face="normal" font="default" size="100%">Free and open source software has transformed from what has been characterized as a resistance movement against proprietary software to become a commercially viable form of software development, integrated in various forms with proprietary software business. In this paper we explain this development as a dependence on historical formations, shaped by different ways of justifying the use of open source during different periods of time. These formations are described as arrangements of different justificatory logics within a certain time frame or a certain group of actors motivating the use of free and open source software by referring to different potentialities. The justificatory arrangements change over time, and tracing these changes makes it easier to understand how the cultural, economic and social practices of open source movements are currently being absorbed and adopted in a commercial context.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;In order to understand how perceptions of FOSS software have developed over time, we have traced justifying arrangements that historically have been used to define the value of FOSS. This has been done by going through canonical texts and previous research [3]; i.e. we look at research and publications considered to have had a major impact on the perception of FOSS....&quot;

Software Commune, software bazaar, public commons</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Duc, Ach Nguyen</style></author><author><style face="normal" font="default" size="100%">Cruzes, Daniela S.</style></author><author><style face="normal" font="default" size="100%">Ayala, Claudia</style></author><author><style face="normal" font="default" size="100%">Conradi, Reidar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Impact of Stakeholder Type and Collaboration on Issue Resolution Time in OSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">COLLABORATION</style></keyword><keyword><style  face="normal" font="default" size="100%">companies</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">defects</style></keyword><keyword><style  face="normal" font="default" size="100%">feature requests</style></keyword><keyword><style  face="normal" font="default" size="100%">geronimo</style></keyword><keyword><style  face="normal" font="default" size="100%">jira</style></keyword><keyword><style  face="normal" font="default" size="100%">qpid</style></keyword><keyword><style  face="normal" font="default" size="100%">qt</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">volunteer</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">1-16</style></pages><abstract><style face="normal" font="default" size="100%">Initialized by a collective contribution of volunteer developers, Open source software (OSS) attracts an increasing involvement of commercial firms. Many OSS projects are composed of a mix group of firm-paid and volunteer developers, with different motivations, collaboration practices and working styles. As OSS development consists of collaborative works in nature, it is important to know whether these differences have an impact on collaboration between difference types of stakeholders, which lead to an influence in the project outcomes. In this paper, we empirically investigate the firm-paid participation in resolving OSS evolution issues, the stakeholder collaboration and its impact on OSS issue resolution time. The results suggest that though a firm-paid assigned developer resolves much more issues than a volunteer developer does, there is no difference in issue resolution time between them. Besides, the more important factor that influences the issue resolution time comes from the collaboration among stakeholders rather than from individual characteristics.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;First, we characterize the difference in the average amount of resolved issues and issue resolution time between a volunteer assignee and a firm-paid assignee....Second, we investigate collaboration among stakeholders in OSS projects by using Social network metrics and analysis. Last, we explore the impact of the collaboration measures on issue resolution time.&quot;

&quot;Three OSS projects were selected for our study, namely Qt, Qpid and Geronimo&quot;

&quot;All software issues were collected from JIRA repositories...Issue resolution time was computed by using the created time field and the issue resolved time field.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stol, Klaas-Jan</style></author><author><style face="normal" font="default" size="100%">Ali Babar, Muhammad</style></author><author><style face="normal" font="default" size="100%">Avgeriou, Paris</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Importance of Architectural Knowledge in Integrating Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">architectural knowledge</style></keyword><keyword><style  face="normal" font="default" size="100%">component-based development</style></keyword><keyword><style  face="normal" font="default" size="100%">Open Source Software integration</style></keyword><keyword><style  face="normal" font="default" size="100%">OSS Integrator</style></keyword><keyword><style  face="normal" font="default" size="100%">software architecture</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">142-158</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) is increasingly used in Component-Based Software Development (CBSD) of large software systems. An important issue in CBSD is selection of suitable components. Various OSS selection methods have been proposed, but most of them do not consider the software architecture aspects of OSS products. The Software Architecture (SA) research community refers to a product’s architectural information, such as design decisions and underlying rationale, and used architecture patterns, as Architecture Knowledge (AK). In order to investigate the importance of AK of OSS components in integration, we conducted an exploratory empirical study. Based on in-depth interviews with 12 IT professionals, this paper presents insights into the following questions: 1) what AK of OSS is needed? 2) Why is AK of OSS needed? 3) Is AK of OSS generally available? And 4) what is the relative importance of AK? Based on these new insights, we provide a research agenda to further the research field of software architecture in OSS.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Pratt, Landon J.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Ringger, Eric K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Knowledge Homogeneity and Specialization in the Apache HTTP Server Project</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">commits</style></keyword><keyword><style  face="normal" font="default" size="100%">developer</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">LDA</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">revision control</style></keyword><keyword><style  face="normal" font="default" size="100%">revision history</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">specialization</style></keyword><keyword><style  face="normal" font="default" size="100%">subversion</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">106-122</style></pages><abstract><style face="normal" font="default" size="100%">We present an analysis of developer communication in the Apache HTTP Server project. Using topic modeling techniques we expose latent conceptual sub-communities arising from developer specialization within the greater developer population. However, we found that among the major contributors to the project, very little specialization exists. We present theories to explain this phenomenon, and suggest further research.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Our data set consists of the commit history and email archives for the Apache HTTP Server Project, spanning sixteen years (2/27/1995 - 1/31/2011)&quot;

&quot;we 1) mapped the committers to email records, 2) cleaned the email records to remove extraneous information, 3) identified topics of discussion in the resulting messages, and 4) constructed a social network model from committers and topics.&quot;

&quot;If specialization exists within the httpd community, we should see distinct communities develop around topics. In addition, unique groups of developers should congregate around specialized subtopics. We examined the data from both angles: topical affinity and topic communities.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Goduguluri, Veerakishore</style></author><author><style face="normal" font="default" size="100%">Kilamo, Terhi</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">KommGame: A Reputation Environment for Teaching Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">312-315</style></pages><abstract><style face="normal" font="default" size="100%">The importance of teaching open source software in universities is increasing with the advent of open source as a development and business model. A novel, student centric approach of teaching open source was tried out at Tampere University of Technology where a new environment called KommGame was introduced to assist in teaching open source development. This environment includes a reputation system to motivate learners to participate. In this paper, we present our approach of teaching open source and how the KommGame environment was employed to teach open source software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Henttonen, Katja</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Libre Software as an Innovation Enabler in India: Experiences of a Bangalorian Software SME</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">India</style></keyword><keyword><style  face="normal" font="default" size="100%">INNOVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">software business</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">220-232</style></pages><abstract><style face="normal" font="default" size="100%">Free/Libre and open source software (FLOSS) has been advocated for its presumed capacity to support native software industries in developing countries. It is said to create new spaces for exploration and to lower entry barriers to mature software markets, for example. However, little empirical research has been conducted concerning FLOSS business in a developing country setting and, thus, there is not much evidence to support or refute these claims. This paper presents a business case study conducted in India, a country branded as a 'software powerhouse' of the developing world. The findings show how FLOSS has opened up significant opportunities for the case company, especially in terms of improving its innovative capability and upgrading in the software value chain. On the other hand, they also highlight some challenges to FLOSS involvement that rise specifically from the Indian context.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">License Update and Migration Processes in Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">license evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">process</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">177-195</style></pages><abstract><style face="normal" font="default" size="100%">Open source software (OSS) has increasingly been the subject of research efforts. Central to this focus is the nature under which the software can be distributed, used, and modified and the causes and consequent effects on software development, usage, and distribution. At present, we have little understanding of, what happens when these licenses change, what motivates such changes, and how new licenses are created, updated, and deployed. Similarly, little attention has been paid to the agreements under which contributions are made to OSS projects and the impacts of changes to these agreements. We might also ask these same questions regarding the licenses governing how individuals and groups contribute to OSS projects. This paper focuses on addressing these questions with case studies of processes by which the Apache Software Foundation's creation and migration to Version 2.0 of the Apache Software License and the NetBeans project's migration to the Joint Licensing Agreement.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;The case studies in this report are part of an ongoing, multi-year research project discovering and modeling open source software processes. Our research methodology is ethnographically informed, applying a grounded theory to the analysis of artifacts found in OSS projects. The primary data sources in this study come from mailing list archives of the Apache and NetBeans projects.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Modding as an Open Source Approach to Extending Computer Game Systems</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">games</style></keyword><keyword><style  face="normal" font="default" size="100%">modding</style></keyword><keyword><style  face="normal" font="default" size="100%">mods</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">62-74</style></pages><abstract><style face="normal" font="default" size="100%">This paper examines what is known so far about the role of open source software development within the world of game mods and modding practices. Game modding has become a leading method for developing games by customizing or creating OSS extensions to game software in general, and to proprietary closed source software games in particular. What, why, and how OSS and CSS come together within an application system is the subject for this study. The research method is observational and qualitative, so as to highlight current practices and issues that can be associated with software engineering and game studies foundations. Numerous examples of different game mods and modding practices are identified throughout.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Juho Lindman</style></author><author><style face="normal" font="default" size="100%">Tammisto, Yulia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source and Open Data: Business Perspectives from the Frontline</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">330-333</style></pages><abstract><style face="normal" font="default" size="100%">Open data initiatives on governmental data seem often to be linked to small software companies, which also use and release software under OSS licenses. This paper calls for more research to understand the similarities between open data and open source software vendors. We build a theoretical linkage between the more established OSS research and emerging research on open data in the context of small software companies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gamalielsson, Jonas</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Mattsson, Anders</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software for Model Driven Development: A Case Study</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">348-367</style></pages><abstract><style face="normal" font="default" size="100%">Model Driven Development (MDD) is widely used in the embedded systems domain, and many proprietary and Open Source tools exist that support MDD. The potential for sustainability of such tools needs to assessed prior to any organisational adoption. In this paper we report from a case study conducted in a consultancy company context aiming to investigate Open Source tools for MDD. For the company it was interesting to explore the two Open Source modelling tools Topcased and Papyrus for potential adoption. The focus for our case study is on assessing the health of the ecosystems for the two investigated Open Source projects by means of quantitative analysis of publically available data sources about Open Source projects. The health of ecosystems is an important prerequisite for a long term sustainable OSS (Open Source Software) tool-chain in the MDD area, which can aid strategic decision making for potential adoption within a company context. We have established details on the extent to which developers and users are active in two specific OSS ecosystems, and identified organisational influence for both ecosystems. We find that the investigated tools are promising regarding the health of their ecosystems, and a natural next step for the company would be to proceed with a pilot study in order to analyse the effectiveness of the investigated tools in company contexts.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Thomson, John</style></author><author><style face="normal" font="default" size="100%">Guerrriro, Andre</style></author><author><style face="normal" font="default" size="100%">Paulo Trezentos</style></author><author><style face="normal" font="default" size="100%">Johnson, Jeff</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Package Upgrade Robustness: An Analysis for GNU/Linux Package Management Systems</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">package management</style></keyword><keyword><style  face="normal" font="default" size="100%">rpm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">299-306</style></pages><abstract><style face="normal" font="default" size="100%">GNU/Linux systems are today used in servers, desktops, mobile and embedded devices. One of the critical operations is the installation and maintenance of software packages in the system. Currently there are no frameworks or tools for evaluating Package Management Systems (PMSs), such as RPM, in Linux and for measuring their reliability. The authors perform an analysis of the robustness of the RPM engine and discuss some of the current limitations. This article contributes to the enhancement of Software Reliability in Linux by providing a framework and testing tools under an open source license. These tools can easily be extended to other PMSs such as DEB packages or Gentoo Portage.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matos, Alfredo</style></author><author><style face="normal" font="default" size="100%">Thomson, John</style></author><author><style face="normal" font="default" size="100%">Paulo Trezentos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Preparing FLOSS for Future Network Paradigms: A Survey on Linux Network Management</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">networking</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">75-89</style></pages><abstract><style face="normal" font="default" size="100%">Operating system tools must fulfill the requirements generated by the advances in networking paradigms. To understand the current state of the Free, Libre and Open Source Software (FLOSS) ecosystem, we present a survey on the main tools used to manage and interact with the network, and how they are organized in Linux-based operating systems. Based on the survey results, we present a reference Linux network stack that can serve as the basis for future heterogeneous network environments, contributing towards a standardized approach in Linux. Using this stack, and focusing on dynamic and spontaneous network interactions, we present an evolution path for network related technologies, contributing to Linux as a network research operating system and to FLOSS as a whole.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rantalinen, Aapo</style></author><author><style face="normal" font="default" size="100%">Hedberg, Henrik</style></author><author><style face="normal" font="default" size="100%">Iivari, Netta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Review of Tool Support for User-Related Communication in FLOSS Development</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Free/Libre/Open Source Software</style></keyword><keyword><style  face="normal" font="default" size="100%">Human-Computer Interaction</style></keyword><keyword><style  face="normal" font="default" size="100%">literature review</style></keyword><keyword><style  face="normal" font="default" size="100%">Tool Support</style></keyword><keyword><style  face="normal" font="default" size="100%">User-Developer Communication</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">90-105</style></pages><abstract><style face="normal" font="default" size="100%">Free/Libre/Open Source Software (FLOSS) projects rely on Internet tools for communication and in coordinating their work. Communication between developers is well supported in FLOSS projects, but user-developer communication has proven out to be challenging. This paper examines the following questions: ”What kinds of means for communication exist in FLOSS projects for user-developer communication? What kinds of means should there be?” We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication. HCI literature indicates that user-developer communication is needed during requirements construction, design and evaluation tasks, and HCI specialists are needed for orchestrating the communication and the user related tasks. Communication during the evaluation task is somewhat supported in FLOSS projects, but design and requirements construction are badly in need for support, even though ideas have already been presented. In addition, HCI specialists are in need of different kinds of communication support in FLOSS projects.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Something of a Potemkin Village? Acid2 and Mozilla’s Efforts to Comply with HTML4</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">320-324</style></pages><abstract><style face="normal" font="default" size="100%">The real point here is that the Acid3 test isn’t a broad-spectrum standards-support test. It’s a showpiece, and something of a Potemkin village at that. Which is a shame, because what’s really needed right now is exhaustive test suites for specifications— XHTML, CSS, DOM, SVG.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Noda, Tetsuo</style></author><author><style face="normal" font="default" size="100%">Tansho, Terutaka</style></author><author><style face="normal" font="default" size="100%">Coughlan, Shane</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Standing Situations and Issues of Open Source Policy in East Asian Nations: Outcomes of Open Source Research Workshop of East Asia</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">379-384</style></pages><abstract><style face="normal" font="default" size="100%">East Asia nations have made some progress with this technology, and started to introduce OSS for e-government systems during the early part of this century. Many countries granted it a central role in their policies. The reasons for this include adoption of software based on standard specification, liberation from vender lock-in, or opposition to the market control of proprietary software. However, the primary reason is to reduce adoption costs for e-government systems. While this policy work is useful, there is a great deal more that needs to be done. The OSS adoption policy in each nation of East Asia must be accompanied by technological progress in domestic IT service industries or US multinationals will expand at the cost of local businesses. If this continues unchecked it will create a new form of lock-in for East Asian nations. Some Asian nations are trying to promote their domestic IT service industries, putting their OSS adoption policy to practical use, and this workshop will provide case studies of that work. It will also provide a forum for discussing current challenges and opportunities around both policy and practical implementation issues across Asia.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">Stol, Klaas-Jan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Successful Reuse of Software Components: A Report from the Open Source Perspective</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">component-based software development</style></keyword><keyword><style  face="normal" font="default" size="100%">OSS components</style></keyword><keyword><style  face="normal" font="default" size="100%">Software reuse</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">159-176</style></pages><abstract><style face="normal" font="default" size="100%">A promising way of software reuse is Component-Based Software Development (CBSD). There is an increasing number of OSS products available that can be freely used in product development. However, OSS communities themselves have not yet taken full advantage of the “reuse mechanism”. Many OSS projects duplicate effort and code, even when sharing the same application domain and topic. One successful counter-example is the FFMpeg multimedia project, since several of its components are widely and consistently reused into other OSS projects. This paper documents the history of the libavcodec library of components from the FFMpeg project, which at present is reused in more than 140 OSS projects. Most of the recipients use it as a black-box component, although a number of OSS projects keep a copy of it in their repositories, and modify it as such. In both cases, we argue that libavcodec is a successful example of reusable OSS library of components.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yamakami, Toshihiko</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Third Generation of OSS: A Three-Stage Evolution from Gift to Commerce-Economy</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">368-378</style></pages><abstract><style face="normal" font="default" size="100%">Linux is penetrating into mobile software as the basis for a mobile middleware platform. It is accelerating the increasing visibility of open source software (OSS) components in mobile middleware platforms. Considering the 10-million lines of code of OSS-based industrial platforms such as a mobile middleware platform, engagement in foundations is inevitable for large-scale packages of OSS for industrial solutions. The author discusses the driving factors toward a foundation-based OSS and the transition of the underlying economy types to analyze the transitions to the third-generation OSS.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nyman, Linus</style></author><author><style face="normal" font="default" size="100%">Mikkonen, Tommi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">To Fork or Not to Fork: Fork Motivations in SourceForge Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">fork rate</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">259-268</style></pages><abstract><style face="normal" font="default" size="100%">A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers’ motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Using this search function, we compiled a list of all of the programs with the word “fork”...&quot;
&quot;We then analyzed the motivations stated in the descriptions of the forked programs....&quot;
&quot;Based on the descriptions entered by the developer, we were able to identify motivations for 381 of the forks.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ruiz, Claudia</style></author><author><style face="normal" font="default" size="100%">Robinson, William</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a Unified Definition of Open Source Quality</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">literature review</style></keyword><keyword><style  face="normal" font="default" size="100%">measurement</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">Software</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">17-33</style></pages><abstract><style face="normal" font="default" size="100%">Software quality needs to be specified and evaluated in order to determine the success of a development project, but this is a challenge with Free/Libre Open Source Software (FLOSS) because of its permanently emergent state. This has not deterred the growth of the assumption that FLOSS is higher quality than traditionally developed software, despite of mixed research results. With this literature review, we found the reason for these mixed results is that that quality is being defined, measured, and evaluated differently. We report the most popular definitions, such as software structure measures, process measures, such as defect fixing, and maturity assessment models. The way researchers have built their samples has also contributed to the mixed results with different project properties being considered and ignored. Because FLOSS projects are evolving, their quality is too, and it must be measured using metrics that take into account its community’s commitment to quality rather than just its software structure. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;In order to answer the research question, how is quality defined in the FLOSS literature, we performed a literature review.&quot;

&quot;we searched Google Scholar for journal articles and conference papers containing the terms “open source” and “quality”&quot;

&quot;This process left us with 24 papers, to which we then added 16 from the quality and defect-fixing categories in [34] that met the above stated criteria.
This left us with 40 papers that defined quality and performed some form of empirical validation of that definition.&quot;

&quot;there is little consensus in the FLOSS literature when it comes to defining quality.&quot;

defect resolution versus modularity: &quot;Defect resolution rates (amount of defects resolved, speed of resolution) are the best way to measure a community’s commitment to quality, because they recognize that FLOSS is not a static product, but ever evolving. These rates should be calculated per release, and not cumulatively, because the cycle of FLOSS evolution is the release. Researchers should be careful to only include defects and not new feature requests, duplicates, or poorly reported bugs into their calculations.
Modularity is being touted as the main driver of FLOSS quality success, but it needs to be further defined and studied in order to understand how it works.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ayala, Claudia</style></author><author><style face="normal" font="default" size="100%">Cruzes, Daniela S.</style></author><author><style face="normal" font="default" size="100%">Franch, Xavier</style></author><author><style face="normal" font="default" size="100%">Conradi, Reidar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards Improving OSS Products Selection – Matching Selectors and OSS Communities Perspectives</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">empirical study</style></keyword><keyword><style  face="normal" font="default" size="100%">information rendering strategy</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">selection</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">244-258</style></pages><abstract><style face="normal" font="default" size="100%">Adopting third-party software is becoming an economical and strategic need for today organizations. A fundamental part of its successful adoption is the informed selection of products that best fit the organization needs. One of the main current problems hampering selection, specially of OSS products is the vast amount of unstructured, incomplete, evolvable and widespread information about products that highly increases the risks of taking a wrong decision. In this paper, we aim to inform and provide evidence to OSS communities that help them to envisage improvements on their information rendering strategies to satisfy industrial OSS selectors’ needs. Our results are from the matching between the informational needs of 23 OSS selectors from diverse software-intensive organizations, and the in-depth study of 9 OSS communities of different sizes and domains. The results evidenced specific areas of improvement that might help to enhance the industrial OSS selection practice.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Seror, Ann</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Virtual Health Information Infrastructures: A Scalable Regional Model</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Systems: Grounding Research (OSS 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Bireme</style></keyword><keyword><style  face="normal" font="default" size="100%">Communities Of Practice</style></keyword><keyword><style  face="normal" font="default" size="100%">culture</style></keyword><keyword><style  face="normal" font="default" size="100%">open source systems</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual infrastructures</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">316-319</style></pages><abstract><style face="normal" font="default" size="100%">Integrating research, education and evidence-based medical practice requires complex infrastructures and network linkages among these critical activities. This research examines communities of practice and open source software tools in development of scalable virtual infrastructures for the regional Virtual Health Library of the Latin American and Caribbean Health Sciences System (Bireme) and embedded national cases. Virtual infrastructures refer to an environment characterized by overlapping distribution networks accessible through Internet portals and websites designed to facilitate integrated use of available resources. Case analysis shows engagement of interdisciplinary communities of practice for scalable virtual infrastructure design. This research program considers theory and methods for study of transferability of the Latin American model to large health care systems in other cultures.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Vieira, Miguel Said</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What kind of commons is free software?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 6th Open Knowledge Conference (OKCon 2011)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">commons</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">governance</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2011</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://ceur-ws.org/Vol-739/paper_10.pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/VIEIRA.pdf</style></url><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/VIEIRA_presentation_0.odp</style></url></related-urls></urls><pub-location><style face="normal" font="default" size="100%">Berlin, Germany</style></pub-location><abstract><style face="normal" font="default" size="100%">This paper analyzes free software under the light of commons theories, and tries to answer whether it is a managed or open access commons. It briefly presents commons studies and its main concepts, as well as the discussion on immaterial commons, arguing that goods' intrinsic characteristics should not be viewed as absolute, but rather contextualized in social struggles. Then, it proposes a two-tier structure for analyzing free software as a commons, considering its dual nature as source and machine code. The two connected layers of the proposal - use and development - are characterized according to commons theory categories; Android and software forking are explored as examples. It concludes that the first layer resembles an open access commons, but with intensional boundaries, and that the second one resembles multiple managed commons. This disparity is associated with the category of nested enterprises and with the layers' relations to appropriation and production.</style></abstract><notes><style face="normal" font="default" size="100%">Available under a CreativeCommons BY-NC-SA license (http://creativecommons.org/licenses/by-nc-sa/3.0/). The presentation slides are also attached; paper's LaTeX source files can be found at http://www.mediafire.com/?7k9dxbkna0x6irl</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Davies, Julius</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Apples vs. oranges?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">246-249</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">We attempt to compare the source code of two Java IDE systems: Netbeans and Eclipse. The result of this experiment shows that many factors, if ignored, could risk a bias in the results, and we posit various observations that should be taken into consideration to minimize such risk.

</style></abstract><notes><style face="normal" font="default" size="100%">&quot;In this MSR challenge report, we compare the source code of two in- dustrial grade Integrated Development Environments (IDE): Netbeans, developed by Oracle Corporation, and Eclipse, developed by the Eclipse Foundation. In the same spirit as [1], our goal is not to identify how similar or different they are, but to identify differences that, if not taken into consideration, might result in biased, and potentially erroneous conclusions.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mizuno, Osamu</style></author><author><style face="normal" font="default" size="100%">Hirata, Yukinao</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Do comments explain codes adequately?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">comments</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">242-245</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Comment lines in the software source code include descriptions of codes, usage of codes, copyrights, unused codes, comments, and so on. It is required for comments to explain the content of written code adequately, since the wrong description in the comment may causes further bug and confusion in maintenance.

In this paper, we try to clarify a research question: &quot;In which projects do comments describe the code adequately?&quot; To answer this question, we selected the group 1 of mining challenge and used data obtained from Eclipse and Netbeans. Since it is difficult to answer the above question directly, we define the distance between codes and comments. By utilizing the fault-prone module prediction technique, we can answer the alternative question from the data of two projects. The result shows that Eclipse project has relatively adequate comments.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tan, Lin</style></author><author><style face="normal" font="default" size="100%">Lam, Patrick</style></author><author><style face="normal" font="default" size="100%">Eyolfson, Jon</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Do time of day and developer experience affect commit bugginess</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">153-162</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Modern software is often developed over many years with hundreds of thousands of commits. Commit metadata is a rich source of social characteristics, including the commit's time of day and the experience and commit frequency of its author. The &quot;bugginess&quot; of a commit is also a critical property of that commit. In this paper, we investigate the correlation between a commit's social characteristics and its &quot;bugginess&quot;; such results can be very useful for software developers and software engineering researchers. For instance, developers or code reviewers might be well-advised to thoroughly verify commits that are more likely to be buggy. In this paper, we study the correlation between a commit's bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. We survey two widely-used open source projects: the Linux kernel and PostgreSQL.

Our main findings include: (1) commits submitted between midnight and 4 AM (referred to as late-night commits) are significantly buggier and commits between 7 AM and noon are less buggy, implying that developers may want to double-check their own latenight commits; (2) daily-committing developers produce less-buggy commits, indicating that we may want to promote the practice of daily-committing developers reviewing other developers' commits; and (3) the bugginess of commits versus day-of-week varies for different software projects.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we study the latest versions of the Linux kernel and PostgreSQL, which have 222,332 and 31,098 commits, respectively. We study the correlation between a commit’s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. In addition, we study several other commit characteristics, such as comment-only fixes and bug lifetimes.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mani, Senthil</style></author><author><style face="normal" font="default" size="100%">Sinha, Saurabh</style></author><author><style face="normal" font="default" size="100%">Sinha, Vibha Singhal</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Entering the circle of trust</style></title><secondary-title><style face="normal" font="default" size="100%">Proceeding of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">commits</style></keyword><keyword><style  face="normal" font="default" size="100%">committers</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">trust</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">133-142</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">The success of an open-source project depends to a large degree on the proactive and constructive participation by the developer community. An important role that developers play in a project is that of a code committer. However, code-commit privilege is typically restricted to the core group of a project. In this paper, we study the phenomenon of the induction of external developers as code committers. The trustworthiness of an external developer is one of the key factors that determines the granting of commit privileges. Therefore, we formulate different hypotheses to explain how the trust is established in practice. To investigate our hypotheses, we developed an automated approach based on mining code repositories and bug-tracking systems. We implemented the approach and performed an empirical study, using the Eclipse projects, to test the hypotheses. Our results indicate that, most frequently, developers establish trust and credibility in a project by contributing to the project in a non-committer role. Moreover, the employing organization of a developer is another factor--although a less significant one--that influences trust.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we started by analyzing 219 projects&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jason Tsay</style></author><author><style face="normal" font="default" size="100%">Wright, Hyrum</style></author><author><style face="normal" font="default" size="100%">Perry, Dewayne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Experiences Mining Open Source Release Histories</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Software and Systems Process (ICSSP 2011) </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">doap</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">life cycle</style></keyword><keyword><style  face="normal" font="default" size="100%">release engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword><keyword><style  face="normal" font="default" size="100%">release management</style></keyword><keyword><style  face="normal" font="default" size="100%">releases</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/icssp11short-p034-tsay.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">Software releases form a critical part of the life cycle of a software project. Typically, each project produces releases in its own way, using various methods of versioning, archiving, announcing and publishing the release. Understanding the release history of a software project can shed light on the project history, as well as the release process used by that project, and how those processes change. However, many factors make automating the retrieval of release history information difficult, such as the many sources of data, a lack of relevant standards and a disparity of tools used to create releases.

In spite of the large amount of raw data available, no attempt has been made to create a release history database of a large number of projects in the open source ecosystem. This paper presents our experiences, including the tools, techniques and pitfalls, in our early work to create a software release history database which will be of use to future researchers who want to study and model the release engineering process in greater depth.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;First, we selected the projects to initially target, using several criteria to get a broad picture of the open source landscape. Second, we collected the actual data, using a framework of parsers and some manual inspection. Third, we standardized and inserted the data into a database for later use.&quot;

&quot;but we plan to eventually cross reference our list of projects with existing open source project information (such as FLOSSmole) to take advantage of the work already done by other researchers.&quot;

&quot;For each release, we collected the following data: the project it belonged to, the date the release was published, the type of release, the release label (version number) and the source of the data&quot;

discussion of their difficulties

&quot;We conclude that programmatically creating a release history database from existing open source data is not trivial,&quot;

&quot;We have currently collected 1579 distinct releases from 22 different open source projects&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maalej, Walid</style></author><author><style face="normal" font="default" size="100%">Pagano, Dennis</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">How do developers blog?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">blog</style></keyword><keyword><style  face="normal" font="default" size="100%">communication</style></keyword><keyword><style  face="normal" font="default" size="100%">developer</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">LDA</style></keyword><keyword><style  face="normal" font="default" size="100%">postgres</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">123-132</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">We report on an exploratory study, which aims at understanding how software developers use social media compared to conventional development infrastructures. We analyzed the blogging and the committing behavior of 1,100 developers in four large open source communities. We observed that these communities intensively use blogs with one new entry about every 8 hours. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that most popular topics represent high-level concepts such as functional requirements and domain concepts. Source code related topics are covered in less than 15% of the posts. Our results also show that developers are more likely to blog after corrective engineering and management activities than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to further understand the role of social media in software engineering and integrate it into development processes and tools.</style></abstract><notes><style face="normal" font="default" size="100%">publishing frequency, post structure, word usage, publication patterns, content</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Murphy-Hill, Emerson</style></author><author><style face="normal" font="default" size="100%">Parnin, Chris</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Java generics adoption</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">commits</style></keyword><keyword><style  face="normal" font="default" size="100%">generics</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">3-12</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured whether generics actually provide such relief. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 20 popular open source Java programs, traversing more than 500 million lines of code in the process. We evaluate five hypotheses, each based on assertions made by prior researchers, about how Java developers use generics. For example, our results suggest that generics do not significantly reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we automatically analyzed 20 open source software projects. We analyzed the top “most used” projects according to ohloh.net, including only projects with significant amounts of Java code&quot;

&quot;The 20 selected projects were Ant, Azureus, CheckStyle, Commons Collections, Free- Mind, FindBugs, Jetty, JEdit, JDT, JUnit, Eclipse-cs, Hibernate, Log4j, Lucene, Maven, the Spring Frame- work, Squirrel-SQL, Subclipse, Weka, and Xerces.&quot;

&quot;In mining the full version histories of these 20 projects, we analyzed the full content of each version of each Java source file, a total of 548,982,841 lines.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cerulo, Luigi</style></author><author><style face="normal" font="default" size="100%">Cimitile, Marta</style></author><author><style face="normal" font="default" size="100%">Di Penta, Massimiliano</style></author><author><style face="normal" font="default" size="100%">Canfora, Gerardo</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Social interactions around cross-system bug fixings</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">committers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">openbsd</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">143-152</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Cross-system bug fixing propagation is frequent among systems having similar characteristics, using a common framework, or, in general, systems with cloned source code fragments. While previous studies showed that clones tend to be properly maintained within a single system, very little is known about cross-system bug management.

This paper describes an approach to mine explicitly documented cross-system bug fixings, and to relate their occurrences to social characteristics of contributors discussing through the project mailing lists--e.g., degree, betweenness, and brokerage--as well as to the contributors' activity on source code.

The paper reports results of an empirical study carried out on FreeBSD and OpenBSD kernels. The study shows that the phenomenon of cross-system bug fixing between these two projects occurs often, despite the limited overlap of contributors. The study also shows that cross-system bug fixings mainly involve contributors with the highest degree, betweenness and brokerage level, as well as contributors that change the source code more than others.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We rely on information stored in versioning database and mailing lists of both systems and develop methods to reconstruct and integrate different historical database&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gall, Harald</style></author><author><style face="normal" font="default" size="100%">Karus, Siim</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">A study of language usage evolution in open source software</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikiki, Honolulu, HI, USA</style></pub-location><pages><style face="normal" font="default" size="100%">13-22</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">The use of programming languages such as Java and C in Open Source Software (OSS) has been well studied. However, many other popular languages such as XSL or XML have received minor attention. In this paper, we discuss some trends in OSS development that we observed when considering multiple programming language evolution of OSS. Based on the revision data of 22 OSS projects, we tracked the evolution of language usage and other artefacts such as documentation files, binaries and graphics files. In these systems several different languages and artefact types including C/C++, Java, XML, XSL, Makefile, Groovy, HTML, Shell scripts, CSS, Graphics files, JavaScript, JSP, Ruby, Phyton, XQuery, OpenDocument files, PHP, etc. have been used. We found that the amount of code written in different languages differs substantially. Some of our findings can be summarized as follows: (1) JavaScript and CSS files most often co-evolve with XSL; (2) Most Java developers but only every second C/C++ developer work with XML; (3) and more generally, we observed a significant increase of usage of XML and XSL during recent years and found that Java or C are hardly ever the only language used by a developer. In fact, a developer works with more than 5 different artefact types (or 4 different languages) in a project on average.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Baik, Eilwoo</style></author><author><style face="normal" font="default" size="100%">Devanbu, Premkar</style></author><author><style face="normal" font="default" size="100%">Wang, Xinlei (Oscar)</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">System compatibility analysis of Eclipse and Netbeans based on bug data</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">ms challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">version history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikiki, Honolulu, HI, USANew York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">230-233</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Eclipse and Netbeans are two top of the line Integrated Development Environments (IDEs) for Java development. Both of them provide support for a wide variety of development tasks and have a large user base. This paper provides an analysis and comparison for the compatibility and stability of Eclipse and Netbeans on the three most commonly used operating systems, Windows, Linux and Mac OS. Both IDEs are programmed in Java and use a Bugzilla issue tracker to track reported bugs and feature requests. We looked into the Bugzilla repository databases of these two IDEs, which contains the bug records and histories of these two IDEs. We used some basic data mining techniques to analyze some historical statistics of the bug data. Based on the analysis, we try to answer certain stability-comparison oriented questions in the paper, so that users can have a better idea which of these two IDEs is designed better to work on different platforms.

</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Davis, Ian</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author><author><style face="normal" font="default" size="100%">Baysal, Olga</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">A tale of two browsers</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">chrome</style></keyword><keyword><style  face="normal" font="default" size="100%">development history</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">238-241</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">We explore the space of open source systems and their user communities by examining the development artifact histories of two popular web browsers -- Firefox and Chrome -- as well as usage data. By examining the data and addressing a number of research questions, two very different profiles emerge: Firefox, as the older and established system, with long product version cycles but short bug fix cycles, and a user base that is slow to adopt newer versions; and Chrome, as the new and fast evolving system, with short version cycles, longer bug fix cycles, and a user base that very quickly adopts new versions as they become available (due largely to Chrome's mandatory automatic updates).

</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Marschner, Eli</style></author><author><style face="normal" font="default" size="100%">Rosenfeld, Evan</style></author><author><style face="normal" font="default" size="100%">Heer, Jeffrey</style></author><author><style face="normal" font="default" size="100%">Heller, Brandon</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Visualizing collaboration and influence in the open-source software community</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">COLLABORATION</style></keyword><keyword><style  face="normal" font="default" size="100%">data exploration</style></keyword><keyword><style  face="normal" font="default" size="100%">geography</style></keyword><keyword><style  face="normal" font="default" size="100%">geoscatter</style></keyword><keyword><style  face="normal" font="default" size="100%">github</style></keyword><keyword><style  face="normal" font="default" size="100%">graph</style></keyword><keyword><style  face="normal" font="default" size="100%">mapping</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">social graph</style></keyword><keyword><style  face="normal" font="default" size="100%">user profiles</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">223-226</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">We apply visualization techniques to user profiles and repository metadata from the GitHub source code hosting service. Our motivation is to identify patterns within this development community that might otherwise remain obscured. Such patterns include the effect of geographic distance on developer relationships, social connectivity and influence among cities, and variation in project-specific contribution styles (e.g., centralized vs. distributed). Our analysis examines directed graphs in which nodes represent users' geographic locations and edges represent (a) follower relationships, (b) successive commits, or (c) contributions to the same project. We inspect this data using a set of visualization techniques: geo-scatter maps, small multiple displays, and matrix diagrams. Using these representations, and tools based on them, we develop hypotheses about the larger GitHub community that would be difficult to discern using traditional lists, tables, or descriptive statistics. These methods are not intended to provide conclusive answers; instead, they provide a way for researchers to explore the question space and communicate initial insights.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;This data set includes the complete social graph of 500,000 follow links as well as over 1,000,000 commits and 50,000 users.&quot;

&quot;...a large fraction of [GitHub] users provide a location in their profile, which we can turn into geographic coordinates using a geocoding API like PlaceFinder...

&quot;For each repository, we extract the owner, collaborator, and contributor usernames, plus branch names. New user- names help to find new repositories, while branch names are used to fetch commit metadata. Using this method, the crawler uncovered 40,860 code repositories, representing 33,388 unique project names and 1,219,872 individual commits.&quot;

&quot;In addition to crawled data, we use the complete GitHub user follower graph from Jan 19, 2011. This graph includes 452,248 links connecting 106,247 unique users, 47% (49,500) of which could be geocoded with the PlaceFinder API&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zagarese, Quirino</style></author><author><style face="normal" font="default" size="100%">Distante, Damiano</style></author><author><style face="normal" font="default" size="100%">Di Penta, Massimiliano</style></author><author><style face="normal" font="default" size="100%">Bernardi, Mario Luca</style></author><author><style face="normal" font="default" size="100%">Sementa, Carmine</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">van Deursen, Arie</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">What topics do Firefox and Chrome contributors discuss?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 8th working conference on Mining software repositories - MSR '11</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '11</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">chrome</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">LDA</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2011</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">234-237</style></pages><isbn><style face="normal" font="default" size="100%">9781450305747</style></isbn><abstract><style face="normal" font="default" size="100%">Firefox and Chrome are two very popular open source Web browsers, implemented in C/C++. This paper analyzes what topics were discussed in Firefox and Chrome bug reports over time. To this aim, we indexed the text contained in bug reports submitted each semester of the project history, and identified topics using Latent Dirichlet Allocation (LDA). Then, we investigated to what extent Firefox and Chrome developers/contributors discussed similar topics, either in different periods, or over the same period. Results indicate a non-negligible overlap of topics, mainly on issues related to page layouting, user interaction, and multimedia contents.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Are Developers Fixing Their Own Bugs?</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">23 - 42</style></pages><abstract><style face="normal" font="default" size="100%">The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue><notes><style face="normal" font="default" size="100%">&quot;The analysis is focused at the level of lines of code and it uses the information stored in the source code management system&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Raza, Arif</style></author><author><style face="normal" font="default" size="100%">Capretz, Luiz Fernando</style></author><author><style face="normal" font="default" size="100%">Ahmed, Faheem</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study of Open Source Software Usability</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">1 - 16</style></pages><abstract><style face="normal" font="default" size="100%">Recent years have seen a sharp increase in the use of open source projects by common novice users; Open Source Software (OSS) is thus no longer a reserved arena for software developers and computer gurus. Although user-centered designs are gaining popularity in OSS, usability is still not considered one of the prime objectives in many design scenarios. This paper analyzes industry users’ perception of usability factors, including understandability, learnability, operability, and attractiveness on OSS usability. The research model of this empirical study establishes the relationship between the key usability factors and OSS usability from industrial perspective. In order to conduct the study, a data set of 105 industry users is included. The results of the empirical investigation indicate the significance of the key factors for OSS usability.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ven, Kris</style></author><author><style face="normal" font="default" size="100%">De Bruyn, Peter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Factors Affecting the Development of Absorptive Capacity in the Adoption of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">adoption</style></keyword><keyword><style  face="normal" font="default" size="100%">government</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">17 - 38</style></pages><abstract><style face="normal" font="default" size="100%">Previous research has shown that the knowledge that is available to an organization is an important factor influencing the adoption of open source software (OSS). Hence, it is important that organizations develop their absorptive capacity in order to successfully adopt OSS. Absorptive capacity refers to the ability of an organization to acquire, assimilate, and exploit new knowledge. However, no study has specifically investigated how organizations can develop their absorptive capacity by acquiring knowledge about OSS. This paper addresses this gap in research by investigating the organizational knowledge assimilation process within the context of the adoption of OSS. Based on a case study conducted at the Flemish government, a framework that is grounded in literature and that illustrates which contextual factors influence the development of absorptive capacity in the context of the adoption of OSS was developed.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lakka, Spyridoula</style></author><author><style face="normal" font="default" size="100%">Stamati, Teta</style></author><author><style face="normal" font="default" size="100%">Michalakelis, Christos</style></author><author><style face="normal" font="default" size="100%">Martakos, Dracoulis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Ontology of the OSS Business Model</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">39 - 59</style></pages><abstract><style face="normal" font="default" size="100%">This study focuses on theory building providing a holistic conceptual framework that consists of an ontology based OSS business model and an OSS business model taxonomy. The study extends existing theory in OSS business models and corresponding taxonomies, based on the structured-case methodological approach. An exploratory study is conducted in two research cycles, for the identification, validation, and evaluation of the critical constructs of an OSS business model. Results reveal that OSS business models differ from traditional software business models, having specific features that affect the software value chain, the infrastructure, and the revenue model of an OSS oriented firm.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Morasca, Sandro</style></author><author><style face="normal" font="default" size="100%">Taibi, Davide</style></author><author><style face="normal" font="default" size="100%">Tosi, Davide</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OSS-TMM</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">testing</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">1 - 22</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test &amp; Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Syeed, M.M. Mahbubul</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author><author><style face="normal" font="default" size="100%">Systä, Tarja</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Tool Assisted Analysis of Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">artifacts</style></keyword><keyword><style  face="normal" font="default" size="100%">tools</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><volume><style face="normal" font="default" size="100%">3</style></volume><pages><style face="normal" font="default" size="100%">43 - 78</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Krein, Jonathan L.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author><author><style face="normal" font="default" size="100%">Eggett, Dennis L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Impact of Programming Language Fragmentation on Developer Productivity</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">commits</style></keyword><keyword><style  face="normal" font="default" size="100%">entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">language entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">programming languages</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">32/2010</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">41 - 61</style></pages><abstract><style face="normal" font="default" size="100%">Programmers often develop software in multiple languages. In an effort to study the effects of programming language fragmentation on productivity—and ultimately on a developer’s problem-solving abilities—the authors present a metric, language entropy, for characterizing the distribution of a developer’s programming efforts across multiple programming languages. This paper presents an observational study examining the project contributions of a random sample of 500 SourceForge developers. Using a random coefficients model, the authors find a statistically (alpha level of 0.001) and practically significant correlation between language entropy and the size of monthly project contributions. Results indicate that programming language fragmentation is negatively related to the total amount of code contributed by developers within SourceForge, an open source software (OSS) community.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Valentin Vlasceanu</style></author><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Quang Vu Dang</style></author><author><style face="normal" font="default" size="100%">Lauriere, Stéphane</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Weaving a Semantic Web Across OSS Repositories</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">archive</style></keyword><keyword><style  face="normal" font="default" size="100%">bug</style></keyword><keyword><style  face="normal" font="default" size="100%">bugtracker</style></keyword><keyword><style  face="normal" font="default" size="100%">database</style></keyword><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">interoperability</style></keyword><keyword><style  face="normal" font="default" size="100%">ontology</style></keyword><keyword><style  face="normal" font="default" size="100%">OSLC-CM</style></keyword><keyword><style  face="normal" font="default" size="100%">RDF</style></keyword><keyword><style  face="normal" font="default" size="100%">repository of repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic Web</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">32/2010</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">29 - 40</style></pages><abstract><style face="normal" font="default" size="100%">Several public repositories and archives of “facts” about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reclassifying Success and Tragedy in FLOSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the International Conference on Open Source Systems (OSS)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">31 May–2 June</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Notre Dame, IN, USA</style></pub-location><abstract><style face="normal" font="default" size="100%">This paper presents the results of a replication of English &amp; Schweik’s 2007 paper classifying FLOSS projects according to their stage of growth and indicators of success. We recreated the analysis using a comparable data set from 2006, with one additional point in time. We also expanded upon the original results by applying different criteria for evaluating the rate of new software releases for sustainability of project activity. We discuss the points of convergence and divergence from the original work from these extensions of the classification, and their implications for studying FLOSS development using archival data. The paper contributes new analysis of operationalizing success in FLOSS projects, with discussion of implications of the findings.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Olson, Jamie F</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Carley, Kathleen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Paying attention to each other in visible work communities: Modeling bursty systems of multiple activity streams</style></title><secondary-title><style face="normal" font="default" size="100%">SocialCom/PASSAT(2010)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2010</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/olson2010paying-attentio.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">276-281</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Online work projects, from open source to wikipedia, have emerged as an important phenomenon. These communities offer exciting opportunities to investigate social processes because they leave traces of their activity over time. Unlike traditional work teams, the participants in these communities are widely dispersed and work without centralized management. The question arises, then, as to the extent to which these are in fact communities: is the group simply the sum of the individuals that make it up, or does the group function as a social unit? We explore this question in the temporal domain.
We argue that the rapid visibility of others’ work afforded by the information systems used by these projects reaches out and attracts the attention of others who are peripherally aware of the group’s online space, prompting them to begin or intensify their participation, binding separate individual streams of activity into a social entity.

Previous work has suggested that for certain types of bursty social behavior (e.g. email), the frequency of the behavior is not homogeneously distributed but rather can be divided into two generative mechanisms: active sessions and passive background participation. We extend this work for the case of multiple conditionally independent streams of behavior, where each stream is generated by these two generative mechanisms. Our model can characterized by a double-chain hidden Markov model, allowing efficient inference using expectation-maximization. We apply this model to visible work communities by modeling each participant as a single stream of behavior, assessing transition probabilities between active sessions of different participants. This allows us to examine the extent to which the various members of the community are influenced by the active participation of others. Our results indicate that an active session by a participant at least triples the likelihood of another participant beginning an active session.</style></abstract><notes><style face="normal" font="default" size="100%">Uses open source projects to study, but this is not about open source, per se.</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Beyond replication: An example of the potential benefits of replicability in the mining of software repositories community</style></title><secondary-title><style face="normal" font="default" size="100%">1st Workshop on Replication in Empirical Software Engineering Research</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">literature review</style></keyword><keyword><style  face="normal" font="default" size="100%">msr</style></keyword><keyword><style  face="normal" font="default" size="100%">replication</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2010</style></date></pub-dates></dates></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gamalielsson, Jonas</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Lings, Brian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Responsiveness as a measure for assessing the health of OSS ecosystems</style></title><secondary-title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">gmane</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">nagios</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2010</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/osscomm002.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">The health of an Open Source ecosystem is an important decision factor when considering the adoption of Open Source software or when monitoring a seeded Open Source project. In this paper we introduce responsiveness as a qualitative measure of the quality of replies within mailing lists, which can be used for assessing ecosystem health. We consider one specific metric of responsiveness in this paper, and that is the response time of follow-up messages in mailing lists. We also describe a way for characterising the nature of communication in messages with short and long response times. The approach is tested in the context of the Nagios project, and we particularly focus on the responsiveness for contributors acting in their professional roles as core developers. Our contribution is a step towards a deeper understanding of voluntary support provided in mailing lists of OSS projects.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Data was collected from the GMANE (gmane.org) archives of the SourceForge “Nagios-devel” mailing list for the period from January 2004 to October 2009&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schweik, C. M.</style></author><author><style face="normal" font="default" size="100%">English, R.</style></author><author><style face="normal" font="default" size="100%">Paienjton, Q.</style></author><author><style face="normal" font="default" size="100%">Haire, S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Success and Abandonment in Open Source Commons: Selected Findings from an Empirical Study of Sourceforge.net Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">abandonment</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">project failure</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">time</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2010</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/osscomm003.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">Some open source software collaborations are sustained over long periods of time and across several versions of a software product, while others become abandoned even before the first version of the product has been developed. In this study, we identify factors that might be responsible for one or the other of these collaborative trajectories. We examine 107,747 open source software projects hosted on Sourceforge.net in August 2006 using data available through the FLOSSmole Project. We employ Classification and Regression Tree modeling and Random Forests statistical approaches to begin to establish an understanding of how various project attributes, especially physical and community ones, contribute to project success or abandonment. We find that factors associated with success and abandonment differ for projects in the early stage of development (pre-first release) compared to projects that have had a first release, and that product utility, project vision, leadership, and group-size are associated with success in open source collaborations. We also find that successful open source projects exist across all types of software and not simply in areas associated with the open source “movement.” Other evidence suggests that Sourceforge.net may play an important role in “intellectual match-making.”</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we utilize data collected from August through October 2006 on 107,747 OSS projects hosted on the open source hosting site Sourceforge.net (SF henceforth). We combined SF project data gathered by the FLOSSmole project (Howison et al., 2006) with other SF data we “crawled” ourselves&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oliver Alexy</style></author><author><style face="normal" font="default" size="100%">Martin Leitner</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Fistful of Dollars: Financial Rewards, Payment Norms, and Motivation Crowding in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">SSRN</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">experiment</style></keyword><keyword><style  face="normal" font="default" size="100%">financial</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/2010</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ssrn</style></publisher><pub-location><style face="normal" font="default" size="100%">ssrn</style></pub-location><abstract><style face="normal" font="default" size="100%">Existing literature on open source software (OSS) maintains that intrinsic motivation and extrinsic financial rewards have a unidimensionally positive effect on the motivation of individual developers. Based on self-determination theory, which underlies most of these studies, we challenge this assumption. We argue that the effect of payment on both intrinsic motivation and total motivation of OSS developers is far more complex. To illustrate our point, we introduce the concept of individuals’ norms about payment to the field of OSS. In doing so, we are able to show that payment norms moderate the effect of payment on intrinsic motivation and total motivation. Conducting a scenario experiment, we find that intrinsic motivation decreases for individuals with norms against payment. This effect becomes even stronger when analyzing for mediation effects. Total motivation is impacted positively by payment, but the effect turns insignificant for individuals with norms for payment. Our findings help explain the results of previous studies in which OSS developers did not seem to be affected by motivation crowding. They further contribute to the more general debate on how to manage individuals in the absence of formal contracts. From a practical perspective, we show that financial rewards may create a management dilemma for OSS project leaders. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Panciera, K.</style></author><author><style face="normal" font="default" size="100%">Priedhorsky, R.</style></author><author><style face="normal" font="default" size="100%">Erickson, T.</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Lurking? Cyclopaths? A Quantitative Lifecyle Analysis of User Behavior in a Geowiki</style></title><secondary-title><style face="normal" font="default" size="100%">ACM Conference on Computer-Human Interaction (CHI)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">content,</style></keyword><keyword><style  face="normal" font="default" size="100%">geographic</style></keyword><keyword><style  face="normal" font="default" size="100%">geowiki,</style></keyword><keyword><style  face="normal" font="default" size="100%">information,</style></keyword><keyword><style  face="normal" font="default" size="100%">lurking</style></keyword><keyword><style  face="normal" font="default" size="100%">open</style></keyword><keyword><style  face="normal" font="default" size="100%">volunteer</style></keyword><keyword><style  face="normal" font="default" size="100%">volunteered</style></keyword><keyword><style  face="normal" font="default" size="100%">Wiki,</style></keyword><keyword><style  face="normal" font="default" size="100%">work,</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/2010</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Association for Computing Machinery</style></publisher><pub-location><style face="normal" font="default" size="100%">Atlanta, GA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hissam, S. A.</style></author><author><style face="normal" font="default" size="100%">Weinstock, C.</style></author><author><style face="normal" font="default" size="100%">Bass, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On Open and Collaborative Software Development in the DoD</style></title><secondary-title><style face="normal" font="default" size="100%">Seventh Annual Acquisition Research Symposium, {NPS} Proceedings -</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">collaborative development</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">reuse</style></keyword><keyword><style  face="normal" font="default" size="100%">software engineering</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/2010</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.acquisitionresearch.net/cms/_files/FY2010/NPS-AM-10-037.pdf</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><publisher><style face="normal" font="default" size="100%">Naval Postgraduate School</style></publisher><pub-location><style face="normal" font="default" size="100%">Monterey, California</style></pub-location><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">219–235</style></pages><abstract><style face="normal" font="default" size="100%">The US Department of Defense (specifically, but not limited to, the DoD CIO's Clarifying Guidance Regarding Open Source Software, DISA's launch of Forge.mil and OSD's Open Technology Development Roadmap Plan) has called for increased use of open source software and the adoption of best practices from the free/open source software (F/OSS) community to foster greater reuse and innovation between programs in the DoD. In our paper, we examine some key aspects of open and collaborative software development inspired by the success of the F/OSS movement as it might manifest itself within the US DoD. This examination is made from two perspectives: the reuse potential among DoD programs sharing software and the incentives, strategies and policies that will be required to foster a culture of collaboration needed to achieve the benefits indicative of F/OSS. Our conclusion is that to achieve predictable and expected reuse, not only are technical infrastructures needed, but also a shift to the business practices in the software development and delivery pattern seen in the traditional acquisition lifecycle is needed. Thus, there is potential to overcome the challenges discussed within this paper to engender a culture of openness and community collaboration to support the DoD mission.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Squire, Megan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Repositories with Public Data about Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/2010</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/ijossp2010.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">1 - 13</style></pages><abstract><style face="normal" font="default" size="100%">Empirical research on software development based on data obtained from project repositories and code forges is increasingly gaining attention in the software engineering research community. The studies in this area typically start by retrieving or monitoring some subset of data found in the repository or forge, and this data is later analyzed to find interesting patterns. However, retrieving information from these locations can be a challenging task. Meta-repositories providing public information about software development are useful tools that can simplify and streamline the research process. Public data repositories that collect and clean the data from other project repositories or code forges can help ensure that research studies are based on good quality data. This paper provides some insight as to how these meta-repositories (sometimes called a “repository of repositories”, RoR) of data about open source projects should be used to help researchers. This paper describes in detail two of the most widely used collections of data about software development: FLOSSmole and FLOSSMetrics.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rentocchini, Francesco</style></author><author><style face="normal" font="default" size="100%">Tartari, Dimitri</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Analysis of the Adoption of Open Source Software by Local Public Administrations</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">government</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">1 - 29</style></pages><abstract><style face="normal" font="default" size="100%">The wide diffusion of open source software (OSS) is driving discussion among scholars on a set of issues, including its adoption by public administrations (PA). Previous works discussed a few factors that drive the decision to adopt OSS and did not address the potential benefits in terms of e-government that OSS may bring to PA. This paper fills these gaps. The analysis is based on the Emilia-Romagna region of Italy and studies the adoption of software (both proprietary and open source) by local PA. The results show there is increased adoption of OSS in several different domains of application, both servers and desktop clients. Among the motivations to adopt OSS, dependence on software suppliers is important. Its adoption also positively affects the variety and extent of interactivity of local public e-services.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analyzing Leadership Dynamics in Distributed Group Communication</style></title><secondary-title><style face="normal" font="default" size="100%">2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">DYNAMICS</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">fire</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">leadership</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-06-02.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-5509-6</style></isbn><abstract><style face="normal" font="default" size="100%">We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Our analysis examines the communication patterns in two FLOSS development projects, Fire and Gaim&quot;
&quot;These data were imported into a database to allow automated analysis. The Fire data set includes about 1,800 events in the user email list, 7,800 messages in the developer venues, and 1,300 events in the combined trackers, spanning a period of 54 months. The signiﬁcantly larger Gaim data set included over 41,000 events in the user forum, over 30,000 events in the developer venues, and about 20,000 events in the trackers, generated over 78 months.&quot;
&quot;The dynamic network analysis was performed using a scientiﬁc workﬂow tool, Taverna Workbench&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Luijten, Bart</style></author><author><style face="normal" font="default" size="100%">Visser, Joost</style></author><author><style face="normal" font="default" size="100%">Zaidman, Andy</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assessment of issue handling efficiency</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/94bluijtenMSR2010.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">94 - 97</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">We mined the issue database of GNOME to assess how issues are handled. How many issues are submitted and resolved? Does the backlog grow or decrease? How fast are issues resolved? Does issue resolution speed increase or decrease over time? In which subproject are issues handled most efficiently? To answer such questions, we apply several visualization and quantification instruments to the raw issue data. In particular, we aggregate issues into four risk categories, based on their resolution time. These categories are the basis both for visualizing and ranking, which are used in concert for issue database exploration.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ossher, Joel</style></author><author><style face="normal" font="default" size="100%">Bajracharya, Sushil</style></author><author><style face="normal" font="default" size="100%">Lopes, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Automated dependency resolution for open source software</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">dependencies</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourcerer</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">130 - 140</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Opportunities for software reuse are plentiful, thanks in large part to the widespread adoption of open source processes and the availability of search engines for locating relevant artifacts. One challenge presented by open source software reuse is simply getting a newly downloaded artifact to build/run in the first place. The artifact itself likely reuses other artifacts, and so depends on their being located to function properly. While merely tedious in the individual case, this can cause serious difficulties for those seeking to study open source software. It is simply not feasible to manually resolve dependencies for thousands of projects, and many forms of analysis require declarative completeness. In this paper we present a method for automatically resolving dependencies for open source software. It works by cross-referencing a project's missing type information with a repository of candidate artifacts. We have implemented this method on top of the Sourcerer, an infrastructure for the large-scale indexing and analysis of open source code. The performance of our resolution algorithm was evaluated in two parts. First, for a small number of popular open source projects, we manually examined the artifacts suggested by our system to determine if they were appropriate. Second, we applied the algorithm to the 13,241 projects in the Sourcerer managed repository to evaluate the rate of resolution success. The results demonstrate the feasibility of this approach, as the algorithm located all of the required artifacts needed by 3,904 additional projects, increasing the percentage of declaratively complete projects in Sourcerer from 39% to 69%.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maalej, Walid</style></author><author><style face="normal" font="default" size="100%">Happel, Hans-Jorg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Can development work describe itself?</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developer interactions</style></keyword><keyword><style  face="normal" font="default" size="100%">work descriptions</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">191 - 200</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">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' interactions. Our findings have many implications for next generation software engineering tools.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rahman, Foyzur</style></author><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Devanbu, Premkumar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Clones: What is that smell?</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fix revisions</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">gimp</style></keyword><keyword><style  face="normal" font="default" size="100%">nautilus</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/72rahman2010cws.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">72 - 81</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">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 &quot;bad smell&quot;. Perhaps we can clone, and breathe easy, at the same time.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Krinke, Jens</style></author><author><style face="normal" font="default" size="100%">Gold, Nicolas</style></author><author><style face="normal" font="default" size="100%">Jia, Yue</style></author><author><style face="normal" font="default" size="100%">Binkley, David</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Cloning and copying between GNOME projects</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/98Coning.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">98 - 101</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">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'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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Finkelstein, A.</style></author><author><style face="normal" font="default" size="100%">van der Hoek, A.</style></author><author><style face="normal" font="default" size="100%">Grundy, J.</style></author><author><style face="normal" font="default" size="100%">Mistrík, I.</style></author><author><style face="normal" font="default" size="100%">Whitehead, J.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaboration Practices and Affordances in Free/Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">Collaborative Software Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CoSE-Scacchi-Chapter.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">307-328</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bougie, Gargi</style></author><author><style face="normal" font="default" size="100%">Treude, Christoph</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Storey, Margaret-Anne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A comparative exploration of FreeBSD bug lifetimes</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/106ChallengeGargi.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">106 - 109</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">McGrath, Owen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Data Mining User Activity in Free and Open Source Software (FOSS)/ Open Learning Management Systems</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">data mining</style></keyword><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">student</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">65 - 75</style></pages><abstract><style face="normal" font="default" size="100%">Free and Open Source Software (FOSS)/Open Educational Systems development projects abound in higher education today. Many universities worldwide have adopted open source software like ATutor and Moodle as an alternative to commercial or homegrown systems. The move to open source learning management systems entails many special considerations, including usage analysis facilities. The tracking of users and their activities poses major technical and analytical challenges within web-based systems. This paper examines how user activity tracking challenges are met with data mining techniques, particularly web usage mining methods, in four different open learning management systems: ATutor, LON-CAPA, Moodle, and Sakai. As examples of data mining technologies adapted within widely used systems, they represent important first steps for moving educational data mining outside the research laboratory. Moreover, as examples of different open source development contexts, exemplify the potential for programmatic integration of data mining technology processes in the future. As open systems mature in the use of educational data mining, they move closer to the long-sought goal of achieving more interactive, personalized, adaptive learning environments online on a broad scale.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Buchan, Janet</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Developing a Dynamic and Responsive Online Learning Environment</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">learning</style></keyword><keyword><style  face="normal" font="default" size="100%">sakai</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">32 - 48</style></pages><abstract><style face="normal" font="default" size="100%">Charles Stuart University adopted the open source software, Sakai, as the foundation for the university’s new, integrated Online Learning Environment. This study explores whether a pedagogical advantage exists in adopting such an open source learning management system. Research suggests that the community source approach to development of open source software has many inherent pedagogical advantages, but this paper examines whether this is due to the choice of open source software or simply having access to appropriate technology for learning and teaching in the 21st century. The author also addresses the challenges of the project management methodology and processes in the large-scale implementation of an open-source courseware management solution at the institutional level. Consequently, this study outlines strategies that an institution can use to harness the potential of a community source approach to software development to meet the institutional and individual user needs into the future. </style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schroter, Adrian</style></author><author><style face="normal" font="default" size="100%">Schröter, Adrian</style></author><author><style face="normal" font="default" size="100%">Bettenburg, Nicolas</style></author><author><style face="normal" font="default" size="100%">Premraj, Rahul</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Do stack traces help developers fix bugs?</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug report</style></keyword><keyword><style  face="normal" font="default" size="100%">debugging</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">stack trace</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/118-10-msr.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">118 - 121</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">A widely shared belief in the software engineering community is that stack traces are much sought after by developers to support them in debugging. But limited empirical evidence is available to confirm the value of stack traces to developers. In this paper, we seek to provide such evidence by conducting an empirical study on the usage of stack traces by developers from the ECLIPSE project. Our results provide strong evidence to this effect and also throws light on some of the patterns in bug fixing using stack traces. We expect the findings of our study to further emphasize the importance of adding stack traces to bug reports and that in the future, software vendors will provide more support in their products to help general users make such information available when filing bug reports.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Ågerfalk, Pär</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús</style></author><author><style face="normal" font="default" size="100%">Madey, Gregory</style></author><author><style face="normal" font="default" size="100%">Noll, John</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Software: New Horizons</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">oss2010</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1007/978-3-642-13244-5_20</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer Boston</style></publisher><volume><style face="normal" font="default" size="100%">319</style></volume><pages><style face="normal" font="default" size="100%">252-267</style></pages><abstract><style face="normal" font="default" size="100%">Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge's history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.</style></abstract><notes><style face="normal" font="default" size="100%">10.1007/978-3-642-13244-5_20</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">McIntosh, Shane</style></author><author><style face="normal" font="default" size="100%">Adams, Bram</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The evolution of ANT build systems</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">ant</style></keyword><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">build</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">jboss</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">tomcat</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">42 - 51</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Darcy, David P.</style></author><author><style face="normal" font="default" size="100%">Daniel, Sherae L.</style></author><author><style face="normal" font="default" size="100%">Stewart, Katherine J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Exploring Complexity in Open Source Software: Evolutionary Patterns, Antecedents, and Outcomes</style></title><secondary-title><style face="normal" font="default" size="100%">2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">fda</style></keyword><keyword><style  face="normal" font="default" size="100%">life cycle</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/10-07-02.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 11</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-5509-6</style></isbn><abstract><style face="normal" font="default" size="100%">Software complexity is important to researchers and managers, yet much is unknown about how complexity evolves over the life of a software application and whether different dimensions of software complexity may exhibit similar or different evolutionary patterns. Using cross-sectional and longitudinal data on a sample of 108 open source projects, this research investigated how the complexity of open source project releases varied throughout the life of the project. Functional data analysis was applied to the release histories of the projects and recurring evolutionary patterns were derived. There were projects that saw little evolution, according to their measures of size and structural complexity. However, projects that displayed some evolution often differed on the pattern of evolution depending on whether size or structural complexity was examined. Factors that contribute to and result from the patterns of complexity were evaluated, and implications for research and practice are presented.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;The sample of projects was drawn from SourceForge&quot;
&quot;projects were selected that were built with C++.&quot;
&quot;Applying the selection criteria generated a total of 108 projects for analysis&quot;
&quot;Scientific Toolwork’s Understand (version 1.4)&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">D'Ambros, Marco</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Robbes, Romain</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An extensive comparison of bug prediction approaches</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">famix</style></keyword><keyword><style  face="normal" font="default" size="100%">lucene</style></keyword><keyword><style  face="normal" font="default" size="100%">mylyn</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/31dambrosLanzaRobbes31.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">31 - 41</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Reliably predicting software defects is one of software engineering's holy grails. Researchers have devised and implemented a plethora of bug prediction approaches varying in terms of accuracy, complexity and the input data they require. However, the absence of an established benchmark makes it hard, if not impossible, to compare approaches. We present a benchmark for defect prediction, in the form of a publicly available data set consisting of several software systems, and provide an extensive comparison of the explanative and predictive power of well-known bug prediction approaches, together with novel approaches we devised. Based on the results, we discuss the performance and stability of the approaches with respect to our benchmark and deduce a number of insights on bug prediction models.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sasaki, Yusuke</style></author><author><style face="normal" font="default" size="100%">Yamamoto, Tetsuo</style></author><author><style face="normal" font="default" size="100%">Hayase, Yasuhiro</style></author><author><style face="normal" font="default" size="100%">Inoue, Katsuro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Finding file clones in FreeBSD Ports Collection</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/102FreeBSDClones.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">102 - 105</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">In Open Source System (OSS) development, software components are often imported and reused; for this reason we might expect that files are copied in multiple projects (file clones). In this paper, we propose a file clone detection tool called FCFinder and show the analysis performed with it on the FreeBSD Ports Collection, a large OSS project collection. We found many file clones among similar or related projects, which are systematically introduced from base projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sirkkala, Petri</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From Proprietary to Open Source: Building a Network of Trust</style></title><secondary-title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">oss2010</style></keyword><keyword><style  face="normal" font="default" size="100%">osscomm</style></keyword><keyword><style  face="normal" font="default" size="100%">workshop</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/osscomm001.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">When a corporation is about to release a product as open source a large network of trust must be built and maintained. Open source and commercial domains have radically different aspects of trust. Still, trust is vital in products survival in both settings. This paper focuses on building cognitive, or rational, trust in both commercial and open source domains. We set the view angle so that trust can be approached via the various relationships between the stakeholders involved in the community building process. Towards this goal, the paper focuses on the first steps of the process by proposing a set of best practices.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Caudill, Jason G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Helping to Bridge the Digital Divide with Free Software and Services</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">13 - 27</style></pages><abstract><style face="normal" font="default" size="100%">The growing importance of digital media in citizens’ participation in government is a major issue in obtaining government services, elections and campaigning in the 21st century. In order to participate in the consumption and creation of online media, citizens must have access to, and knowledge of, appropriate technology resources. There exists a gap between those who have access to technology and those who do not A gap commonly referred to as the digital divide. While there are many different aspects to the digital divide one of them is access to the software necessary to participate in digital media. A potential solution to the software component of the digital divide is the use of open source software and free online services. Implementing these solutions can play a part in narrowing the digital divide and producing better informed citizens more capable of participating in the modern electoral process.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Williams van Rooij, Shahron</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Higher Education and FOSS for e-Learning</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">education</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">15 - 31</style></pages><abstract><style face="normal" font="default" size="100%">This paper examines the paradox of FOSS adoption in U.S. institutions of higher education, where campus-wide deployment of FOSS for e-learning lags far behind adoption for technical infrastructure applications. Drawing on the fields of organizational management, information systems, and education, the author argues that the gap between FOSS advocacy and the enterprise-wide deployment of FOSS for e-learning is a consequence of the divergent perspectives of two organizational sub-cultures—the technologist and the academic—and the extent to which those sub-cultures are likely to embrace FOSS. The author recommends (a) collaborative needs analysis/assessment prior to a go/no go adoption decision, and (b) broad dissemination of total cost of ownership (TCO) data by institutions deploying FOSS for e-learning enterprise-wide. This discussion satisfies e-learning administrators and practitioners seeking research-based, cross-disciplinary evidence about the FOSS decision-making process and also assists educators seeking to expand student knowledge of e-learning technology options. </style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Di Penta, Massimiliano</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Antoniol, Giuliano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying licensing of jar archives using a code-search approach</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bytecode</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">google code</style></keyword><keyword><style  face="normal" font="default" size="100%">jar</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">licenses</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/151msr2010.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">151 - 160</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Free and open source software strongly promotes the reuse of source code. Some open source Java components/libraries are distributed as jar archives only containing the bytecode and some additional information. For whoever wanting to integrate this jar in her own project, it is important to determine the license(s) of the code from which the jar archive was produced, as this affects the way that such component can be used. This paper proposes an automatic approach to determine the license of jar archives, combining the use of a code-search engine with the automatic classification of licenses contained in textual flies enclosed in the jar. Results of an empirical study performed on 37 jars - from 17 different systems - indicate that this approach is able to successfully infer the jar licenses in over 95% of the cases, but that in many cases the license in textual flies may differ from the one of the classes contained in the jar.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matthew Van Antwerp</style></author><author><style face="normal" font="default" size="100%">Madey, Greg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Importance of Social Network Structure in the Open Source Software Developer Community</style></title><secondary-title><style face="normal" font="default" size="100%">2010 43rd Hawaii International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-06-07.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-5509-6</style></isbn><abstract><style face="normal" font="default" size="100%">This paper outlines the motivations and methods for analyzing the developer network of open source software (OSS) projects. Previous work done by Hinds [5] suggested social network structure was instrumental towards the success of an OSS project, as measured by activity and output. The follow-up paper by Hinds [4] discovered that his hypotheses, based on social network theory and previous research on the importance of subgroup connectedness, were vastly different than the results of his study of over 100 successful OSS projects. He concluded that the social network structure had no significant effect on project success. We outline how his approach disregarded potentially important factors and through a new study evaluate the role of the OSS developer network as it pertains to long-term project popularity. We also present an initial investigation into the adequacy of using the SourceForge activity percentile as a long-term success metric. In contrast with Hinds, we show that previously existing developer-developer ties are an indicator of past and future project popularity.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Using data from the SourceForge Research Data Archive [2, 9] and the new dataset of concurrent versions system (CVS) metadata described in [8]...&quot; (M. Van Antwerp. Studying open source versioning metadata. Master’s thesis, University of NotreDame, Notre Dame, IN, January 2009)
&quot;To measure long-term popularity, we used the SourceForge activity percentile.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yuri Takhteyev</style></author><author><style face="normal" font="default" size="100%">Andrew Hilts</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Investigating the Geography of Open Source Software through Github</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Takhteyev-Hilts-2010.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">The paper presents an empirical study of the geography of open source software development that looks at Github, a popular project hosting website. We show that developers are highly clustered and concentrated primarily in North America and Western and Northern Europe, though a substantial minority is present in other regions. Code contributions and attention show a strong local bias. Users in North America account for a larger share of received contributions than of contributions made. They also receive a disproportionate amount of attention.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We collected our data through Github’s public API, which offers the same data as available on the Github’s website but presents it in a structured format for simpler processing. The data were collected from May to July of 2010&quot;

&quot;The data collection followed a recursive procedure. We started with a single account, belonging to one of Github’s founders. We then identified accounts connected to this user, then looked for accounts connected to the newly found ones, repeating this procedure until we achieved closure. New accounts were identified through the four kinds of connections mentioned in the previous section: (1) those that follow accounts collected earlier, (2) those followed by the accounts collected earlier, (3) those whose repositories were being “watched” by accounts collected earlier, (4) those who had made code contributions to the repositories watched by accounts collected earlier.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maha Shaikh</style></author><author><style face="normal" font="default" size="100%">Cornford, Tony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">'Letting go of Control' to Embrace Open Source: Implications for Company and Community</style></title><secondary-title><style face="normal" font="default" size="100%">2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">adoption</style></keyword><keyword><style  face="normal" font="default" size="100%">companies</style></keyword><keyword><style  face="normal" font="default" size="100%">interviews</style></keyword><keyword><style  face="normal" font="default" size="100%">organizations</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-06-01.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-5509-6</style></isbn><abstract><style face="normal" font="default" size="100%">It is increasingly understood across the information technology and services sector that engagement with the open source software model can serve as a means for firms to capture intellectual energy, learn about productive software processes, access relevant technical skills, identify and recruit staff, as well as obtain valuable resources including code. This paper reports a study undertaken within two large global IT companies that have been actively involved with open source for more than ten years. The study involved over 30 semi-structured interviews with employees of the companies drawn from top, middle, and lower level management, and included active and experienced developer as well as open source community members. Our findings indicate how these companies have adapted their day-to-day management practices to take into account the need for flexibility and freedom expected by open source communities. This paper focuses on how they 'let go of control' and what the implications of this are for both companies and the communities involved. Our data reveals a number of themes and in this paper we focus on three principal ones; issues of requirements, total cost of adoption, and alignment of open source engagement with long term company strategy.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Guido Conaldi</style></author><author><style face="normal" font="default" size="100%">Tonellato, Marco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Longitudinal Study on Collaboration Networks and Decision to Participate in a FLOSS Community</style></title><secondary-title><style face="normal" font="default" size="100%">5th Workshop on Public Data about Software Development (WoPDaSD 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bicho</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">COLLABORATION</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">epiphany</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmetrics</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/wopdasd002.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">In this paper we conjecture that individual decisions of FLOSS (Free/Libre Open Source Software) developers to take on a task are influenced by network relations generated by collaboration among project members. In order to explore our conjecture we collected data on a FLOSS project team consisting of 227 developers committed since 2002 to the development of a web browser. We reconstructed 2-mode co- collaboration networks (software developer by bug) in which a tie represents an action taken by a developer in order to solve a specific bug. Co-collaboration networks were collected at five points in time during a six-month development cycle of the software. We report and discuss results of longitudinal actor-based modeling that we specify to test for the influence of local network structures on developer’s decision to take action on a specific bug. The study controls for bug-specific and developer-specific characteristics that may also affect developers’ decisions exogenously. We also control for priority and severity levels assigned by the team to bugs in an attempt to manage voluntary contribution.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we chose as a case of study Epiphany, which is the default web browser of the GNOME graphical desktop environment&quot;

&quot;We collected all relevant data by parsing all the bug reports in GNOME Bugzilla repository relative to Epiphany. The data collection and storing was done using Bicho (v. 0.4 rev. 7198), a software part of the FLOSSMetric project [14].&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mauczka, Andreas</style></author><author><style face="normal" font="default" size="100%">Schanes, Christian</style></author><author><style face="normal" font="default" size="100%">Fankhauser, Florian</style></author><author><style face="normal" font="default" size="100%">Bernhart, Mario</style></author><author><style face="normal" font="default" size="100%">Grechenig, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining security changes in FreeBSD</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">security</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">90 - 93</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Current research on historical project data is rarely touching on the subject of security related information. Learning how security is treated in projects and which parts of a software are historically security relevant or prone to security changes can enhance the security strategy of a software project. We present a mining methodology for security related changes by modifying an existing method of software repository analysis. We use the gathered security changes to find out more about the nature of security in the FreeBSD project and we try to establish a link between the identified security changes and a tracker for security issues (security advisories). We give insights how security is presented in the FreeBSD project and show how the mined data and known security problems are connected.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bruch, Marcel</style></author><author><style face="normal" font="default" size="100%">Mezini, Mira</style></author><author><style face="normal" font="default" size="100%">Monperrus, Martin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining subclassing directives to improve framework reuse</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">api</style></keyword><keyword><style  face="normal" font="default" size="100%">documentation</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">frameworks</style></keyword><keyword><style  face="normal" font="default" size="100%">jface</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/141Mining-Subclassing-Directives-to-Improve-Framework-Reuse.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">141 - 150</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">To help developers in using frameworks, good documentation is crucial. However, it is a challenge to create high quality documentation especially of hotspots in white-box frameworks. This paper presents an approach to documentation of object-oriented white-box frameworks which mines from client code four different kinds of documentation items, which we call subclassing directives. A case study on the Eclipse JFace user-interface framework shows that the approach can improve the state of API documentation w.r.t. subclassing directives.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bhuricha Deen Sethanandha</style></author><author><style face="normal" font="default" size="100%">Bart Massey</style></author><author><style face="normal" font="default" size="100%">William Jones</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On the Need for OSS Patch Contribution Tools</style></title><secondary-title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">kanban</style></keyword><keyword><style  face="normal" font="default" size="100%">patch</style></keyword><keyword><style  face="normal" font="default" size="100%">patch acceptance</style></keyword><keyword><style  face="normal" font="default" size="100%">patches</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/osscomm004.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) projects and systems have become significant parts of the software economy. The sustainability of an OSS project depends largely on community contributions. The patch contribution process is important to OSS projects. Nevertheless, there are several issues negatively impacting patch contribution in mature OSS projects. These issues can be addressed by improving tools to support the patch contribution process.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rejas-Muslera, Ricardo J.</style></author><author><style face="normal" font="default" size="100%">García-Tejedor, Alvaro J.</style></author><author><style face="normal" font="default" size="100%">Rodriguez, Olga Peñalba</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Educational Resources in E-Learning</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">1 - 12</style></pages><abstract><style face="normal" font="default" size="100%">According to Dr. B.R. Ambedkar's definition (Deshpande &amp; Mugridge, 1994), Open Educational Resources (OER) are based on the philosophical view of knowledge as a collective, social product. In the last years the relevance of OER has been widely acknowledged and a high magnitude impact is to be expected for OER in the near future (Atkins et al, 2007), (Wiley &amp; Gurrell, 2009), especially as a masterpiece in e-learning development. The aim of this chapter is to present an overview of OER in e-learning, focused on two fundamental aspects: (i) technical issues, mainly standards, and (ii) socio-economic and legal questions. This way the chapter deals with the most relevant issues in this matter: Which is the OER's role in education, especially for e-learning performance? Which are the technical resources and current standards needed for them? Which socio-economics and legal aspects influence the diffusion and use of OER?</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Laffey, James</style></author><author><style face="normal" font="default" size="100%">Schmidt, Matthew</style></author><author><style face="normal" font="default" size="100%">Amelung, Christopher</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open for Social</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">education</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">49 - 64</style></pages><abstract><style face="normal" font="default" size="100%">Online learning in K-12 and higher education has been growing rapidly, and open source software has the potential to improve the quality of e-learning. This paper describes how FOSS enables turning e-learning from a potentially restrictive framing of the education experience to an emergent and social experience. The authors identify several key elements of the FOSS model that position open source initiatives to contribute to the emergent and social nature of experience in e-learning. The authors also describe several challenges to developing FOSS in a community of educators for e-learning. These elements and challenges are illustrated in a brief case report about the development of an open source software system called Context-aware Activity Notification System (CANS). CANS (http://cansaware.com) is a notification system that integrates with collaborative work and learning systems and is designed around the importance of awareness of user activity, a user's social context and personal notification preferences. </style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">von Kortzfleisch, Harald</style></author><author><style face="normal" font="default" size="100%">Schaarschmidt, Mario</style></author><author><style face="normal" font="default" size="100%">Magin, Philipp</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Scientific Entrepreneurship</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">48 - 66</style></pages><abstract><style face="normal" font="default" size="100%">The objective of this article is to conceptually transfer the concept of open source software (OSS) development to scientific entrepreneurship and to hypothetically discuss the support potentials of this rather new development philosophy for what we than call open scientific entrepreneurship. Therefore, at first the authors will go into conceptual details of scientific entrepreneurship and than of OSS development. Following, the main thrust of the article presents open scientific entrepreneurship from two points of origin: first of all, OSS development as a specific form of scientific e-entrepreneurship and further on potential benefits of opening “traditional” scientific entrepreneurship up by looking at specific action fields. These action fields are theoretically based on the process and competence perspective of scientific entrepreneurship. Finally, the general benefits as well as downsides of the concept of openness are discussed on a generic level. It becomes obvious that there is need for balancing the tensions between an open and closed design pattern for scientific entrepreneurship with a general emphasis on the open design perspective.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Saini, Sanjeev K.</style></author><author><style face="normal" font="default" size="100%">Krishnan, C. N.</style></author><author><style face="normal" font="default" size="100%">Rajaram, L. N.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Adoption Index</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">48 - 60</style></pages><abstract><style face="normal" font="default" size="100%">This paper reports the preliminary results of a study conducted to assess and quantify the adoption of Free/Open Source Software (FOSS) by organisations and enterprises. While almost all organisations use FOSS in some form today, there is a wide variation in the manner and extent to which they do so, and presently no quantitative measure exists that can capture the true picture. The present work has built a model with two sets of parameters that, when fed with relevant data about an organisation, generates a single number, the FOSS Adoption Index (FAI), for that organisation. The index is so defined that the higher its value for an organisation, the greater is the extent of FOSS adoption in that organisation. Beyond the single measure FAI that gives a coarse assessment, the model also allows drilling down to finer levels of granularity that provides deeper insights into the status and role of FOSS within a given organisation. Primary data collected for two classes of organisations through questionnaire based surveys and interviews have been used to demonstrate the working of the model as well as its potential usefulness for real world situations.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Madey, G.</style></author><author><style face="normal" font="default" size="100%">van Antwerp, M.</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Ågerfalk, Pär</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús M.</style></author><author><style face="normal" font="default" size="100%">Madey, Gregory R.</style></author><author><style face="normal" font="default" size="100%">Noll, John</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Developer and Project Networks</style></title><secondary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication TechnologyOpen Source Software: New Horizons</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">berlios</style></keyword><keyword><style  face="normal" font="default" size="100%">savannah</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer Berlin Heidelberg</style></publisher><pub-location><style face="normal" font="default" size="100%">Berlin, Heidelberg</style></pub-location><volume><style face="normal" font="default" size="100%">319</style></volume><pages><style face="normal" font="default" size="100%">407 - 412</style></pages><isbn><style face="normal" font="default" size="100%">978-3-642-13244-5</style></isbn><abstract><style face="normal" font="default" size="100%">This paper outlines complex network concepts and how social networks are built from Open Source Software (OSS) data. We present an initial study of the social networks of three different OSS forges, BerliOS Developer, GNU Savannah, and SourceForge. Much research has been done on snapshot or conflated views of these networks, especially SourceForge, due to the size of the SourceForge community. The degree distribution, connectedness, centrality, and scale-free nature of SourceForge has been presented for the network at particular points in time. However, very little research has been done on how the network grows, how connections were made, especially during its infancy, and how these metrics evolve over time. </style></abstract><notes><style face="normal" font="default" size="100%">no information on data gathering procedures</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lenin, R. B.</style></author><author><style face="normal" font="default" size="100%">Ramaswamy, S.</style></author><author><style face="normal" font="default" size="100%">Yu, Liguo</style></author><author><style face="normal" font="default" size="100%">Govindan, R. B.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Systems</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">28 - 47</style></pages><abstract><style face="normal" font="default" size="100%">Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems ‘evolve’ as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Junior, Methanias Colaco</style></author><author><style face="normal" font="default" size="100%">Mendonca, Manoel</style></author><author><style face="normal" font="default" size="100%">Farias, Mario</style></author><author><style face="normal" font="default" size="100%">Henrique, Paulo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">neurolinguistics</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">126 - 129</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) mailing lists are used by developers to discuss software engineering tasks performed in the project. In the last years, researchers have been conducting mailing lists linguistic analyses for understanding the intricacies of OSS development. An unpublished approach for that is to use NeuroLinguistic Theory (NT). NT postulates the use of a Preferred Representational cognitive System (PRS) in specific contexts. This means that different resources and cognitive channels are used by developers in order to understand software, but what types of representational systems are the preferred by software engineers? This paper introduces a psychometrically-based neuro-linguistic analysis tool to classify developers, and presents early results of an experiment to assess the PRS of four top developers against a baseline of the Apache server mailing list.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Davies, Julius</style></author><author><style face="normal" font="default" size="100%">Hanyu Zhang</style></author><author><style face="normal" font="default" size="100%">Nussbaum, Lucas</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Perspectives on bugs in the Debian bug tracking system</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/86bugs-debian.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">86 - 89</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Bugs in Debian differ from regular software bugs. They are usually associated with packages, instead of software modules. They are caused and fixed by source package uploads instead of code commits. The majority are reported by individuals who appear in the bug database once, and only once. There also exists a small group of bug reporters with over 1,000 bug reports each to their name. We also explore our idea that a high bug-frequency for an individual package might be an indicator of popularity instead of poor quality.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lamkanfi, Ahmed</style></author><author><style face="normal" font="default" size="100%">Demeyer, Serge</style></author><author><style face="normal" font="default" size="100%">Giger, Emanuel</style></author><author><style face="normal" font="default" size="100%">Goethals, Bart</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Predicting the severity of a reported bug</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">severity</style></keyword><keyword><style  face="normal" font="default" size="100%">text mining</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/1lamkanfiDemeyer1.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bug, it remains an inherent manual process left to the person reporting the bug. In this paper we investigate whether we can accurately predict the severity of a reported bug by analyzing its textual description using text mining algorithms. Based on three cases drawn from the open-source community (Mozilla, Eclipse and GNOME), we conclude that given a training set of sufficient size (approximately 500 reports per severity), it is possible to predict the severity with a reasonable accuracy (both precision and recall vary between 0.65-0.75 with Mozilla and Eclipse; 0.70-0.85 in the case of GNOME).</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robbes, Romain</style></author><author><style face="normal" font="default" size="100%">Pollet, Damien</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Replaying IDE interactions to evaluate and improve change prediction approaches</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cbse</style></keyword><keyword><style  face="normal" font="default" size="100%">change based software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">change prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">changes</style></keyword><keyword><style  face="normal" font="default" size="100%">commit</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">development history</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipseeye</style></keyword><keyword><style  face="normal" font="default" size="100%">ide</style></keyword><keyword><style  face="normal" font="default" size="100%">mylyn</style></keyword><keyword><style  face="normal" font="default" size="100%">spyware</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/161Robbes2010changePrediction.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">161 - 170</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Change prediction helps developers by recommending program entities that will have to be changed alongside the entities currently being changed. To evaluate their accuracy, current change prediction approaches use data from versioning systems such as CVS or SVN. These data sources provide a coarse-grained view of the development history that flattens the sequence of changes in a single commit. They are thus not a valid basis for evaluation in the case of development-style prediction, where the order of the predictions has to match the order of the changes a developer makes. We propose a benchmark for the evaluation of change prediction approaches based on fine-grained change data recorded from IDE usage. Moreover, the change prediction approaches themselves can use the more accurate data to fine-tune their prediction. We present an evaluation procedure and use it on several change prediction approaches, both novel and from the literature, and report on the results.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Replicating MSR: A study of the potential replicability of papers published in the Mining Software Repositories proceedings</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">data</style></keyword><keyword><style  face="normal" font="default" size="100%">literature review</style></keyword><keyword><style  face="normal" font="default" size="100%">msr</style></keyword><keyword><style  face="normal" font="default" size="100%">replication</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://gsyc.urjc.es/~grex/msr2010</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/171MSR_2010_69.final_.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">171 - 180</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">This paper is the result of reviewing all papers published in the proceedings of the former International Workshop on Mining Software Repositories (MSR) (2004-2006) and now Working Conference on MSR (2007-2009). We have analyzed the papers that contained any experimental analysis of software projects for their potentiality of being replicated. In this regard, three main issues have been addressed: i) the public availability of the data used as case study, ii) the public availability of the processed dataset used by researchers and iii) the public availability of the tools and scripts. A total number of 171 papers have been analyzed from the six workshops/working conferences up to date. Results show that MSR authors use in general publicly available data sources, mainly from free software repositories, but that the amount of publicly available processed datasets is very low. Regarding tools and scripts, for a majority of papers we have not been able to find any tool, even for papers where the authors explicitly state that they have built one. Lessons learned from the experience of reviewing the whole MSR literature and some potential solutions to lower the barriers of replicability are finally presented and discussed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></title><secondary-title><style face="normal" font="default" size="100%">Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">oscomm</style></keyword><keyword><style  face="normal" font="default" size="100%">oscomm2010</style></keyword><keyword><style  face="normal" font="default" size="100%">oss2010</style></keyword><keyword><style  face="normal" font="default" size="100%">workshop</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/osscomm000.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">The Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) aims at building a commu- nity of researchers and practitioners to share experiences and discuss chal- lenges involved in building and maintaining open source communities. De- tailed	information	regarding	the	workshop	is	available	at http://tutopen.cs.tut.fi/oscomm10/.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ibrahim, Walid M</style></author><author><style face="normal" font="default" size="100%">Bettenburg, Nicolas</style></author><author><style face="normal" font="default" size="100%">Shihab, Emad</style></author><author><style face="normal" font="default" size="100%">Adams, Bram</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Should I contribute to this discussion?</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/181ibrahim-msr2010.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town</style></pub-location><pages><style face="normal" font="default" size="100%">181 - 190</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Development mailing lists play a central role in facilitating communication in open source projects. Since these lists frequently host design and project discussions, knowledgeable contribution to these discussion threads is essential to avoid mis-communication that might slow-down the progress of a project. However, given the sheer volume of emails on these lists, it is easy to miss important discussions. To find out how developers are able to deal with mailing list discussions, we study the main factors that encourage developers to contribute to the development mailing lists. We develop personalized models to automatically identify discussion threads that a developer would contribute to based on his previous contribution behavior. Case studies on development mailing lists of three open source projects (Apache, PostgreSQL and Python) show that the average accuracy of our models is 89-85% and that the models vary significantly between different developers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bein, Wolfgang</style></author><author><style face="normal" font="default" size="100%">Jeffery, Clinton</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards an Openness Rating System for Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">alice</style></keyword><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">contribution</style></keyword><keyword><style  face="normal" font="default" size="100%">documentation</style></keyword><keyword><style  face="normal" font="default" size="100%">freespire</style></keyword><keyword><style  face="normal" font="default" size="100%">galib</style></keyword><keyword><style  face="normal" font="default" size="100%">latex</style></keyword><keyword><style  face="normal" font="default" size="100%">license</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">linux kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">mediaportal</style></keyword><keyword><style  face="normal" font="default" size="100%">openness</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice</style></keyword><keyword><style  face="normal" font="default" size="100%">opensolaris</style></keyword><keyword><style  face="normal" font="default" size="100%">rating</style></keyword><keyword><style  face="normal" font="default" size="100%">unicon</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/10-07-04.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 8</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-5509-6</style></isbn><abstract><style face="normal" font="default" size="100%">Many open source software projects are not very open to third party developers. The point of open source is to enable anyone to fix bugs or add desired capabilities without holding them hostage to the original developers. This principle is important because an open source project's developers may be unresponsive or unable to meet third party needs, even if funding support for requested improvements is offered.This paper presents a simple rating system for evaluating the openness of software distributions. The rating system considers factors such as platform portability, documentation, licensing, and contribution policy. Several popular open source products are rated in order to illustrate the efficacy of the rating system.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Pratt, Landon J.</style></author><author><style face="normal" font="default" size="100%">Krein, Jonathan L.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Trends That Affect Temporal Analysis Using SourceForge Data</style></title><secondary-title><style face="normal" font="default" size="100%">5th Workshop on Public Data about Software Development (WoPDaSD 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cliff walls</style></keyword><keyword><style  face="normal" font="default" size="100%">committers</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">growth</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">time</style></keyword><keyword><style  face="normal" font="default" size="100%">time series</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/wopdasd001.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">SourceForge is a valuable source of software artifact data for researchers who study project evolution and developer behavior. However, the data exhibit patterns that may bias temporal analyses. Most notable are cliff walls in project source code repository timelines, which indicate large commits that are out of character for the given project. These cliff walls often hide significant periods of development and developer collaboration—a threat to studies that rely on SourceForge repository data. We demonstrate how to identify these cliff walls, discuss reasons for their appearance, and propose preliminary measures for mitigating their effects in evolution-oriented studies.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;In this paper we examine some of the limitations of artifact data by specifically addressing the applicability of SourceForge data to the study of project evolution.&quot;

&quot;For our analysis we examine 9,997 Production/Stable or Maintenance phase projects stored in CVS on SourceForge and extracted in October of 2006 [5]&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nussbaum, Lucas</style></author><author><style face="normal" font="default" size="100%">Zacchiroli, Stefano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Ultimate Debian Database: Consolidating bazaar metadata for Quality Assurance and data mining</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">udd</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/52msr2010-udd.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">52 - 61</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">FLOSS distributions like RedHat and Ubuntu require a lot more complex infrastructures than most other FLOSS projects. In the case of community-driven distributions like Debian, the development of such an infrastructure is often not very organized, leading to new data sources being added in an impromptu manner while hackers set up new services that gain acceptance in the community. Mixing and matching data is then harder than should be, albeit being badly needed for Quality Assurance and data mining. Massive refactoring and integration is not a viable solution either, due to the constraints imposed by the bazaar development model. This paper presents the Ultimate Debian Database (UDD), which is the countermeasure adopted by the Debian project to the above &quot;data hell&quot;. UDD gathers data from various data sources into a single, central SQL database, turning Quality Assurance needs that could not be easily implemented before into simple SQL queries. The paper also discusses the customs that have contributed to the data hell, the lessons learnt while designing UDD, and its applications and potentialities for data mining on FLOSS distributions.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Leahy, Michael G.</style></author><author><style face="normal" font="default" size="100%">Hall, G. Brent</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Open Source Software Components to Implement a Modular Web 2.0 Design for Map-Based Discussions</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">30 - 47</style></pages><abstract><style face="normal" font="default" size="100%">This paper discusses the research-based origins and modular architecture of an open source geospatial tool that facilitates synchronous individual and group discussions using the medium of a Web map service. The software draws on existing open source geospatial projects and associated libraries and techniques that have evolved as part of the new generation of Web applications. The purpose of the software is discussed, highlighting the fusion of existing open source projects to produce new tools. Two case studies are briefly discussed to illustrate the value an open source approach brings to communities who would remain otherwise outside the reach of proprietary software tools. The paper concludes with comments on the project’s future evolution as an open source participatory mapping platform.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nia, Roozbeh</style></author><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Devanbu, Premkumar</style></author><author><style face="normal" font="default" size="100%">Filkov, Vladimir</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Validity of network analyses in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">missing data</style></keyword><keyword><style  face="normal" font="default" size="100%">mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">perl</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/201NetworkAnalysis.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">201 - 209</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Social network methods are frequently used to analyze networks derived from Open Source Project communication and collaboration data. Such studies typically discover patterns in the information flow between contributors or contributions in these projects. Social network metrics have also been used to predict defect occurrence. However, such studies often ignore or side-step the issue of whether (and in what way) the metrics and networks of study are influenced by inadequate or missing data. In previous studies email archives of OSS projects have provided a useful trace of the communication and co-ordination activities of the participants. These traces have been used to construct social networks that are then subject to various types of analysis. However, during the construction of these networks, some assumptions are made, that may not always hold; this leads to incomplete, and sometimes incorrect networks. The question then becomes, do these errors affect the validity of the ensuing analysis? In this paper we specifically examine the stability of network metrics in the presence of inadequate and missing data. The issues that we study are: 1) the effect of paths with broken information flow (i.e. consecutive edges which are out of temporal order) on measures of centrality of nodes in the network, and 2) the effect of missing links on such measures. We demonstrate on three different OSS projects that while these issues do change network topology, the metrics used in the analysis are stable with respect to such changes.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We have mined archival records of developer mailing lists to generate reply-to social networks for the three OSS projects: Apache, MySQL, and Perl.&quot;

&quot;For each of these projects, we construct an information flow network based on messages that are sent as replies to previous messages....We use this methodology on all mined data to create a network of mailing list participants. &quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">van Antwerp, M.</style></author><author><style face="normal" font="default" size="100%">Madey, G.</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Ågerfalk, Pär</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús M.</style></author><author><style face="normal" font="default" size="100%">Madey, Gregory R.</style></author><author><style face="normal" font="default" size="100%">Noll, John</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Warehousing and Studying Open Source Versioning Metadata</style></title><secondary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology Open Source Software: New Horizons (OSS 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">berlios</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">savannah</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword><keyword><style  face="normal" font="default" size="100%">subversion</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer Berlin Heidelberg</style></publisher><pub-location><style face="normal" font="default" size="100%">Berlin, Heidelberg</style></pub-location><volume><style face="normal" font="default" size="100%">319</style></volume><pages><style face="normal" font="default" size="100%">413 - 418</style></pages><isbn><style face="normal" font="default" size="100%">978-3-642-13244-5</style></isbn><abstract><style face="normal" font="default" size="100%">In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxtaposed with the SourceForge.net Research Data Archive [5] for the purpose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Huett, Jason B.</style></author><author><style face="normal" font="default" size="100%">Sharp, Jason H.</style></author><author><style face="normal" font="default" size="100%">Huett, Kimberly C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What's all the FOSS?</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">1 - 14</style></pages><abstract><style face="normal" font="default" size="100%">Philosophical, financial, practical, and pedagogical considerations have prompted educators to take a serious look at Free and Open Source Software (FOSS) as an alternative to proprietary software. To better understand the overall concept of FOSS, this article provides a brief history of FOSS as well as a summary of its definition, philosophy, and major areas of research, including strengths and limitations, diffusion in education and educational uses as well as a look at the opportunities, issues, and challenges associated with FOSS. In conclusion, the authors speculate how FOSS, along with advances in E-Learning and other emerging technologies, will positively shape our educational future. </style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bachmann, Adrian</style></author><author><style face="normal" font="default" size="100%">Bernstein, Abraham</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">When process data quality affects the number of bugs: Correlations in software engineering datasets</style></title><secondary-title><style face="normal" font="default" size="100%">2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice.org</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2010</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/62bachmann-msr10.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Cape Town, South Africa</style></pub-location><pages><style face="normal" font="default" size="100%">62 - 71</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-6802-7</style></isbn><abstract><style face="normal" font="default" size="100%">Software engineering process information extracted from version control systems and bug tracking databases are widely used in empirical software engineering. In prior work, we showed that these data are plagued by quality deficiencies, which vary in its characteristics across projects. In addition, we showed that those deficiencies in the form of bias do impact the results of studies in empirical software engineering. While these findings affect software engineering researchers the impact on practitioners has not yet been substantiated. In this paper we, therefore, explore (i) if the process data quality and characteristics have an influence on the bug fixing process and (ii) if the process quality as measured by the process data has an influence on the product (i.e., software) quality. Specifically, we analyze six Open Source as well as two Closed Source projects and show that process data quality and characteristics have an impact on the bug fixing process: the high rate of empty commit messages in Eclipse, for example, correlates with the bug report quality. We also show that the product quality - measured by number of bugs reported - is affected by process data quality measures. These findings have the potential to prompt practitioners to increase the quality of their software process and its associated data quality.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Madey, Greg</style></author><author><style face="normal" font="default" size="100%">Squire, Megan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Envisioning National and International Research on the Multidisciplinary Empirical Science of Free/Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Spring 2009</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Audris Mockus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Amassing and indexing a large sample of version control systems: towards the census of public source code history</style></title><secondary-title><style face="normal" font="default" size="100%">6th IEEE Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bazaar</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">git</style></keyword><keyword><style  face="normal" font="default" size="100%">mercurial</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">subversion</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May 16–17</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/11amassing.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The source code and its history represent the output and process of software development activities and are an in- valuable resource for study and improvement of software development practice. While individual projects and groups of projects have been extensively analyzed, some fundamental questions, such as the spread of innovation or genealogy of the source code, can be answered only by considering the entire universe of publicly available source code and its history. We describe methods we developed over the last six years to gather, index, and update an approximation of such a universal repository for publicly accessible version control systems and for the source code inside a large corporation. While challenging, the task is achievable with limited resources. The bottlenecks in network bandwidth, processing, and disk access can be dealt with using inherent parallelism of the tasks and suitable tradeoffs between the amount of storage and computations, but a completely automated discovery of public version control systems may require enticing participation of the sampled projects. Such universal repository would allow studies of global properties and origins of the source code that are not possible through other means.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Audris Mockus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Succession: Measuring Transfer of Code and Developer Productivity</style></title><secondary-title><style face="normal" font="default" size="100%">2009 International Conference on Software Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May 12–22</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, CA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Subramaniam, Chandrasekar</style></author><author><style face="normal" font="default" size="100%">Sen, Ravi</style></author><author><style face="normal" font="default" size="100%">Nelson, Matthew L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Determinants of open source software project success: A longitudinal study</style></title><secondary-title><style face="normal" font="default" size="100%">Decis. Support Syst.</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">licenses</style></keyword><keyword><style  face="normal" font="default" size="100%">longitudinal study</style></keyword><keyword><style  face="normal" font="default" size="100%">Open source project</style></keyword><keyword><style  face="normal" font="default" size="100%">OSS</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">restrictive</style></keyword><keyword><style  face="normal" font="default" size="100%">Software project success</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://portal.acm.org/citation.cfm?id=1480545.1480824</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Elsevier Science Publishers B. V.</style></publisher><pub-location><style face="normal" font="default" size="100%">Amsterdam, The Netherlands, The Netherlands</style></pub-location><volume><style face="normal" font="default" size="100%">46</style></volume><pages><style face="normal" font="default" size="100%">576–585</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, we investigate open source software (OSS) success using longitudinal data on OSS projects. We find that restrictive OSS licenses have an adverse impact on OSS success. On further analysis, restrictive OSS license is found to be negatively associated with developer interest, but is positively associated with the interest of non-developer users and project administrators. We also show that developer and non-developer interest in the OSS project and the project activity levels in any time period significantly affect the project success measures in subsequent time period. The implications of our findings for OSS research and practice are discussed. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fang, Yulin</style></author><author><style face="normal" font="default" size="100%">Neufeld, Derrick</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding Sustained Participation in Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">J. Manage. Inf. Syst.</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Communities Of Practice</style></keyword><keyword><style  face="normal" font="default" size="100%">Legitimate Peripheral Participation</style></keyword><keyword><style  face="normal" font="default" size="100%">Open Source Projects</style></keyword><keyword><style  face="normal" font="default" size="100%">Open Source Software Community</style></keyword><keyword><style  face="normal" font="default" size="100%">Qualitative Study</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://portal.acm.org/citation.cfm?id=1554441.1554443</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">M. E. Sharpe, Inc.</style></publisher><pub-location><style face="normal" font="default" size="100%">Armonk, NY, USA</style></pub-location><volume><style face="normal" font="default" size="100%">25</style></volume><pages><style face="normal" font="default" size="100%">9–50</style></pages><abstract><style face="normal" font="default" size="100%">Prior research into open source software (OSS) developer participation has emphasized individuals' motivations for joining these volunteer communities, but it has failed to explain why people stay or leave in the long run. Building upon Lave and Wenger's theory of legitimate peripheral participation (LPP), this paper offers a longitudinal investigation of one OSS community in which sustained participation is hypothesized to be associated with the coevolution of two major elements of LPP theory: &quot;situated learning&quot; (the process of acting knowledgeably and purposefully in the world) and &quot;identity construction&quot; (the process of being identified within the community). To test this hypothesis, data were collected from multiple sources, including online public project documents, electronic mail messages, tracker messages, and log files. Results from qualitative analyses revealed that initial conditions to participate did not effectively predict long-term participation, but that situated learning and identity construction behaviors were positively linked to sustained participation. Furthermore, this study reveals that sustained participants distinguished themselves by consistently engaging in situated learning that both made conceptual (advising others) and practical contributions (improving the code). Implications and future research are discussed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Méndez-Durón, Rebeca</style></author><author><style face="normal" font="default" size="100%">García, Clara E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Returns from social capital in open source software networks</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of Evolutionary Economics</style></secondary-title><short-title><style face="normal" font="default" size="100%">J Evol Econ</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">games</style></keyword><keyword><style  face="normal" font="default" size="100%">gpl</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">social capital</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">4/2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Mendez-DuronGarcia.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">19</style></volume><pages><style face="normal" font="default" size="100%">277 - 295</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software projects base their operation on a collaborative structure for knowledge exchange in the form of provision or reception of information, expertise, and feedback on the creation of source code. Here, we address the direction of these knowledge flows among projects throughout social networks and their impact on project success. We identify the roles of membership or contribution that individuals play within projects. We found that connections through contributors who bring their knowledge to the project, improve project success, and that connection through members, who transfer their knowledge towards other projects, enhance project success. Finally, we found that ties through shared membership and contributions hamper project success. The analysis of knowledge flows and their impact on project success imply a translation of returns from investment in social capital, where investment takes the shape of knowledge flows and the returns mean the projects' diffusion over the network.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue><notes><style face="normal" font="default" size="100%">&quot;The data we use in this analysis come from the SourceForge.net Research Data (Department of Computer Science and Engineering, University of Notre Dame).&quot; &quot;Particularly, our dataset is a sub-sample of 2,962 valid observations over twelve months of projects aimed at developing games’ software. To get this sample, we look at the monthly dumps of data and select all projects that belong to the category of GNU Public License (GPL) [6]. &quot;
dependent variable: performance (number of downloads); independent variable: social network (&quot;Here we measure ties among projects through the individuals’ member and contributor roles at projects on the network over time.)</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sen, S.</style></author><author><style face="normal" font="default" size="100%">Vig, J.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Tagommenders: Connecting Users to Items through Tags</style></title><secondary-title><style face="normal" font="default" size="100%">International World Wide Web Conference</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">4/20/2009</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Madrid, Spain</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paul J. Adams</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Bridging the Gap between Agile and Free Software Approaches</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">agile</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">plone</style></keyword><keyword><style  face="normal" font="default" size="100%">productivity</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">scrum</style></keyword><keyword><style  face="normal" font="default" size="100%">sprints</style></keyword><keyword><style  face="normal" font="default" size="100%">subversion</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">31/2009</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">58 - 71</style></pages><abstract><style face="normal" font="default" size="100%">Agile sprints are short events where a small team collocates in order to work on particular aspects of the overall project for a short period of time. Sprinting is a process that has been observed also in Free Software projects: these two paradigms, sharing common principles and values have shown several commonalities of practice. This article evaluates the impact of sprinting on a Free Software project through the analysis of code repository logs: sprints from two Free Software projects (Plone and KDE PIM) are assessed and two hypotheses are formulated: do sprints increase productivity? Are Free Software projects more productive after sprints compared with before? The primary contribution of this article is to show how sprinting creates a large increase in productivity both during the event, and immediately after the event itself: this argues for more in-depth studies focussing on the nature of sprinting.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Squire, Megan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Integrating Projects from Multiple Open Source Code Forges</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">data integration</style></keyword><keyword><style  face="normal" font="default" size="100%">forges</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">31/2009</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">46 - 57</style></pages><abstract><style face="normal" font="default" size="100%">Much of the data about free, libre, and open source (FLOSS) software development comes from studies of code forges or code repositories used for managing projects. This paper presents a method for integrating data about open source projects by way of matching projects (entities) across multiple code forges. After a review of the relevant literature, a few of the methods are chosen and applied to the FLOSS domain, including a comparison of some simple scoring systems for pairwise project matches. Finally, the paper describes limitations of this approach and recommendations for future work.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Teaching Software Engineering with Free/Libre Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">curriculum</style></keyword><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">teaching</style></keyword><keyword><style  face="normal" font="default" size="100%">undergraduate</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">31/2009</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">72 - 90</style></pages><abstract><style face="normal" font="default" size="100%">One of the major problems in software engineering education is the involvement of students in real world software projects. Industry projects are a solution, but in many cases they are hard to find and student participation can be problematic due to cultural, familiarization and other practical reasons. The abundance of Free / Libre Open Source Software (FLOSS) projects is a neat solution, offering multi-lingual, multicultural environments in virtually every application domain, at different levels of project size, maturity, organization etc. The paper analyzes how acquisition of practical experience on several basic and advanced software engineering topics can be achieved by working in a FLOSS project. The kind of skills that can be acquired are those requested by the Overview Report for Computing Curricula by ACM and topics examined are those of the Software Engineering Body of Knowledge, by IEEE. Also software engineering areas that require special care or that may not prove suitable for such treatment are identified. Various isolated teaching cases pertaining to this approach are presented and discussed.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús M.</style></author><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Tools for the Study of the Usual Data Sources found in Libre Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking systems</style></keyword><keyword><style  face="normal" font="default" size="100%">data sources</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">tools</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">31/2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/robles.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">24 - 45</style></pages><abstract><style face="normal" font="default" size="100%">Due to the open nature of Free/Libre/Open Source software projects, researchers have gained access to a rich set of development-related information. Although this information is publicly available on the Internet, obtaining and analyzing it in a convenient way is not an easy task and many considerations have to be taken into account. In this paper we present the most important data sources that can be found in libre software projects and that are studied by the research community: source code, source code management systems, mailing lists and bug tracking systems. We will give advice for the problems that can be found when retrieving and preparing the data sources for a posterior analysis, as well as provide information about the tools that support these tasks.</style></abstract><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andreas Meiszner</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">1st International Workshop on: ‘Designing for Participatory Learning’ Building from Open Source Success to Develop Free Ways to Share and Learn</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/1st International Workshop on.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">355 - 356</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Open Source world shows how volunteer collaboration can lead to great products and to great learning. We want to further explore at this workshop what happens using approaches from that community to break barriers between teachers and learners for today’s Internet-savvy young people to design and co-construct sites for participatory learning. The aim of this workshop is to explore the barriers for this type of learning in higher education settings. Content creation, knowledge exchange, community
dynamics, and the impact on the boundary between formal and informal education are key subjects of this workshop.
</style></abstract><section><style face="normal" font="default" size="100%">33</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">González-Barahona, Jesús</style></author><author><style face="normal" font="default" size="100%">Squire, Megan</style></author><author><style face="normal" font="default" size="100%">Izquierdo-Cortázar, Daniel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">4th International Workshop on Public Data about Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/4the International Workshop on Public Data.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">351 - 352</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Libre (free, open source) projects offer publicly available data sources. The research community is starting to produce, use and exchange large data sets of information. These data sets have to be retrieved, purged, described, and can be published for public consumption by other groups. Their availability allows for the decoupling of research activities, the reproducibility of research results, and even the collaboration (and competition) in the analysis of data. This activity is frequently presented at workshops and conferences, but since the focus of these conferences is not specific to the use of public data, discussions of techniques and experiences are not as deep and fruitful as they could be. This workshop is once again (for the fourth year in a row) such a place. We will host discussions specifically about these sorts of public data sets about software development, how they are retrieved, how they can be analyzed and mined, how they can be exchanged and extended.
</style></abstract><section><style face="normal" font="default" size="100%">31</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysis of Open Source Software Development Iterations by Means of Burst Detection Techniques</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Analysis of Open Source Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">83 - 93</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">A highly efficient bug fixing process and quick release cycles are considered key properties of the open source software development methodology. In this paper, we study the relation between code activities (such as lines of code added per commit), bug fixing activities, and software release dates in a subset of open source projects. To study the phenomenon, we gathered a large data set about the evolution of 5 major open source projects. We compared activities by means of a burst detection technique to discover temporal peaks in time-series. We found quick adaptation of issue tracking activities in proximity of releases, and a distribution of coding activities across releases. Results show the importance of the application type/domain for the evaluation of the development process.
</style></abstract><section><style face="normal" font="default" size="100%">9</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús</style></author><author><style face="normal" font="default" size="100%">Deprez, Jean-Christophe</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assessing FLOSS Communities: An Experience Report from the QualOSS Project</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Assessing FLOSS Communities.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">364 - 364</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents work done in the QualOSS (Quality of Open Source Software) research project,which aims at building a methodology and tools to help in the assessment of the quality of FLOSS (free, libre, open source software) endeavors. In particular, we introduce the research done to evaluate the FLOSS endeavor communities. Following the Goal-Question-Metric paradigm, QUALOSS describes goals, the associated questions and then metrics that allow to answer the questions.
</style></abstract><section><style face="normal" font="default" size="100%">38</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, Claudio</style></author><author><style face="normal" font="default" size="100%">Banzi, Massimo</style></author><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author><author><style face="normal" font="default" size="100%">El Ioini, Nabil</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assurance Evaluation for OSS Adoption in a Telco Context</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Assurance Evaluation for OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">363 - 363</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software Assurance (SwA) is a complex concept that involves different stages of a software development process and may be defined differently depending on its focus, as for instance software quality, security, or dependability. In Computer Science, the term assurance is referred to all activities necessary to provide enough confidence that a software product will satisfy its users’ functional and non-functional requirements.
</style></abstract><section><style face="normal" font="default" size="100%">37</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Juho Lindman</style></author><author><style face="normal" font="default" size="100%">Juutilainen, Juha-Pekka</style></author><author><style face="normal" font="default" size="100%">Rossi, Matti</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Beyond the Business Model: Incentives for Organizations to Publish Software Source Code</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Beyond the Business Model.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">47 - 56</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The software stack opened under Open Source Software (OSS) licenses is growing rapidly. Commercial actors have released considerable amounts of previously proprietary source code. These actions beg the question why companies choose a strategy based on giving away software assets? Research on outbound OSS approach has tried to answer this question with the concept of the “OSS business model”. When studying the reasons for code release, we have observed that the business model concept is too generic to capture the many incentives organizations have. Conversely, in this paper we investigate empirically what the companies’ incentives are by means of an exploratory case study of three organizations in different stages of their code release. Our results indicate that the companies aim to promote standardization, obtain development resources, gain cost savings, improve the quality of software, increase the trustworthiness of software, or steer OSS communities. We conclude that future research on outbound OSS could benefit from focusing on the heterogeneous incentives for code release rather than on revenue models.
</style></abstract><section><style face="normal" font="default" size="100%">6</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stathopoulos, Panagiotis</style></author><author><style face="normal" font="default" size="100%">Soumplis, Alexandros</style></author><author><style face="normal" font="default" size="100%">Houssos, Nikos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Case Study of an F/OSS Virtualization Platform Deployment and Quantitative Results</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Case Study of an F OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">367 - 367</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we present practical experiences and results from the deployment of an F/OSS virtualization platform. EKT’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’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.
</style></abstract><section><style face="normal" font="default" size="100%">41</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ayala, Claudia</style></author><author><style face="normal" font="default" size="100%">Hauge, Øyvind</style></author><author><style face="normal" font="default" size="100%">Conradi, Reidar</style></author><author><style face="normal" font="default" size="100%">Franch, Xavier</style></author><author><style face="normal" font="default" size="100%">Li, Jingyue</style></author><author><style face="normal" font="default" size="100%">Velle, Ketil</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Challenges of the Open Source Component Marketplace in the Industry</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Challenges of the Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">213 - 224</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 “classical” 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.
</style></abstract><section><style face="normal" font="default" size="100%">19</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Johansson, Björn</style></author><author><style face="normal" font="default" size="100%">Sudzina, Frantisek</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Choosing Open Source ERP Systems: What Reasons Are There For Doing So?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Choosing Open Source ERP.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">143 - 155</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract><section><style face="normal" font="default" size="100%">14</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Keßler, Steffen</style></author><author><style face="normal" font="default" size="100%">Alpar, Paul</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Customization of Open Source Software in Companies</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Customization of Open Source Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">129 - 142</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract><section><style face="normal" font="default" size="100%">13</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Milev, Roberto</style></author><author><style face="normal" font="default" size="100%">Muegge, Steven</style></author><author><style face="normal" font="default" size="100%">Weiss, Michael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design Evolution of an Open Source Project Using an Improved Modularity Metric</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Design Evolution of an Open Source Project.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">20 - 33</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Modularity of an open source software code base has been associated with community growth, incentives for voluntary contribution, and a reduction in free riding. As a theoretical construct, it links open source software to other domains of research, including organization theory, the economics of industry structure, and new product development; however, measuring the modularity of an open source software design has proven difficult, especially for large and complex systems. Building on previous work on Design Structure Matrices (DSMs), this paper describes two contributions towards a method for examining the evolving modularity of large-scale software systems: (1) an algorithm and new modularity metric for comparing code bases of different size; and (2) evolution analysis of Apache Tomcat to illustrate the insights gained from this approach. Over a ten-year period, the modularity of Tomcat continually increased, except in three instances: with each major change to the architecture or implementation, modularity first declined, then increased in the subsequent version to fully compensate for the decline.
</style></abstract><section><style face="normal" font="default" size="100%">4</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Domain Drivers in the Modularization of FLOSS Systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Domain Drivers in the Modularization.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">3 - 19</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The classification of software systems into types has been achieved in the past by observing both their specifications and behavioral patterns: the SPE classification, for instance, and its further supplements and refinements, has identified the S-type (i.e., fully specified), the P-type (i.e., specified but dependent on the context) and the E-type (i.e., addressing evolving problems) among the software systems. In order to detect types, and establish similarities, among Free/Libre/Open Source Software (FLOSS) systems, this paper considers three modular characteristics (functions, files and folders) and their evolution: how they are evolving with size, if they are constant across systems, and whether recurring evolutionary patterns are observed. Using these various-grained characteristics,a set of models for the evolution of modularization are extracted from evolving systems, and then used to extract similarities and types from a wide sample of FLOSS projects. This paper provides three contributions: first, it shows that several models are needed to encompass the variety of modularization patterns; second, it provides three types of models (uni-variate, bi-variate and tri-variate) for the evolution of modularization, with significant goodness-of-fit’s. Finally, it shows that two of these patterns alone can interpolate the modular characteristics of the vast majority of a random choice of FLOSS projects.
</style></abstract><section><style face="normal" font="default" size="100%">3</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">German, Daniel</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study of the Reuse of Software Licensed under the GNU General Public License</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Empirical Study of the Reuse of Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">185 - 198</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software licensing is a complex issue in free and open source software (FOSS), specially when it involves the redistribution of derived works. The creation of derivative works created from components with different FOSS licenses poses complex challenges, particularly when one of the components is licensed under the terms of one of the versions of the GNU General Public License (GPL). This paper describes an empirical study of the manner in which GPLed licensed software is combined with components under different FOSS licenses. We have discovered that FOSS software developers have found interesting methods to create derivative works with GPLed software that legally circumvent the apparent restrictions of the GPL. In this paper we document these methods and show that FOSS licenses interact in complex and unexpected ways. In most of these cases the goal of the developers (both licensors and licensees) is to further increase the commons of FOSS.
</style></abstract><section><style face="normal" font="default" size="100%">17</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hofmann, Philipp</style></author><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Estimating Commit Sizes Efficiently</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Estimating Commit Sizes Effciently.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">105 - 115</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The quantitative analysis of software projects can provide insights that let us better understand open source and other software development projects. An important variable used in the analysis of software projects is the amount of work being contributed, the commit size. Unfortunately, post-facto, the commit size can only be estimated, not measured. This paper presents several algorithms for estimating the commit size. Our performance evaluation shows that simple, straightforward heuristics are superior to the more complex text-analysis-based algorithms. Not only are the heuristics significantly faster to compute, they also deliver more accurate results when estimating commit sizes. Based on this experience, we design and present an algorithm that improves on the heuristics, can be computed equally fast, and is more accurate than any of the prior approaches.
</style></abstract><section><style face="normal" font="default" size="100%">11</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">First International Workshop on Building Sustainable Open Source Communities (OSCOMM 2009)</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/First International Workshop.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">353 - 354</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The First International Workshop on Building Sustainable Open Source Communities aims at building a community of researchers and practitioners to share experiences and discuss challenges involved in building and maintaining open source communities.
</style></abstract><section><style face="normal" font="default" size="100%">32</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bach, Paula</style></author><author><style face="normal" font="default" size="100%">Carroll, John</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">FLOSS UX Design: An Analysis of User Experience Design in Firefox and OpenOffice.org</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Floss UX Desing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">237 - 250</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We describe two cases of open user experience (UX) design using the Firefox web browser and OpenOffice.org office suite as case studies. We analyze the social complexity of integrating UX practices into the two open source projects using activity awareness, a framework for understanding team performance in collective endeavors of significant scope, duration, and complexity. The facets of activity awareness are common ground, community of practice, social capital, and human development. We found that differences between the communities include different strategies for community building, UX status in the community, type of open UX design, and different ways to share information.
</style></abstract><section><style face="normal" font="default" size="100%">21</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Scialdone, Michael</style></author><author><style face="normal" font="default" size="100%">Li, Na</style></author><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Group Maintenance Behaviors of Core and Peripherial Members of Free/Libre Open Source Software Teams</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Group Maintenance Behavior.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">298 - 309</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Group Maintenance is pro-social, discretionary, and relation-building behavior that occurs between members of groups in order to maintain reciprocal trust and cooperation. This paper considers how Free/libre Open Source Software (FLOSS) teams demonstrate such behaviors within the context of e-mail, as this is the primary medium through which such teams communicate. We compare group maintenance behaviors between both core and peripheral members of these groups, as well as behaviors between a group that remains producing software today and one which has since dissolved. Our findings indicate that negative politeness tactics (those which show respect for the autonomy of others) may be the most instrumental group maintenance behaviors that contribute to a FLOSS group’s ability to survive and continue software production.
</style></abstract><section><style face="normal" font="default" size="100%">26</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Heatbeat Measuring Active Use.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">94 - 104</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents a novel method and algorithm to measure the size of an open source project’s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.
</style></abstract><section><style face="normal" font="default" size="100%">10</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Behlendorf, Brian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Open Source Can Still Save the World</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/How Open Source Can Still Save the World.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">2 </style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Many of the worlds’ major problems - economic distress, natural disaster responses, broken health care systems, education crises, and more - are not fundamentally information technology issues. However, in every case mentioned and more, there exist opportunities for Open Source software to uniquely change the way we can address these problems. At times this is about addressing a need for which no sufficient commercial market exists. For others, it is in the way Open Source licenses free the recipient from obligations to the creators, creating a relationship of mutual empowerment rather than one of dependency. For yet others, it is in the way the open collaborative processes that form around Open Source software provide a neutral ground for otherwise competitive parties to find a greatest common set of mutual needs to address together rather than in parallel. Several examples of such software exist today and are gaining traction. Governments, NGOs, and businesses are beginning to recognize the potential and are organizing to meet it. How far can this be taken?
</style></abstract><section><style face="normal" font="default" size="100%">2</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ven, Kris</style></author><author><style face="normal" font="default" size="100%">Verelst, Jan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Importance of External Support in the Adoption of Open Source Server Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Importance of Extertnal Support.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">116 - 128</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">IT managers seem to be hesitant to adopt OSS in the absence of professional support. Previous qualitative studies have indeed suggested that the availability of external support is important for the adoption of OSS. Therefore, we feel it is interesting to gain more insight into the role of external support in the adoption process. To this end, we performed a web survey involving 95 Belgian organizations. Our data suggests a balanced picture. As expected, our results show that the majority of organizations in our sample rely on commercial support such as vendor or third party support. Even organizations that have deployed OSS to a large extent—and that are therefore likely to have some experience and familiarity with OSS—rely on commercial support. Nevertheless, a considerable proportion of organizations indicated not to rely on commercial support, which suggests that internal expertise can be sufficient for successful adoption. Finally, and most surprisingly, we have found that the OSS community is used by a large proportion of organizations. This indicates that the OSS community is a valuable source of external support for organizations. Nevertheless, it appears that it is primarily used by organizations with a rather strong background in IT.
</style></abstract><section><style face="normal" font="default" size="100%">12</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hedberg, Henrik</style></author><author><style face="normal" font="default" size="100%">Iivari, Netta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Integrating HCI Specialists into Open Source Software Development Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Intergrating HCI Specialists.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">251 - 263</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Typical open source software (OSS) development projects are organized around technically talented developers, whose communication is based on technical aspects and source code. Decision-making power is gained through proven competence and activity in the project, and non-technical end-user opinions are too many times neglected. In addition, also human-computer interaction (HCI) specialists have encountered difficulties in trying to participate in OSS projects, because there seems to be no clear authority and responsibility for them. In this paper, based on HCI and OSS literature, we introduce an extended OSS development project organization model that adds a new level of communication and roles for attending human aspects of software. The proposed model makes the existence of HCI specialists visible in the projects, and promotes interaction between developers and the HCI specialists in the course of a project.
</style></abstract><section><style face="normal" font="default" size="100%">22</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ali Babar, Muhammad</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">van der Linden, Frank</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Joint Workshop of QACOS and OSSPL</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Joint Workshop of QACOS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">357 - 358</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The OSS movement, which originated from a pragmatic need to share code among individuals, has grown to become a major force behind inter-organizational reuse of platforms, components and code. The use of open source software to build single or family of systems (i.e., product line development) appears to be a profitable way to quality software products. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source
communities. The configuration mechanisms used in open source communities may be applicable within software product lines variability management. In addition, product line organizations are usually involved in distributed development, which works very efficiently within open source communities, leading to high quality products. However, at present, there is limited interaction between the open source and product line development communities.
</style></abstract><section><style face="normal" font="default" size="100%">34</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ortega, Felipe</style></author><author><style face="normal" font="default" size="100%">Lafuente, Isabel</style></author><author><style face="normal" font="default" size="100%">Gato, Jose</style></author><author><style face="normal" font="default" size="100%">González-Barahona, Jesús</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Libre Software in Spanish Public Administrations</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Libre Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">366 - 366</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Libre software started to be used in Public Administrations in Spain during the 1990s, in some isolated but interesting experiences.During the early 2000s, and specially in some regional governments, libre software started to be considered as an integral part of ITrelated policies. In 2007, it was evident that many experiences related to libre software were running in Public Administrations with different levels of success. However, no study had looked into the details of these experiences, and no comprehensive analysis had been performed to better understand the different factors that affect them.
</style></abstract><section><style face="normal" font="default" size="100%">40</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><translated-authors><author><style face="normal" font="default" size="100%">The NESSI Open Source Working Group</style></author></translated-authors></contributors><titles><title><style face="normal" font="default" size="100%">NESSI OSS Workshop</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/NESSI OSS Workshop.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">359 - 360</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The NESSI Technology Platform aims to provide a unified view for European research and development in Services Architectures and Software Infrastructures that will define technologies for new, open, industrial solutions and societal applications that enhance the safety, security and well-being of citizens.
</style></abstract><section><style face="normal" font="default" size="100%">35</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Peters, Stormy</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Is Changing the Way Work Gets Done</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source is Changing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">1 </style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software is changing not only the way the software industry works, but also the way work gets done. In the open source software model, individuals and companies collaborate together to produce software. They learn new ways of getting work done that are based on meritocracy and little management. In addition, they learn ways of communication that work well across large groups and virtual environments. These new ways of communicating and getting work done are changing the nature of work across all industries, not just the software industry, industries like mobile technology providers and medical equipment. Come learn how the open source software model is changing the way individuals and companies work and collaborate.
</style></abstract><section><style face="normal" font="default" size="100%">1</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sirkkala, Petri</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Opening Industrial Software: Planting an Onion</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Opening Industrial Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">57 - 69</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper studies the problem of building open source communities for industrial software that was originally developed as closed source. We present a conceptual framework for planning the early stages of the release process highlighting the main stakeholders and concerns involved. The framework is illustrated by means of three industrial software platforms reporting first experiences of the community building process. In order to measure the effectiveness of the approach, the use of a quantitative and qualitative evaluation framework is advocated.
</style></abstract><section><style face="normal" font="default" size="100%">7</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Lings, Brian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Openness to Standard Document Formats in Swedish Public Sector Organisations</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Openness to Standard Document Formats.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">320 - 329</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">There is a strong movement in Europe to promote products that support open, well-documented standards. Directives and proposals at European and national levels have been developed in this area. There is in particular an increasing recognition of the need for governmental organisations to support and promote standard document formats. This vision can stand in stark contrast with the reality of those document formats which can currently be accepted and produced by those organisations. In this paper we address the question: to what extent can and do Swedish governmental organisations respond appropriately when presented with a document in a format that conforms to an open standard? We find that a small minority of organisations can actually do so, whereas all are willing and able to accept documents in a proprietary format. The study also highlights a lack of transparency in organisations regarding formats which should be accepted and used for communication with the general public.
</style></abstract><section><style face="normal" font="default" size="100%">28</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bolici, Francesco</style></author><author><style face="normal" font="default" size="100%">de Laat, Paul</style></author><author><style face="normal" font="default" size="100%">Ljungberg, Jan</style></author><author><style face="normal" font="default" size="100%">Pontiggia, Andrea</style></author><author><style face="normal" font="default" size="100%">Rossi Lamastra, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Panel: Governance in Open Source Projects and Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Panel Governnance.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">370 - 370</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">“Although considerable research has been devoted to the growth and expansion of open source communities and the comparison between the efficiency of corporate structures and community structures in the field of software development, rather less attention has been paid to their governance structures (control, monitoring, supervision)” (Lattemann and Stieglitz 2005).
</style></abstract><section><style face="normal" font="default" size="100%">43</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Amundsen, Morten</style></author><author><style face="normal" font="default" size="100%">Ghosh, Rishab</style></author><author><style face="normal" font="default" size="100%">Hardy, Jean-Luc</style></author><author><style face="normal" font="default" size="100%">Sjöswärd, Per-Ola</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Panel: Open Source in the Public Sector</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Panel Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">368 - 369</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) is becoming mainstream, and it is perhaps not surprising that public sector organisations seek to explore the potential of OSS in financially difficult times. Today, OSS has become an issue of strategic importance for many public sector organisations. In addition, related to OSS, many organisations and governments are also acknowledging Open Standards as important for addressing various lock-in scenarios.
</style></abstract><section><style face="normal" font="default" size="100%">42</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Masmoudi, Héla</style></author><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">de Loupy, Claude</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Peeling the Onion</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Peeling the Onion.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">284 - 297</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">According to the now widely accepted “onion-model” of the organization of open source software development, an open source project typically relies on a core of developers that is assisted by a larger periphery of users. But what does the role of the periphery consist of? Raymond’s Linus’s Law which states that “given enough eyeballs all bugs are shallow” suggests at least one important function: the detection of defects. Yet, what are the ways through which core and periphery interact with each other? With the help of text-mining methods, we study the treatment of bugs that affected the Firefox Internet browser as reflected in the discussions and actions recorded in Mozilla’s issue tracking system Bugzilla. We find various patterns in the modes of interactions between core and peripheral members of the community. For instance, core members seem to engage more frequently with the periphery when the latter proposes a solution (a patch). This leads us to conclude that Alan Cox’s dictum “show me the code”, perhaps even more than Linus’s law, seems to be the dominant rule that governs the development of software like Firefox.
</style></abstract><section><style face="normal" font="default" size="100%">25</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hauge, Øyvind</style></author><author><style face="normal" font="default" size="100%">Ziemer, Sven</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Providing Commercial Open Source Software: Lessons Learned</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Providing Commercial Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">70 - 82</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Even though companies like Sun, IBM, MySQL and others have released several commercial Open Source Software (OSS) products, little evidence exist of how to successfully launch such products and establish a living community around them. This paper presents a case study from a small software company succeeding at establishing a business model and a vivid community around their own OSS products. Based on this case study, the paper presents lessons learned which could help other OSS providers.
</style></abstract><section><style face="normal" font="default" size="100%">8</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">del Bianco, Vieri</style></author><author><style face="normal" font="default" size="100%">Lavazza, Luigi</style></author><author><style face="normal" font="default" size="100%">Morasca, Sandro</style></author><author><style face="normal" font="default" size="100%">Taibi, Davide</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality of Open Source Software: The QualiPSo Trustworthiness Model</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Quality of Open Source Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">199 - 212</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Trustworthiness is one of the main issues upon which the decision whether to adopt an Open-Source Software (OSS) product is based. The work described here is part of an activity that has the goals of 1) defining an adequate notion of trustworthiness of software products and artifacts and 2) identifying a number of factors that influence it. Specifically, this paper reports about the identification of the “dimensions” of trustworthiness, i.e., of the high-level qualities that software products and artefacts have to posses in order to be considered trustworthy. These dimensions are described by means of a conceptual model of trustworthiness, which comprises the representation of the factors that affect the user’s perception of trustworthiness, as well as the objective characteristics of the products that contribute to “build” trustworthi-ness. The aforementioned model is equipped with a measurement plan that de-scribes, at the operational level, how to perform the evaluation of the trustwor-thiness of OSS products. The proposed model provides the basis to build quantitative models of the trustworthiness of OSS products and artifacts that are able to explain the relationships between the (objectively observable) characteristics of OSS products and the level of trustworthiness perceived by the users of such products.
</style></abstract><section><style face="normal" font="default" size="100%">18</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Adams, Paul</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reassessing Brooks’ Law for the Free Software Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Reassessing Brook's Law.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">274 - 283</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Proponents of Free Software have argued that some of the most established software engineering principles do not fully apply when considered in an open, distributed approach. Among these principles, “Brooks’ Law” has been questioned in the Free Software context: large teams of developers, contrary to the law, will not need an increasingly growing number of communication channels. As advocates claim, this is due to the internal haracteristics of the Free Software process: the high modularity of the code helps developers to work on comparted sections, without the need to coordinate with all other contriutors.
This paper examines Brooks’ Law in a Free Software context, and it studies the interaction of contributors to a large Free Software project, KDE. The network of interactions is analyzed and a summary term, the “compaction”, is dynamically evaluated to test how the coordination mechanism evolves over time in the project. This paper argues that the claim of advocates holds true, but with limitations: in the KDE project, the few initial developers needed a significant amount of communication. The growth of KDE brought the need to break the number of overall communication channels to a significant extent. Finally, an established amount of 300 developers currently needs the same amount of communication as when the developers were only 10. We interpret this result by arguing that Brooks’ Law holds true among the core developers of any large Free Software project.
</style></abstract><section><style face="normal" font="default" size="100%">24</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wright, Hyrum</style></author><author><style face="normal" font="default" size="100%">Perry, Dewayne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Release Mismanagement in Open Source</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Release Mismanagement.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">365 - 365</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">To a user, unreleased software is nonexistent software, even in open source projects which make the source code readily accessible. Every project requires regular software releases to encourage adoption and attract developers. Different projects approach the task of releasing software in variousways [2], and many experience breakdowns in their release process at some point during their evolution [3]. This poster presents examples of these instances, and how projects are learning from and improving upon them.
</style></abstract><section><style face="normal" font="default" size="100%">39</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stol, Klaas-Jan</style></author><author><style face="normal" font="default" size="100%">Ali Babar, Muhammad</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reporting Empirical Research in Open Source Software: The State of Practice</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Reporting Empirical Research.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">156 - 169</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Background: The number of reported empirical studies of Open Source Software (OSS) has continuously been increasing. However, there has been no effort to systematically review the state of the practice of reporting empirical studies of OSS with respect to the recommended standards of performing and reporting empirical studies in software engineering. It is important to understand, how to report empirical studies of OSS in order to make them useful for practitioners and researchers.
Research aim: The aim of our research is to gain insights in the state of the practice of reporting empirical studies of OSS in order to identify the gaps to be filled for improving the quality of evidence being provided for OSS.
Method: To that end, we decided to systematically review the empirical studies of OSS. A total of 63 papers reporting empirical studies were selected from the four editions of the Proceedings of the International Conference on Open Source Systems. The data were extracted and synthesised from the selected papers for analysis.
Results and conclusions: We have found that the quality of the reported OSS-related empirical studies needs to be significantly improved. Based on the results of our systematic review and general principles of reporting good empirical research, we present a set of guidelines for reporting OSS-related empirical studies. The suggested guidelines are expected to help the research community to improve the quality of reported studies.
</style></abstract><section><style face="normal" font="default" size="100%">15</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Knowles, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Engineering in Practice: Design and Architectures of FLOSS Systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Software Engineering in Practice.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">34 - 46</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free/Libre/Open Source Software (FLOSS) practitioners and developers are typically also users of their own systems: as a result, traditional software engineering (SE) processes (e.g., the requirements and design phases), take less time to articulate and negotiate among FLOSS developers. Design and requirements are kept more as informal knowledge, rather than formally described and assessed. This paper attempts to recover the SE concepts of software design and architectures from three FLOSS case studies, sharing the same application domain (i.e., Instant Messaging). Its first objective is to determine whether a common architecture emerges from the three systems, which can be used as shared knowledge for future applications. The second objective is to determine whether these architectures evolve or decay during the evolution of these systems. The results of this study are encouraging: albeit no explicit effort was done by FLOSS developers to define a high-level view of the architecture, a common shared architecture could be distilled for the Instant Messaging application domain. It was also found that, for two of the three systems, the architecture becomes better organised, and the components better specified, as long as the system evolves in time.
</style></abstract><section><style face="normal" font="default" size="100%">5</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paul, Celeste</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Survey of Usability Practices in Free/Libre/Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Survey of Usability Practices.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">264 - 273</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">A review of case studies about usability in eight Free/Libre/Open Source Software (FLOSS) projects showed that an important issue regarding a usability initiative in the project was the lack of user research. User research is a key component in the user-centered design (UCD) process and a necessary step for creating usable products. Reasons why FLOSS projects suffered from a lack of user research included poor or unclear project leadership, cultural differences between developer and designers, and a lack of usability engineers. By identifying these critical issues, the FLOSS usability community can begin addressing problems in the efficacy of usability activities and work towards creating more usable FLOSS products.
</style></abstract><section><style face="normal" font="default" size="100%">23</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capra, Eugenio</style></author><author><style face="normal" font="default" size="100%">Francalanci, Chiara</style></author><author><style face="normal" font="default" size="100%">Merlo, Francesco</style></author><author><style face="normal" font="default" size="100%">Rossi Lamastra, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Survey on Firms’ Participation in Open Source Community Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Survey on Firns' Participation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">225 - 236</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The role of firms in commercial Open Source projects (e.g., former MySQL, EnterpriseDB, SugarCRM) is a consolidated and generally accepted fact. On other hand, community Open Source projects, which are built upon communities and not directly associated with firms, are commonly perceived to be based mainly on the work of volunteers. Up to now, firms’ role in these projects has been poorly investigated. We conducted a survey on 1,302 SourceForge.net projects to inquire about the level and the typology of involvement of firms. We propose three different models for firm participation and provide empirical evidence on their diffusion in SourceForge.net.
</style></abstract><section><style face="normal" font="default" size="100%">20</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Knowles, Thomas</style></author><author><style face="normal" font="default" size="100%">Munro, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Undergraduate Research Opportunities in OSS</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Undergraduate Research Opportunities.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">340 - 350</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Using Open Source Software (OSS) in undergraduate teaching in universities is now commonplace. Students use OSS applications and systems in their courses on programming, operating systems, DBMS, web development to name but a few. Studying OSS projects from both a product and a process view also forms part of the software engineering curriculum at various universities. Many students have taken part in OSS projects as well as developers. At the University of Lincoln, under the Undergraduate Research Opportunities Scheme (UROS), undergraduate student researchers have the chance to work over the summer embedded within an existing research centre on a UROS project. Here two such projects within the Centre for Research in Open Source Software (CROSS) are described: Collaborative Development for the XO Laptop (CODEX) and Software Modularity in Open Source Software (SoMOSS). The CODEX project focused on creating resources to support students undertaking software application development for the XO laptop, and the SoMOSS project focused on architectural studies of OSS instant messaging software. Both projects achieved successful research outcomes; more importantly, both student researchers benefited directly from the encouragement and concrete assistance that they received through interaction with the wider OSS research community. Both projects are ongoing and present further research opportunities for students.
</style></abstract><section><style face="normal" font="default" size="100%">30</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Squire, Megan</style></author><author><style face="normal" font="default" size="100%">Duvall, Shannon</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using FLOSS Project Metadata in the Undergraduate Classroom</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">artificial intelligence</style></keyword><keyword><style  face="normal" font="default" size="100%">database</style></keyword><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">teaching</style></keyword><keyword><style  face="normal" font="default" size="100%">undergraduate</style></keyword><keyword><style  face="normal" font="default" size="100%">undergraduate research</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Using FLOSS Project Metadata.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">330 - 339</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper describes our efforts to use the large amounts of data available from public repositories of free, libre, and open source software (FLOSS) in our undergraduate classrooms to teach concepts that would have previously been taught using other types of data from other sources.
</style></abstract><section><style face="normal" font="default" size="100%">29</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Noll, John</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What Constitutes Open Source? A Study of the Vista Electronic Medical Record Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/What Constitues Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">310 - 319</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Strictly speaking, Open Source Software is any program that is covered by an Open Source Software license. However, the notion of Open Source Software Development conjures images of high-quality, market dominating products developed by armies of volunteer programmers, who work only for the joy of programming. Certainly, banner projects like Apache, the Linux kernel, and Mozilla/Firefox resemble this notion, even if they do employ significant numbers of paid programmers. This paper examines three Open Source Software projects related to the Vista Electronic Medical Record system developed and maintained by the U.S. Department of Veterans Affairs and released to the public domain. While all three claim to be “Open Source” projects, there is considerable deviation from the strong community-oriented model that Linux, Apache, and Mozilla represent.
</style></abstract><section><style face="normal" font="default" size="100%">27</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fernandez-Ramil, Juan</style></author><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Mens, Tom</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What Does It Take to Develop a Million Lines of Open Source Code?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/What Does it Take to Develop.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">170 - 184</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This article presents a preliminary and exploratory study of the relationship between size, on the one hand, and effort, duration and team size, on the other, for 11 Free/Libre/Open Source Software (FLOSS) projects with current size ranging between between 0.6 and 5.3 million lines of code (MLOC). Effort was operationalised based on the number of active committers per month. The extracted data did not fit well an early version of the closed-source cost estimation model COCOMO for proprietary software, overall suggesting that, at least to some extent, FLOSS communities are more productive than closed-source teams. This also motivated the need for FLOSS-specific effort models. As a first approximation, we evaluated 16 linear regression models involving different pairs of attributes. One of our experiments was to calculate the net size, that is, to remove any suspiciously large outliers or jumps in the growth trends. The best model we found involved effort against net size, accounting for 79 percent of the variance. This model was based on data excluding a possible outlier (Eclipse), the largest project in our sample. This suggests that different effort models may be needed for certain categories of FLOSS projects. Incidentally, for each of the 11 individual FLOSS projects we were able to model the net size trends with very high accuracy (R 2 ≥ 0.98). Of the 11 projects, 3 have grown superlinearly, 5 linearly and 3 sublinearly, suggesting that in the majority of the cases accumulated complexity is either well controlled or don’t constitute a growth constraining factor.
</style></abstract><section><style face="normal" font="default" size="100%">16</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Backlund, Per</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Workshop – Serious Games and Open Source: Practice and Futures</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP Advances in Information and Communication Technology </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Workshop Serious Games and Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">299/2009</style></volume><pages><style face="normal" font="default" size="100%">361 - 362</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Computer games are increasingly used throughout our society with people playing on the bus, at home and at work. Computer games thus affect larger and larger number of people and areas in the society of today. There are even scholars who advocate that games create better environments for learning than traditional classrooms. This situation motivates the use of games and game technology for additional purposes, e.g. education, training, health care or marketing.
</style></abstract><section><style face="normal" font="default" size="100%">36</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Guido Conaldi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Flat for the few, steep for the many: Structural cohesion as  a measure of hierarchy in FLOSS communities</style></title><secondary-title><style face="normal" font="default" size="100%">4th Workshop on Public Data about Software Development (WoPDaSD 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">epiphany</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/guido-conaldi-flat-for-the-few.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">A discrepancy exists between the emphasis posed by practitioners on decentralized and non-hierarchical communication in Free/Libre Open Source Software (FLOSS) communities and empirical evidence of their hierarchical structure. In order to explain this apparent paradox it is here hypothesized that in FLOSS communities local sub-groups exist and are less hierarchical, more decentralized than the whole social network to which they belong. A measure of structural cohesion based on network node connectivity is proposed as an effective method to test whether FLOSS communication networks can be decomposed in nested hierarchies of progressively less centralized sub-groups. Preliminary results from a case study that are consistent with the hypothesis are presented and discussed. </style></abstract><notes><style face="normal" font="default" size="100%">&quot;The FLOSS project selected as case study is the GNOME web browser Epiphany. The communication network was  generated tracing backwards mail threads in the development mailing list. &quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wray, Barry</style></author><author><style face="normal" font="default" size="100%">Mathieu, Richard</style></author><author><style face="normal" font="default" size="100%">Teets, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying How Determinants Impact Security-Based Open Source Software Project Success Using Rule Induction</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Electronic Marketing and Retailing</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">2</style></volume><pages><style face="normal" font="default" size="100%">352-362</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Krein, Jonathan L.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Eggett, Dennis L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Language entropy: A metric for characterization of author programming language distribution</style></title><secondary-title><style face="normal" font="default" size="100%">4th Workshop on Public Data about Software Development (WoPDaSD 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">language entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">multiple languages</style></keyword><keyword><style  face="normal" font="default" size="100%">programming languages</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/LanguageEntropy-JonathanKrein.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">Programmers are often required to develop in multiple languages. In an eﬀort to study the eﬀects of programming language fragmentation on productivity—and ultimately on a programmer’s problem solving abilities—we propose a metric, language entropy, for characterizing the distribution of an individual’s development eﬀorts across multiple programming languages. To evaluate this metric, we present an observational study examining all project contributions (through August 2006) of a random sample of 500 SourceForge developers. Using a random coeﬃcients model, we found a statistically signiﬁcant correlation (alpha level of 0.05) between language entropy and the size of monthly pro ject contributions (measured in lines of code added). Our results indicate that language entropy is a good candidate for characterizing author programing language distribution.</style></abstract><notes><style face="normal" font="default" size="100%">The data set used in this study was previously collected for a separate, but related work. It was originally extracted from the SourceForge Research Archive (SFRA), August 2006. For a detailed discussion of the data source, collection tools and processes, and summary statistics, see [6].&quot;

&quot;From the initial data set we extracted a random sample of 500 developers3 along with descriptive details of all revisions that those developers made since the inception of the projects on which they worked. We then condensed this sample by totaling the lines of code added by each developer for each month in which that developer made at least one code submission.&quot;
[6] Daniel P. Delorey, Charles D. Knutson, and Alex MacLean. Studying production phase sourceforge projects: A case study using cvs2mysql and sfra+. In Second International Workshop on Public Data about Software Development (WoPDaSD ’07), June 2007.</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sen, S.</style></author><author><style face="normal" font="default" size="100%">Vig, J.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Learning to Recognize Valuable Tags</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Intelligent User Interfaces</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2/8/2009</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ekstrand, M.D.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.T.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">rv you're dumb: Identifying Discarded Work in Wiki Article History</style></title><secondary-title><style face="normal" font="default" size="100%">The Fifth International Symposium on Wiki's and Open Collaboration</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/25/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Orlando, FL</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Halfaker, A.</style></author><author><style face="normal" font="default" size="100%">Kittur, N.</style></author><author><style face="normal" font="default" size="100%">Kraut, R.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Jury of Your Peers: Quality, Experience and Ownership in Wikipedia</style></title><secondary-title><style face="normal" font="default" size="100%">The International Symposium on Wiki's and Open Collaboration</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">experience,</style></keyword><keyword><style  face="normal" font="default" size="100%">ownership,</style></keyword><keyword><style  face="normal" font="default" size="100%">peer</style></keyword><keyword><style  face="normal" font="default" size="100%">peer,</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">review,</style></keyword><keyword><style  face="normal" font="default" size="100%">wikipedia,</style></keyword><keyword><style  face="normal" font="default" size="100%">wikiwork,</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Orlando, FL</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alspaugh, Thomas</style></author><author><style face="normal" font="default" size="100%">Hazeline U. Asuncion</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Intellectual Property Rights Requirements for Heterogeneously Licensed Systems</style></title><secondary-title><style face="normal" font="default" size="100%">17th Internnational Conference on Requirements Engineering (RE09)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">09/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Atlanta, GA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alspaugh, Thomas</style></author><author><style face="normal" font="default" size="100%">Hazeline U. Asuncion</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Role of Software Licenses in Open Architecture Ecosystems</style></title><secondary-title><style face="normal" font="default" size="100%">International Workshop on Software Ecosystems, in conjunction with the  International Conference on Software Reuse</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">09/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Falls Church, VA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mehrdad Nurolahzade</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Seyed Mehdi Nasehi</style></author><author><style face="normal" font="default" size="100%">Shahedul Huq Khandkar</style></author><author><style face="normal" font="default" size="100%">Shreya Rawal</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">The role of patch review in software evolution: an analysis of the mozilla firefox</style></title><secondary-title><style face="normal" font="default" size="100%">The joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">inspection</style></keyword><keyword><style  face="normal" font="default" size="100%">open source development</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">08/2009</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://ase.cpsc.ucalgary.ca/ase/uploads/Publications/iwpse31-nurolahzade.pdf</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Amsterdam, The Netherlands</style></pub-location><pages><style face="normal" font="default" size="100%">9-18</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-678-6</style></isbn><abstract><style face="normal" font="default" size="100%">Patch review is the basic mechanism for validating the design and implementation of patches and maintaining consistency in some commercial and Free/Libre/Open Source Software (FLOSS) projects. We examine the inner-workings of the development process of the successful and mature Mozilla foundation and highlight how different parties involved affect and steer the process. Although reviewers are the primary actors in the patch review process, success in the process can only be achieved if the community supports reviewers adequately. Peer developers play the supporting role by offering insight and ideas that help create more quality patches. Moreover, they reduce the huge patch backlog reviewers have to clear by identifying and eliminating immature patches.</style></abstract><work-type><style face="normal" font="default" size="100%">Paper in Conference Proceedings</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wohed, P.</style></author><author><style face="normal" font="default" size="100%">ter Hofstede, A.H.M.</style></author><author><style face="normal" font="default" size="100%">Russell, N.</style></author><author><style face="normal" font="default" size="100%">Andersson, B.</style></author><author><style face="normal" font="default" size="100%">van der Aalst, W.M.P</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On the Maturity of Open Source BPM Systems</style></title><secondary-title><style face="normal" font="default" size="100%">BP Trends</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/bpm.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">(11 pages)</style></pages><abstract><style face="normal" font="default" size="100%">Two major trends in the area of information systems development are the growing interest for Workflow and Busi- ness Process Management (BPM) systems and the increasing acceptance and spread of open source software. This development raises the following questions:
1. What are the prominent representatives of current open source Workflow and BPM systems? 2. What is the maturity level of these systems?
Seeking answers to these questions we have performed a study. First an overview of the existing open source systems was made and three systems: jBPM, OpenWFE, and Enhydra Shark, selected for further analysis. Then a detailed analysis on the selected systems was performed. The results from this analysis were documented and the developers invited to comment. Based on the feedback from the developers the results were revisited and the study finalized [5]. In this article we summarise the study and reflect on the area of open source BPM systems.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Figure 1 shows a snapshot (from 3rd of July 2008) of the most downloaded workflow and BPM systems distributed through a code repository. The systems in the figure are ordered historically with respect to month and year of their registration. The code repositories searched for this snapshot were SourceForge, RubyForge, ObjectWebForge, Tigris.org, BountySource, BerliOS, JavaForge and GNU Savannah&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alspaugh, Thomas</style></author><author><style face="normal" font="default" size="100%">Hazeline U. Asuncion</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analyzing Software Licenses in Open Architecture Software Systems</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the  Workshop on Emerging Trends in FLOSS Research and Development</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Vancouver, Canada</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stefan Theußl</style></author><author><style face="normal" font="default" size="100%">Achim Zeileis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaborative Software Development Using R-Forge</style></title><secondary-title><style face="normal" font="default" size="100%">The R Journal</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">R</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">statistics</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/rjournal.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">9-14</style></pages><abstract><style face="normal" font="default" size="100%">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’s “release early, release often paradigm”). 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 Zü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’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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alspaugh, Thomas</style></author><author><style face="normal" font="default" size="100%">Hazeline U. Asuncion</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Licenses, Open Source Components, and Open Architectures</style></title><secondary-title><style face="normal" font="default" size="100%">Sixth Annual Acquisition Research Symposium</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Monterey, CA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lam, S.K.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Is Wikipedia Growing a Longer Tail?</style></title><secondary-title><style face="normal" font="default" size="100%">ACM 2009 International Conference on Supporting Group Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/10/2009</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Association for Computing Machinery</style></publisher><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Reily, K.</style></author><author><style face="normal" font="default" size="100%">Finnerty, P.L.</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Two peers are better than one: aggregating peer reviews for computing assignments is surprisingly accurate</style></title><secondary-title><style face="normal" font="default" size="100%">ACM 2009 International Conference on Supporting Group Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/10/2009</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Association for Computing Machinery</style></publisher><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><pages><style face="normal" font="default" size="100%">115-124</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-500-0 </style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Panciera, K.</style></author><author><style face="normal" font="default" size="100%">Halfaker, A.</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Wikipedians are born, not made: a study of power editors on Wikipedia</style></title><secondary-title><style face="normal" font="default" size="100%">ACM 2009 International Conference on Group Work</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">computer-supported</style></keyword><keyword><style  face="normal" font="default" size="100%">cooperative</style></keyword><keyword><style  face="normal" font="default" size="100%">interaction</style></keyword><keyword><style  face="normal" font="default" size="100%">web-based</style></keyword><keyword><style  face="normal" font="default" size="100%">work,</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/10/2009</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Association for Computing Machinery</style></publisher><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><pages><style face="normal" font="default" size="100%">51-60</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chen, J</style></author><author><style face="normal" font="default" size="100%">Nairn, R.</style></author><author><style face="normal" font="default" size="100%">Nelson, L.</style></author><author><style face="normal" font="default" size="100%">Bernstein, M.</style></author><author><style face="normal" font="default" size="100%">Chi, E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Short and Tweet: Experiments on Recommending Content from Information</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 28th annual conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/10/10</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">Atlanta, GA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sandeep Krishnamurthy</style></author><author><style face="normal" font="default" size="100%">Tripathi, Arvind K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Monetary donations to an open source software platform</style></title><secondary-title><style face="normal" font="default" size="100%">Research Policy</style></secondary-title><short-title><style face="normal" font="default" size="100%">Research Policy</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Collective action</style></keyword><keyword><style  face="normal" font="default" size="100%">Donation</style></keyword><keyword><style  face="normal" font="default" size="100%">Identification</style></keyword><keyword><style  face="normal" font="default" size="100%">incentives</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">Open source software platform</style></keyword><keyword><style  face="normal" font="default" size="100%">projects</style></keyword><keyword><style  face="normal" font="default" size="100%">Reciprocity</style></keyword><keyword><style  face="normal" font="default" size="100%">Relational commitment</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">03/2009</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">38</style></volume><pages><style face="normal" font="default" size="100%">404 - 414</style></pages><abstract><style face="normal" font="default" size="100%">Online open source software platforms, such as Sourceforge.net, play a vital role in creating an ecosystem that enables the creation and growth of open source projects. However, there is little research exploring the interactions between open source stakeholders and the platform. We believe that the sustainability of the platform crucially depends on financial incentives. While platforms can obtain these incentives through multiple means, in this paper we focus on one form of financial incentives—voluntary monetary donations by open source community members. We report findings from two empirical studies that examine factors that impact donations. Study 1 investigates the factors that cause some community members to donate and not others. We find that the decision to donate is impacted by relational commitment with open source software platform, donation to projects and accepting donations from others. Study 2 examines what drives the level of donation. We find that the length of association with the platform and relational commitment affects donation levels.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bach, Paula</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design Information Sharing Across Multiple Knowledge Systems in a FLOSS Community</style></title><secondary-title><style face="normal" font="default" size="100%">iConference '09</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">codeplex</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">information sharing</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">02/2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/finalDraft41.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">This paper explores support for design information sharing between the distinct knowledge systems and skill sets of interactive system designers and developers. The paper focuses on the challenges of sharing information among groups of designers, developers, and users with multiple knowledge systems in the context of free/libre/open source software (FLOSS) communities. Bringing design to FLOSS communities introduces new knowledge into a solitary community of practice, and discussion ensues about how exploiting the 'symmetry of ignorance' can enhance information sharing through design in CodePlex, an open source project hosting community website. Finally, design mockups illustrate how CodePlex serves as a boundary object supporting design information sharing across distinct knowledge systems.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Vig, J.</style></author><author><style face="normal" font="default" size="100%">Sen, S.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Tagsplanations: Explaining Recommendations using Tags</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Intelligent User Interfaces</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">recommender</style></keyword><keyword><style  face="normal" font="default" size="100%">SYSTEMS</style></keyword><keyword><style  face="normal" font="default" size="100%">tagging,</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">02/08/2009</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fitzgerald, Brian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Adoption: Anatomy of Success and Failure</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">adoption</style></keyword><keyword><style  face="normal" font="default" size="100%">project failure</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2009</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">1-23</style></pages><abstract><style face="normal" font="default" size="100%">Current estimates suggest widespread adoption of open source software (OSS) in organizations worldwide. However, the problematic nature of OSS adoption is readily evidenced in the fairly frequent reports of problems, unforeseen hold-ups, and outright abandonment of OSS implementation over time. Hibernia Hospital, an Irish public sector organization, have embarked on the adoption of a range of OSS applications over several years, some of which have been successfully deployed and remain in live use within the organisation, whereas others, despite achieving high levels of assimilation over a number of years, have not been ultimately retained in live use in the organization. Using a longitudinal case study, we discuss in depth the deployment process for two OSS applications – the desktop application suite whose deployment was unsuccessful ultimately, and the email application which was successfully deployed. To our knowledge, this is the first such in-depth study into successful and unsuccessful OSS implementation.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yilmaz, Levent</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Agent Simulation Study on Conflict, Community Climate and Innovation in Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">1 - 25</style></pages><abstract><style face="normal" font="default" size="100%">More than ever the complexity of innovation requires group efforts, as teams of scientists and engineers from diverse backgrounds work together to solve problems. One of the significant problems in understanding emergence of innovation involves how virtual innovation organizations and communities govern and coordinate to maximize innovation output. An agent simulation study is conducted to examine the impact of culture and conflict management styles on collective creativity in open source innovation systems. Findings suggest that decentralized coordination schemes such as emergent selection such as found in utility communities and moderate degrees of assertiveness and cooperation for conflict management result in higher incidence of innovation.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matter, Dominique</style></author><author><style face="normal" font="default" size="100%">Kuhn, Adrian</style></author><author><style face="normal" font="default" size="100%">Nierstrasz, Oscar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assigning bug reports using a vocabulary-based expertise model of developers</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">develect</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/131AssigningBugReports.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">131 - 140</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6% top-1 precision and 71.0% top-10 recall.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Casebolt, Jason R.</style></author><author><style face="normal" font="default" size="100%">Krein, Jonathan L.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Author entropy vs. file size in the GNOME suite of applications</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">author entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">91 - 94</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">We present the results of a study in which author entropy was used to characterize author contributions per file. Our analysis reveals three patterns: banding in the data, uneven distribution of data across bands, and file size dependent distributions within bands. Our results suggest that when two authors contribute to a file, large files are more likely to have a dominant author than smaller files.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kuhn, Adrian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Automatic labeling of software components and their evolution using log-likelihood ratio of word frequencies in source code</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">frequency</style></keyword><keyword><style  face="normal" font="default" size="100%">hapax</style></keyword><keyword><style  face="normal" font="default" size="100%">information retrieval</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">junit</style></keyword><keyword><style  face="normal" font="default" size="100%">keywords</style></keyword><keyword><style  face="normal" font="default" size="100%">labeling</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/175AutomaticLabeling.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">175 - 178</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">As more and more open-source software components become available on the Internet we need automatic ways to label and compare them. For example, a developer who searches for reusable software must be able to quickly gain an understanding of retrieved components. This understanding cannot be gained at the level of source code due to the semantic gap between source code and the domain model. In this paper we present a lexical approach that uses the log-likelihood ratios of word frequencies to automatically provide labels for software components. We present a prototype implementation of our labeling/comparison algorithm and provide examples of its application. In particular, we apply the approach to detect trends in the evolution of a software system.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Di Penta, Massimiliano</style></author><author><style face="normal" font="default" size="100%">Gueheneuc, Yann-Gael</style></author><author><style face="normal" font="default" size="100%">Antoniol, Giuliano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Code siblings: Technical and legal implications of copying code between applications</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bsd</style></keyword><keyword><style  face="normal" font="default" size="100%">fossology</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">openbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/81CodeSiblings.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">81 - 90</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Görkem Çetin</style></author><author><style face="normal" font="default" size="100%">Göktürk, Mehmet</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaboration in Open Source Domains</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">17 - 28</style></pages><abstract><style face="normal" font="default" size="100%">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’ 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</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Arafat, O.</style></author><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Commit Size Distribution of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">commits</style></keyword><keyword><style  face="normal" font="default" size="100%">configuration management</style></keyword><keyword><style  face="normal" font="default" size="100%">history</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-07.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikoloa, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 8</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We use the database of the open source analytics firm Ohloh Inc.&quot;
&quot;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.&quot;
&quot;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.&quot;
&quot;We measure the size of commits in this paper in source lines of code (SLoC) using Ohloh's own open source diff too&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hinds, David</style></author><author><style face="normal" font="default" size="100%">Lee, Ronald M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Communication Network Characteristics of Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">26 - 48</style></pages><abstract><style face="normal" font="default" size="100%">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—the open source software project community—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.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gaudeul, Alexia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Consumer Welfare and Market Structure in a Model of Competition between Open Source and Proprietary Software</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">43 - 65</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Cost Model of Open Source Software Adoption</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">60 - 82</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Iivari, Netta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Discourses on User Participation</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">44 - 59</style></pages><abstract><style face="normal" font="default" size="100%">Users should participate in information technology (IT) artifact development, but it has proven to be challenging. This applies also in the open source software (OSS) development. This chapter critically examines discursive construction of user participation in academic literatures and in practice, in IT artifact development. First three academic discourses constructing user participation are discussed. Then the discursive construction of user participation is explored in OSS development literature. Afterwards, results from several empirical, interpretive case studies are outlined. Some of them have been carried out in the IT artifact product development organizations, others in the OSS development context. Clear similarities can be identified in the discourses constructing user participation in these divergent IT artifact development contexts. The academic discourses on user participation clearly also legitimate certain ways of constructing user participation in practice. The OSS development literature bears resemblance mainly with the Human Computer Interaction (HCI) discourse on user participation. Therefore, it is argued that especially the HCI community should carefully reflect on what kinds of discourses on user participation it advocates and deems as legitimate.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conley, Caryn A.</style></author><author><style face="normal" font="default" size="100%">Lee Sproull</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Easier Said than Done: An Empirical Investigation of Software Design and Quality in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">modularity</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/09-14-05.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Los Alamitos, CA, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">We empirically examine the relationship between software design modularity and software quality in open source software (OSS) development projects. Conventional wisdom suggests that degree of software modularity affects software quality. An analysis of 203 software releases in 46 OSS projects hosted on SourceForge.net lends support for a more complex relationship between software modularity and software quality than conventional wisdom suggests. We find that software modularity is associated with reduced software complexity, an increased number of static software bugs, and a mixed relationship with the percentage of bugs closed. We do not find empirical evidence supporting any relationship between modularity and other measures of customer satisfaction. In addition to empirically testing the relationship between modularity and quality, we introduce new measures of software modularity and software quality. Implications are developed for the theory of modularity and the practice of software development.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;projects that do not exhibit obvious corporate or organizational sponsorship or involvement, projects with at least one software release in a relatively mature development stage (Beta or Production/Stable), projects exhibiting a minimum level of project activity, and products written only using Java.&quot;
&quot;The frame includes approximately 180 projects from which a random sample of 46 was drawn&quot;
&quot;For each project, we sample each major software release (e.g. 1.x, 2.x) as our unit of analysis for a total of 203 releases.&quot;
&quot;We calculate the degree of modularity for each major software release sampled using the source code contained in each release&quot;
&quot;To measure intrinsic software quality, we calculate the number of static bugs and software complexity based on objective evaluations of the source code included in the software release using two static source code analysis tools&quot;
&quot;To assess customer satisfaction, we use three measures of software quality previously identified in OSS research as a proxy for software quality and OSS project success [3]: number of bugs reported, percentage of bugs closed, and time to close bugs.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jing Wu</style></author><author><style face="normal" font="default" size="100%">Khim Yong Goh</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating Longitudinal Success of Open Source Software Projects: A Social Network Perspective</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">communication</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/09-02-12.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Los Alamitos, CA, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">To date, numerous open source projects are hosted on many online repositories. While some of these projects are active and thriving, some projects are either languishing or showing no development activities at all. This phenomenon thus begs the important question of what are the influential factors that affect the success of open source projects. In a quest to deepen our understanding of the evolution of open source projects, this research aims to analyze the success of open source projects by using the theoretical lens of social network analysis. Based on extensive analyses of data collected from online repositories, we study the impact of the communication patterns of software development teams on the demand and supply outcomes of these projects, while accounting for project-specific characteristics. Using panel data analysis of data over 13 months, we find significant impacts of communication patterns on project outcomes over the long term.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We collect data of various OSS projects over an extended period of 13 months and utilize cross-sectional time-series panel data analysis methods...&quot;
&quot;we observe and analyze the developers' interactions through bug, patch, support request, and feature request (BPSF) tracking systems hosted on SourceForge.net&quot;
&quot;Three criteria are adopted to select useful projects: projects are selected from top 7000 ranked projects; projects have at least three developers; and there are enough interactions to ensure that each sociomatrix is equal to or larger than 3×3 matrix...&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schackmann, Holger</style></author><author><style face="normal" font="default" size="100%">Lichter, Horst</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating process quality in GNOME based on change request data</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzillametrics.org</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">qmetric</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/95ProcessQualityInGNOME.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">95 - 98</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">The lifecycle of defects reports and enhancement requests collected in the Bugzilla database of the GNOME project provides valuable information on the evolution of the change request process and for the assessment of process quality in the GNOME sub projects. We present a quality model for the analysis of quality characteristics that is based on evaluating metrics on the Bugzilla database, and illustrate it with a comparative evaluation for 25 of the largest products within GNOME.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution of the core team of developers in libre software projects</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">gimp</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/167core-evolution.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">167 - 170</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">In many libre (free, open source) software projects, most of the development is performed by a relatively small number of persons, the &quot;core team&quot;. The stability and permanence of this group of most active developers is of great importance for the evolution and sustainability of the project. In this position paper we propose a quantitative methodology to study the evolution of core teams by analyzing information from source code management repositories. The most active developers in different periods are identified, and their activity is calculated over time, looking for core team evolution patterns.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Namjoo Choi</style></author><author><style face="normal" font="default" size="100%">Chengular-Smith, I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Exploratory Study on the Two New Trends in Open Source Software: End-Users and Service</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">intended audiences</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-05.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikoloa, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">Many have been envisaging the emergence of Open Source Software (OSS) for general end-users and the enhancements in providing services and support, as the most critical factors for OSS success, and at the same time, the most critical issues which are holding back the OSS movement. While these two distinct waves in OSS evolution have become more observable, researchers have not yet explored the characteristics of these two distinct new waves. The current study found evidence for these two waves and further explored the two waves by empirically examining two hundred projects hosted in Sourceforge.net. We compared the characteristics of OSS projects that are intended for two disparate audiences: developers and end-users and found that projects for end-users supported more languages but also had more restrictive licenses as compared to projects for developers.</style></abstract><notes><style face="normal" font="default" size="100%">used sourceforge data
&quot;We created our dataset by restricting our attention to projects that have production/stable and mature development status&quot;
&quot;we limited our sample to two categories: developers and end-users/desktop&quot;
&quot;We manually compiled a total of 200 projects, 100 each of the most downloaded projects from developers and end-users/desktop categories during the period of March 4 to March 23, 2008. &quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Elpern, Jeff</style></author><author><style face="normal" font="default" size="100%">Dascalu, Sergiu</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Framework for Understanding the Open Source Revolution</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">1 - 16</style></pages><abstract><style face="normal" font="default" size="100%">Traditional software engineering methodologies have mostly evolved from the environment of proprietary, large-scale software systems. Here, software design principles operate within a hierarchical decision-making context. Development of banking, enterprise resource and complex weapons systems all fit this paradigm. However, another paradigm for developing software-intensive systems has emerged, the paradigm of open source software. Although from a traditional perspective open source projects might look like chaos, their real-world results have been spectacular. This chapter presents open source software development as a fundamentally new paradigm driven by economics and facilitated by new processes. The new paradigm's revolutionary aspects are explored, a framework for describing the massive impact brought about by the new paradigm is proposed, and directions of future research are outlined. The proposed framework's goals are to help the understanding of the open source paradigm as a new economic revolution and stimulate research in designing open source software.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maalej, Walid</style></author><author><style face="normal" font="default" size="100%">Happel, Hans-Jorg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From work to word: How do software developers describe their work?</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">diaries</style></keyword><keyword><style  face="normal" font="default" size="100%">eureka</style></keyword><keyword><style  face="normal" font="default" size="100%">mycomp</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">work management system</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">121 - 130</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Developers take notes about their work sessions, either to remember the work status and share it with collaborators, or because employers explicitly require this for project management matters. We report on an exploratory study which aims at understanding how software developers describe their work. We analyzed more than 750,000 work descriptions of about 2,000 professionals taken over 8 years in three settings. We observed several similarities in the content and time meta-data of work descriptions. Most frequent terms, such as top-30 performed activities, are used consistently. Particular templates such as ldquoACTION concerning ARTIFACT because of CAUSErdquo occur frequently. Developers described sessions that last 30-120 min. 4-16 times a day. Maintaining diaries seems to consume between 3-6% of the total work time, and in 10% of the sessions, developers did not describe their work in sufficient detail. We argue that our results make the first step towards automatically generating work diaries for software developers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Karl Beecher</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying exogenous drivers and evolutionary stages in FLOSS projects</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of Systems and Software</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">forges</style></keyword><keyword><style  face="normal" font="default" size="100%">repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">success</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V0N-4TVTJFS-1/2/e32ecee1bcb54bd4a5dff6d5e3daca8d</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">5</style></number><volume><style face="normal" font="default" size="100%">82</style></volume><pages><style face="normal" font="default" size="100%">739 - 750</style></pages><abstract><style face="normal" font="default" size="100%">The success of a Free/Libre/Open Source Software (FLOSS) project has been evaluated in the past through the number of commits made to its configuration management system, number of developers and number of users. Most studies, based on a popular FLOSS repository (SourceForge), have concluded that the vast majority of projects are failures. This study's empirical results confirm and expand conclusions from an earlier and more limited work. Not only do projects from different repositories display different process and product characteristics, but a more general pattern can be observed. Projects may be considered as early inceptors in highly visible repositories, or as established projects within desktop-wide projects, or finally as structured parts of FLOSS distributions. These three possibilities are formalized into a framework of transitions between repositories. The framework developed here provides a wider context in which results from FLOSS repository mining can be more effectively presented. Researchers can draw different conclusions based on the overall characteristics studied about an Open Source software project's potential for success, depending on the repository that they mine. These results also provide guidance to OSS developers when choosing where to host their project and how to distribute it to maximize its evolutionary success.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Pollock, Rufus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Innovation, Imitation and Open Source</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">28 - 42</style></pages><abstract><style face="normal" font="default" size="100%">An extensive empirical literature indicates that, even without formal intellectual property rights, innovators enjoy a variety of first-mover advantages and that ‘imitation’ is itself a costly activity. There is also accumulating evidence that an ‘open’ approach to knowledge production can deliver substantial efficiency advantages. This article introduces a formal framework incorporating all of these factors. We examine the relative performance of an ‘open’ versus a ‘closed’ (proprietary) regime, and explicitly characterize the circumstances in which an open approach, despite its effect on facilitating imitation, results in a higher level of innovation.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ayewah, Nathaniel</style></author><author><style face="normal" font="default" size="100%">Pugh, William</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Learning from defect removals</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">cherry</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">groovy</style></keyword><keyword><style  face="normal" font="default" size="100%">launching</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword><keyword><style  face="normal" font="default" size="100%">text editor</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/179LearnFromDefects-MSR09.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">179 - 182</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Recent research has tried to identify changes in source code repositories that fix bugs by linking these changes to reports in issue tracking systems. These changes have been traced back to the point in time when they were previously modified as a way of identifying bug introducing changes. But we observe that not all changes linked to bug tracking systems are fixing bugs; some are enhancing the code. Furthermore, not all fixes are applied at the point in the code where the bug was originally introduced. We flesh out these observations with a manual review of several software projects, and use this opportunity to see how many defects are in the scope of static analysis tools.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiyi Shang</style></author><author><style face="normal" font="default" size="100%">Zhen Ming Jiang</style></author><author><style face="normal" font="default" size="100%">Adams, Bram</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">MapReduce as a general framework to support research in Mining Software Repositories (MSR)</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">hadoop</style></keyword><keyword><style  face="normal" font="default" size="100%">mapreduce</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/21MSR2009-MSR-0114-Shang-Weiyi.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">21 - 30</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Researchers continue to demonstrate the benefits of Mining Software Repositories (MSR) for supporting software development and research activities. However, as the mining process is time and resource intensive, they often create their own distributed platforms and use various optimizations to speed up and scale up their analysis. These platforms are project-specific, hard to reuse, and offer minimal debugging and deployment support. In this paper, we propose the use of MapReduce, a distributed computing platform, to support research in MSR. As a proof-of-concept, we migrate J-REX, an optimized evolutionary code extractor, to run on Hadoop, an open source implementation of MapReduce. Through a case study on the source control repositories of the Eclipse, BIRT and Datatools projects, we demonstrate that the migration effort to MapReduce is minimal and that the benefits are significant, as running time of the migrated J-REX is only 30% to 50% of the original J-REX's. This paper documents our experience with the migration, and highlights the benefits and challenges of the MapReduce framework in the MSR community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bajracharya, Sushil</style></author><author><style face="normal" font="default" size="100%">Lopes, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining search topics from a code search engine usage log</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">black duck</style></keyword><keyword><style  face="normal" font="default" size="100%">koders</style></keyword><keyword><style  face="normal" font="default" size="100%">log</style></keyword><keyword><style  face="normal" font="default" size="100%">logfile</style></keyword><keyword><style  face="normal" font="default" size="100%">search</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">111 - 120</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">We present a topic modeling analysis of a year long usage log of Koders, one of the major commercial code search engines. This analysis contributes to the understanding of what users of code search engines are looking for. Observations on the prevalence of these topics among the users, and on how search and download activities vary across topics, leads to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. The findings support the conclusion that existing code search engines provide only a subset of the various information needs of the users when compared to the categories of queries they look at.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Enslen, Eric</style></author><author><style face="normal" font="default" size="100%">Hill, Emily</style></author><author><style face="normal" font="default" size="100%">Pollock, Lori</style></author><author><style face="normal" font="default" size="100%">Vijay-Shanker, K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining source code to automatically split identifiers for software analysis</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">samurai</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/71EnslenandHillandPollockandVijayShanker.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">71 - 80</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Automated software engineering tools (e.g., program search, concern location, code reuse, quality assessment, etc.) increasingly rely on natural language information from comments and identifiers in code. The first step in analyzing words from identifiers requires splitting identifiers into their constituent words. Unlike natural languages, where space and punctuation are used to delineate words, identifiers cannot contain spaces. One common way to split identifiers is to follow programming language naming conventions. For example, Java programmers often use camel case, where words are delineated by uppercase letters or non-alphabetic characters. However, programmers also create identifiers by concatenating sequences of words together with no discernible delineation, which poses challenges to automatic identifier splitting. In this paper, we present an algorithm to automatically split identifiers into sequences of words by mining word frequencies in source code. With these word frequencies, our identifier splitter uses a scoring technique to automatically select the most appropriate partitioning for an identifier. In an evaluation of over 8000 identifiers from open source Java programs, our Samurai approach outperforms the existing state of the art techniques.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Linstead, Erik</style></author><author><style face="normal" font="default" size="100%">Baldi, Pierre</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining the coherence of GNOME bug reports with statistical topic models</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">sourcerer</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">99 - 102</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">We adapt latent Dirichlet allocation to the problem of mining bug reports in order to define a new information-theoretic measure of coherence. We then apply our technique to a snapshot of the GNOME Bugzilla database consisting of 431,863 bug reports for multiple software projects. In addition to providing an unsupervised means for modeling report content, our results indicate substantial promise in applying statistical text mining algorithms for estimating bug report quality. Complete results are available from our supplementary materials Web site at http://sourcerer.ics.uci.edu/msr2009/gnome_coherence.html.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Allyn, Mark R.</style></author><author><style face="normal" font="default" size="100%">Misra, Ram B.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Motivation of Open Source Developers</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">65 - 81</style></pages><abstract><style face="normal" font="default" size="100%">The motivational drivers of open source software developers have been researched by various investigators since about 2000. This work shows that developers are motivated by different extrinsic and intrinsic drivers, among them community aspirations, reciprocity and fairness, creative impulses, and monetary and career ambitions. There has been some work done in studying whether the profile of developer motivations is constant across open source projects or is sensitive to project organizational design. Among the many factors that could influence the mix of motives of OS developers is the license under which the work is performed. Licenses range in openness between those such as the GNU GPL that severely restrict the freedom of developers to mingle their OS code with proprietary code to those such as BSD licenses which allow programmers much greater latitude in integrating open source code with proprietary code. In addition to formal rules, meritocracies emerge to reward effort and performance, and also to direct, coordinate, and control other participants. The authors discuss these variables and how they may be related to motivations.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">de Sousa, S.F.</style></author><author><style face="normal" font="default" size="100%">Balieiro, M.A.</style></author><author><style face="normal" font="default" size="100%">dos R. Costa, J.M.</style></author><author><style face="normal" font="default" size="100%">de Souza, C.R.B.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Multiple Social Networks Analysis of FLOSS Projects using Sargas</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">multiple social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">ossnetwork</style></keyword><keyword><style  face="normal" font="default" size="100%">pmd</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">transflow</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-06.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikoloa, Hawaii, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1 - 10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">Due to their characteristics and claimed advantages, several researchers have been investigating free and open-source projects. Different aspects are being studied: for instance, what motivates developers to join FLOSS projects, the tools, processes and practices used in FLOSS projects, the evolution of FLOSS communities among other things. Researchers have studied collaboration and coordination of open source software developers using an approach known as social network analysis and have gained important insights about these projects. Most researchers, however, have not focused on the integrated study of these networks and, accordingly, in their interrelationships. This paper describes an approach and tool to combine multiple social networks to study the evolution of open-source projects. Our tool, named Sargas, allows comparison and visualization of different social networks at the same time. Initial results of our analysis can be used to extend the &quot;onion-model&quot; of open source participation.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;The interval of analysis for the first three networks was from 2003/02/24 to 2003/11/03. These networks were created using the OSSNetwork tool [18]. The source code of the PMD project was collected starting on 2002/06/24...&quot;
&quot;Transflow performs a co-changes analysis of the source code modification history and creates a matrix where software components are connected by taking into account the frequency that they have been changed together (i.e., in the same check-in): if two files have been changed together in the same check-in, an edge is created to link these two files.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Anbalagan, Prasanth</style></author><author><style face="normal" font="default" size="100%">Vouk, Mladen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On mining data across software repositories</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">Fedora</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">htmlscraper</style></keyword><keyword><style  face="normal" font="default" size="100%">integration</style></keyword><keyword><style  face="normal" font="default" size="100%">launchpad</style></keyword><keyword><style  face="normal" font="default" size="100%">national vulnerability database</style></keyword><keyword><style  face="normal" font="default" size="100%">RedHat</style></keyword><keyword><style  face="normal" font="default" size="100%">Suse</style></keyword><keyword><style  face="normal" font="default" size="100%">tracker</style></keyword><keyword><style  face="normal" font="default" size="100%">Ubuntu</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/171MiningAcrossmsr09.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">171 - 174</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Software repositories provide abundance of valuable information about open source projects. With the increase in the size of the data maintained by the repositories, automated extraction of such data from individual repositories, as well as of linked information across repositories, has become a necessity. In this paper we describe a framework that uses web scraping to automatically mine repositories and link information across repositories. We discuss two implementations of the framework. In the first implementation, we automatically identify and collect security problem reports from project repositories that deploy the Bugzilla bug tracker using related vulnerability information from the National Vulnerability Database. In the second, we collect security problem reports for projects that deploy the Launchpad bug tracker along with related vulnerability information from the National Vulnerability Database. We have evaluated our tool on various releases of Fedora, Ubuntu, Suse, RedHat, and Firefox projects. The percentage of security bugs identified using our tool is consistent with that reported by other researchers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Shihab, Emad</style></author><author><style face="normal" font="default" size="100%">Zhen Ming Jiang</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On the use of Internet Relay Chat (IRC) meetings by developers of the GNOME GTK+ project</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">gtk</style></keyword><keyword><style  face="normal" font="default" size="100%">irc</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/107MSR2009-MSR-0130-Shihab-Emad.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">107 - 110</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Developers of open source projects are distributed across the world. They rely on email, mailing lists, instant messaging, IRC channels and more recently IRC meetings to communicate. Most of the studies thus far focus on the use of mailing lists by OSS developers, however, an increasing number of open source projects are using IRC meetings to hold developer meetings. In this paper, we mine the #gtk-devel IRC meeting channel and study the usage of the IRC meetings held by the GNOME GTK+ core developers and maintainers. We look at three different dimensions: the discussion volume of the meetings, the number of participants attending the meetings and the activity of these participants. Our findings show that IRC meetings are gaining popularity among open source developers and maintainers: the IRC meeting discussions are increasing in volume, have increasing attendance levels, and the participants actively contribute to the meetings. To the best of our knowledge, this is the first study on the use of developer IRC meetings by OSS developers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rastkar, Sarah</style></author><author><style face="normal" font="default" size="100%">Murphy, Gail C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On what basis to recommend: Changesets or interactions?</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">changeset</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">mylyn</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">155 - 158</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Different flavours of recommendation systems have been proposed to help software developers perform software evolution tasks. A number of these recommendation systems are based on changesets. When changeset information is used, recommendations are based on only the end result of the activity undertaken to complete a task. In this paper, we report on an investigation that compared how recommendations based on changesets compare to recommendations based on interactions collected as a programmer performed the task that resulted in a changeset. To provide a common basis for the comparison, our investigation considered how bug reports considered similar based on changeset information compare to bug reports considered similar based on interaction information. We found that there is no direct relationship between the bug reports found similar with the different methods, suggesting that each comparison methods captures a different aspect of the problem.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Darmon, Eric</style></author><author><style face="normal" font="default" size="100%">Torre, Dominique</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source and Commercial Software Platforms</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">67 - 80</style></pages><abstract><style face="normal" font="default" size="100%">In this article, we consider the dynamics and competition between two software platforms (Open Source and proprietary software). Potential user-developers can adopt one of the two platforms in order to develop and sell new applications based on the platform. We consider the static issue first and then use a simple dynamic system where the dynamics comes from the development efforts (spillovers) made on each platforms. In this context, we first identify the conditions for the two platforms to coexist in the long run. From this baseline, we then consider different strategies for the editor. A first strategy is for the editor to “show the code” of its software, so as to develop more compatible products. A second strategy is to strategically monitor the compatibility degree between the proprietary and OS platform. In both cases, we analyze whether a mixed industry may be sustainable in the long run.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Le Texier, Thomas</style></author><author><style face="normal" font="default" size="100%">Versailles, David W.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Governance Serving Technological Agility</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">14 - 27</style></pages><abstract><style face="normal" font="default" size="100%">The development of open source software is currently arousing increasing interest in the IT world. This research inquires some specific paths enlarging the traditional view over open source software in inquiring the US Department of Defense (DoD) and the dynamics associated its front- and back-office activities. We explain how distinguishing basic administration from operational constraints and weapon R&amp;D dynamics introduces specific governance concerns among public and private stakeholders. By no longer defining open source solutions as mere goods, but as services characterized by a flow of knowledge, we particularly highlight new emerging strategies of technological acquisition. Our analysis leads to revise the traditional role focusing mainly on cost issues and introduces open source software with distinctive properties serving the management of innovation and technological agility at the level of complex systems, exemplified here with the constraints associated to weapon systems and the Network centric warfare doctrine</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gousios, Georgios</style></author><author><style face="normal" font="default" size="100%">Diomidis Spinellis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A platform for software engineering research</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">alitheia core</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/31gousios.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">31 - 40</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Research in the fields of software quality, maintainability and evolution requires the analysis of large quantities of data, which often originate from open source software projects. Collecting and preprocessing data, calculating metrics, and synthesizing composite results from a large corpus of project artifacts is a tedious and error prone task lacking direct scientific value. The Alitheia Core tool is an extensible platform for software quality analysis that is designed specifically to facilitate software engineering research on large and diverse data sources, by integrating data collection and preprocessing phases with an array of analysis services, and presenting the researcher with an easy to use extension mechanism. Alitheia Core aims to be the basis of an ecosystem of shared tools and research data that will enable researchers to focus on their research questions at hand, rather than spend time on re-implementing analysis tools. In this paper, we present the Alitheia Core platform in detail and demonstrate its usefulness in mining software repositories by guiding the reader through the steps required to execute a simple experiment.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Peter C. Rigby</style></author><author><style face="normal" font="default" size="100%">Earl T. Barr</style></author><author><style face="normal" font="default" size="100%">David J. Hamilton</style></author><author><style face="normal" font="default" size="100%">Daniel M. Germán</style></author><author><style face="normal" font="default" size="100%">Premkumar T. Devanbu</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The promises and perils of mining git</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 6th International Working Conference on Mining Software Repositories, MSR 2009</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">dscm</style></keyword><keyword><style  face="normal" font="default" size="100%">git</style></keyword><keyword><style  face="normal" font="default" size="100%">mining</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/1promisePeril.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">1-10</style></pages><abstract><style face="normal" font="default" size="100%">We are now witnessing the rapid growth of decentralized source code management (DSCM) systems, in which every developer has her own repository. DSCMs facilitate a style of collaboration in which work output can flow sideways (and privately) between collaborators, rather than always up and down (and publicly) via a central repository. Decentralization comes with both the promise of new data and the peril of its misinterpretation. We focus on git, a very popular DSCM used in high-profile projects. Decentralization, and other features of git, such as automatically recorded contributor attribution, lead to richer content histories, giving rise to new questions such as &quot;How do contributions flow between developers to the official project repository?&quot; However, there are pitfalls. Commits may be reordered, deleted, or edited as they move between repositories. The semantics of terms common to SCMs and DSCMs sometimes differ markedly, potentially creating confusion. For example, a commit is immediately visible to all developers in centralized SCMs, but not in DSCMs. Our goal is to help researchers interested in DSCMs avoid these and other perils when mining and analyzing git data.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author><author><style face="normal" font="default" size="100%">Karl Beecher</style></author><author><style face="normal" font="default" size="100%">Paul J. Adams</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality Factors and Coding Standards - a Comparison Between Open Source Forges</style></title><secondary-title><style face="normal" font="default" size="100%">Electronic Notes in Theoretical Computer Science</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">artefacts</style></keyword><keyword><style  face="normal" font="default" size="100%">artifacts</style></keyword><keyword><style  face="normal" font="default" size="100%">coding standards</style></keyword><keyword><style  face="normal" font="default" size="100%">coding style</style></keyword><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">forges</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B75H1-4VXDKRV-7/2/abcc2be2c4c3998e4bc9b53473ca2d81</style></url></web-urls></urls><volume><style face="normal" font="default" size="100%">233</style></volume><pages><style face="normal" font="default" size="100%">89 - 103</style></pages><abstract><style face="normal" font="default" size="100%">Enforcing adherence to standards in software development in order to produce high quality software artefacts has long been recognised as best practice in traditional software engineering. In a distributed heterogeneous development environment such those found within the Open Source paradigm, coding standards are informally shared and adhered to by communities of loosely coupled developers. Following these standards could potentially lead to higher quality software. This paper reports on the empirical analysis of two major forges where OSS projects are hosted. The first one, the KDE forge, provides a set of guidelines and coding standards in the form of a coding style that developers may conform to when producing the code source artefacts. The second studied forge, SourceForge, imposes no formal coding standards on developers. A sample of projects from these two forges has been analysed to detect whether the SourceForge sample, where no coding standards are reinforced, has a lower quality than the sample from KDE. Results from this analysis form a complex picture; visually, all the selected metrics show a clear divide between the two forges, but from the statistical standpoint, clear distinctions cannot be drawn amongst these quality related measures in the two forge samples.</style></abstract><notes><style face="normal" font="default" size="100%">Proceedings of the International Workshop on Software Quality and Maintainability (SQM 2008)</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jones, M. Cameron</style></author><author><style face="normal" font="default" size="100%">Michael B Twidale</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Informatics?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings, iConference 2009</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://hdl.handle.net/2142/9600</style></url></web-urls></urls><abstract><style face="normal" font="default" size="100%">The paper proposes the term 'software informatics' to describe research on the individual, collaborative, and social aspects of software production and use, spanning multiple representations of software from design, to source code, to application. It does this with a particular focus on information processes around software development. As more applications are web-based or available online for download and increasing amounts of source code is also available online, the information processes surrounding software are changing the way that software is created, appropriated and redesigned. Traditional distinctions between software developer and end-user are blurring, with software development processes occurring along a continuum of the proportion of original code written to develop the application, from build from scratch, through library and API calls, copy-paste programming, web mashup development, end-user programming, to creative design through the selection and combination of existing applications. All these design activities have much in common and can benefit from being studied as a whole.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ossher, Joel</style></author><author><style face="normal" font="default" size="100%">Bajracharya, Sushil</style></author><author><style face="normal" font="default" size="100%">Linstead, Erik</style></author><author><style face="normal" font="default" size="100%">Baldi, Pierre</style></author><author><style face="normal" font="default" size="100%">Lopes, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">integration</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">java.net</style></keyword><keyword><style  face="normal" font="default" size="100%">project</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">SourcererDB</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">183 - 186</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential resuse. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ossher, Joel</style></author><author><style face="normal" font="default" size="100%">Bajracharya, Sushil</style></author><author><style face="normal" font="default" size="100%">Linstead, Erik</style></author><author><style face="normal" font="default" size="100%">Baldi, Pierre</style></author><author><style face="normal" font="default" size="100%">Lopes, Cristina</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">java.net</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">sourcerer</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">183 - 186</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential re-use. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zhao, Luyin</style></author><author><style face="normal" font="default" size="100%">Deek, Fadi P.</style></author><author><style face="normal" font="default" size="100%">McHugh, James A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Strategies for Improving Open Source Software Usability</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">49 - 64</style></pages><abstract><style face="normal" font="default" size="100%">The Open Source Software (OSS) movement has had enormous impact on how software is created and continues to attract interest from researchers, software developers and users. A factor that may be inhibiting OSS from achieving greater success is usability, a fundamental characteristic to user acceptance of software. Motivated by the uniquely user-driven nature of the open source model and the extensive user base that participates in OSS projects, the authors propose an exploratory learning method and an associated web-based inspection environment that enables non-experts to contribute to open source usability inspection. This tool uses patternbased usability guidelines to help identify usability knowledge during inspection. The method emphasizes outlining and exploration features which the authors have formally evaluated and the results of which are described. Data collected from a qualitative study indicates positive impact of the proposed method in helping end-users inspect software and achieve better results in discovering usability problems.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bach, Paula</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Supporting the user experience in free/libre/open source software development</style></title><secondary-title><style face="normal" font="default" size="100%">PhD Thesis, THE PENNSYLVANIA STATE UNIVERSITY</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">codeplex</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><abstract><style face="normal" font="default" size="100%">With the increasing number and awareness of free/libre/open source software (FLOSS) projects, Internet users can download a FLOSS tool that meets just about any need. The user experience of projects, however, varies greatly and identifying FLOSS projects that offer a positive user experience (UX) is challenging. FLOSS projects center on software developer activities with little attention to user-centered design activities that could increase the user experience on the project. The purpose of this dissertation is to understand open source software ecology in order to bring support for user experience design activities on FLOSS projects. CodePlex, an open source project hosting website, serves as the open source software ecology.

The research consists of two phases, a descriptive science phase and a design science phase. In the descriptive phase fieldwork in the form of ethnomethodologically informed ethnography describes the everyday activities of three groups: the team that produces CodePlex, the participants who use CodePlex to produce open source projects, and user experience practitioners who bring their expertise to design software with a positive user experience. The descriptive phase also includes an analysis of activity awareness of the three groups. The design science phase consists of a claims analysis that provides design rationale for a design that proposes to support UX activities on CodePlex. The results show that activity awareness contributes to the socio-technical solution where UX activities can be supported as a new community of practice, with features that support building social capital. The UX support features include a UX workspace where UX contributors recognize their value and other features that support the presence of UX throughout the project site and the CodePlex community.

This dissertation contributes empirical materials from the descriptions of everyday activities of the three groups and analytic materials generated from the activity awareness and claims analyses that are translated into design representations. Specifically the contributions include (1) mechanisms of articulation work of the three groups and how the mechanisms contribute to the design representation; (2) the demonstration of a translation science in computersupported cooperative work (CSCW) and human-computer interaction (HCI); and (3) an understanding of how UX activities and software engineering activities integrate.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Vicini, Paolo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The System for Population Kinetics</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">29 - 43</style></pages><abstract><style face="normal" font="default" size="100%">This chapter describes the System for Population Kinetics (SPK), a novel Web service for performing population kinetic analysis. Population kinetic analysis is a widely-used tool for extracting information about the probability distributions of unknown parameters in kinetic models. The statistical population model is usually hierarchical, with a nested structure encompassing both variation between subjects and residual unexplained variation associated with the model predictions. The complexity of the analysis is largely driven by the nonlinearity of the models employed. Here, we provide a concise introduction to the topic and a historical perspective for the benefit of the reader who is new to these concepts. Next, we briefly describe the SPK open source system and its multi-tiered architecture, indicating the user goals it set to achieve and elucidating its practical usage with examples.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ekanayake, Jayalath</style></author><author><style face="normal" font="default" size="100%">Tappolet, Jonas</style></author><author><style face="normal" font="default" size="100%">Gall, Harald C.</style></author><author><style face="normal" font="default" size="100%">Bernstein, Abraham</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Tracking concept drift of software projects using defect prediction quality</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">defect prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/51MSR2009_0111_Ekanayake_Jayalath.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">51 - 60</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Defect prediction is an important task in the mining of software repositories, but the quality of predictions varies strongly within and across software projects. In this paper we investigate the reasons why the prediction quality is so fluctuating due to the altering nature of the bug (or defect) fixing process. Therefore, we adopt the notion of a concept drift, which denotes that the defect prediction model has become unsuitable as set of influencing features has changed - usually due to a change in the underlying bug generation process (i.e., the concept). We explore four open source projects (Eclipse, OpenOffice, Netbeans and Mozilla) and construct file-level and project-level features for each of them from their respective CVS and Bugzilla repositories. We then use this data to build defect prediction models and visualize the prediction quality along the time axis. These visualizations allow us to identify concept drifts and - as a consequence - phases of stability and instability expressed in the level of defect prediction quality. Further, we identify those project features, which are influencing the defect prediction quality using both a tree induction-algorithm and a linear regression model. Our experiments uncover that software systems are subject to considerable concept drifts in their evolution history. Specifically, we observe that the change in number of authors editing a file and the number of defects fixed by them contribute to a project's concept drift and therefore influence the defect prediction quality. Our findings suggest that project managers using defect prediction models for decision making should be aware of the actual phase of stability or instability due to a potential concept drift.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yatani, Koji</style></author><author><style face="normal" font="default" size="100%">Chung, Eunyoung</style></author><author><style face="normal" font="default" size="100%">Jensen, Carlos</style></author><author><style face="normal" font="default" size="100%">Truong, Khai N.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding how and why open source contributors use diagrams in the development of Ubuntu</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 27th international conference on Human factors in computing systems</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">CHI '09</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">diagramming</style></keyword><keyword><style  face="normal" font="default" size="100%">interviews</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software (oss)</style></keyword><keyword><style  face="normal" font="default" size="100%">software development</style></keyword><keyword><style  face="normal" font="default" size="100%">Ubuntu</style></keyword><keyword><style  face="normal" font="default" size="100%">visual representation</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1518701.1518853</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">995–1004</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-246-7</style></isbn><abstract><style face="normal" font="default" size="100%">Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort—Ubuntu.&quot;
&quot;Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants’ OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zegaye Seifu Wubishet</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding the Nature and Production Model of Hybrid Free and Open Source Systems: The Case of Varnish</style></title><secondary-title><style face="normal" font="default" size="100%">42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">organizational sponsorship</style></keyword><keyword><style  face="normal" font="default" size="100%">peer production</style></keyword><keyword><style  face="normal" font="default" size="100%">varnish</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-02.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Los Alamitos, CA, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-11</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">This is a detailed interpretive case study analysis of an open source software project, called Varnish. The conceptual framework is based on the literature covering issues of commons based production models and the organization of open source projects. The comparative analysis reveals that Varnish is a hybrid project, encompassing the features of open source software while managed by a company as a proprietary project would. It is also hybrid in the sense that it employs a combination of hierarchical and commons based peer production model features. This mix of characters addresses a variety of problems related to each of the aforementioned categories.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Singh, V</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author><author><style face="normal" font="default" size="100%">Nichols, D.M</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Users of Open Source Software - How do they get help?</style></title><secondary-title><style face="normal" font="default" size="100%">HICSS 2009</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">technical help</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><abstract><style face="normal" font="default" size="100%">A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Singh, Vandana</style></author><author><style face="normal" font="default" size="100%">Michael B Twidale</style></author><author><style face="normal" font="default" size="100%">David M Nichols</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Users of Open Source Software - How Do They Get Help?</style></title><secondary-title><style face="normal" font="default" size="100%">42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">technical help</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-04.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Los Alamitos, CA, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we collected twenty threads each from eight different websites making a total of 160 threads&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lubsen, Zeeger</style></author><author><style face="normal" font="default" size="100%">Zaidman, Andy</style></author><author><style face="normal" font="default" size="100%">Pinzger, Martin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using association rules to study the co-evolution of production &amp; test code</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">association rules</style></keyword><keyword><style  face="normal" font="default" size="100%">checkstyle</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">unit test</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/151UsingAssociation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">151 - 154</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">Unit tests are generally acknowledged as an important aid to produce high quality code, as they provide quick feedback to developers on the correctness of their code. In order to achieve high quality, well-maintained tests are needed. Ideally, tests co-evolve with the production code to test changes as soon as possible. In this paper, we explore an approach based on association rule mining to determine whether production and test code co-evolve synchronously. Through two case studies, one with an open source and another one with an industrial software system, we show that our association rule mining approach allows one to assess the co-evolution of product and test code in a software project and, moreover, to uncover the distribution of programmer effort over pure coding, pure testing, or a more test-driven-like practice.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tian, Kai</style></author><author><style face="normal" font="default" size="100%">Revelle, Meghan</style></author><author><style face="normal" font="default" size="100%">Poshyvanyk, Denys</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Latent Dirichlet Allocation for automatic categorization of software</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">categorization</style></keyword><keyword><style  face="normal" font="default" size="100%">category mining</style></keyword><keyword><style  face="normal" font="default" size="100%">lact</style></keyword><keyword><style  face="normal" font="default" size="100%">mudablue</style></keyword><keyword><style  face="normal" font="default" size="100%">multiple languages</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/163MSR2009_TianPos.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">163 - 166</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">In this paper, we propose a technique called LACT for automatically categorizing software systems in open-source repositories. LACT is based on latent Dirichlet Allocation, an information retrieval method which is used to index and analyze source code documents as mixtures of probabilistic topics. For an initial evaluation, we performed two studies. In the first study, LACT was compared against an existing tool, MUDABlue, for classifying 41 software systems written in C into problem domain categories. The results indicate that LACT can automatically produce meaningful category names and yield classification results comparable to MUDABlue. In the second study, we applied LACT to 43 software systems written in different programming languages such as C/C++, Java, C#, PHP, and Perl. The results indicate that LACT can be used effectively for the automatic categorization of software systems regardless of the underlying programming language or paradigm. Moreover, both studies indicate that LACT can identify several new categories that are based on libraries, architectures, or programming languages, which is a promising improvement as compared to manual categorization and existing techniques.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Izquierdo-Cortazar, Daniel</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Ortega, Felipe</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Software Archaeology to Measure Knowledge Loss in Software Projects Due to Developer Turnover</style></title><secondary-title><style face="normal" font="default" size="100%">2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">attrition</style></keyword><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">evince</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">gimp</style></keyword><keyword><style  face="normal" font="default" size="100%">growth</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge collaboration</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">nautilus</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword><keyword><style  face="normal" font="default" size="100%">turnover</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/07-07-08.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Los Alamitos, CA, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><isbn><style face="normal" font="default" size="100%">978-0-7695-3450-3</style></isbn><abstract><style face="normal" font="default" size="100%">Developer turnover can result in a major problem when developing software. When senior developers abandon a software project, they leave a knowledge gap that has to be managed. In addition, new (junior) developers require some time in order to achieve the desired level of productivity. In this paper, we present a methodology to measure the effect of knowledge loss due to developer turnover in software projects. For a given software project, we measure the quantity of code that has been authored by developers that do not belong to the current development team, which we define as orphaned code. Besides, we study how orphaned code is managed by the project. Our methodology is based on the concept of software archaeology, a derivation of software evolution. As case studies we have selected four FLOSS (free, libre, open source software) projects, from purely driven by volunteers to company-supported. The application of our methodology to these case studies will give insight into the turnover that these projects suffer and how they have managed it and shows that this methodology is worth being augmented in future research.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yoris A. Au</style></author><author><style face="normal" font="default" size="100%">Darrell Carpenter</style></author><author><style face="normal" font="default" size="100%">Xiaogang Chen</style></author><author><style face="normal" font="default" size="100%">Jan G. Clark</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Virtual organizational learning in open source software development projects</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Management</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">learning</style></keyword><keyword><style  face="normal" font="default" size="100%">Project performance</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual organization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6VD0-4V1D7NT-1/2/a3bbf7652c674f753398160b8f05f6e9</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">46</style></volume><pages><style face="normal" font="default" size="100%">9 - 15</style></pages><abstract><style face="normal" font="default" size="100%">We studied virtual organizational learning in open source software (OSS) development projects. Specifically, our research focused on learning effects of OSS projects and the factors that affect the learning process. The number and percentage of resolved bugs and bug resolution time of 118 SourceForge.net OSS projects were used to measure the learning effects. Projects were characterized by project type, number and experience of developers, number of bugs, and bug resolution time. Our results provided evidence of virtual organizational learning in OSS development projects and support for several factors as determinants of performance. Team size was a significant predictor, with mid-sized project teams functioning best. Teams of three to seven developers exhibited the highest efficiency over time and teams of eight to 15 produced the lowest mean time for bug resolution. Increasing the percentage of bugs assigned to specific developers or boosting developer participation in other OSS projects also improved performance. Furthermore, project type introduced variability in project team performance.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lungu, Mircea</style></author><author><style face="normal" font="default" size="100%">Malnati, Jacopo</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Visualizing Gnome with the Small Project Observatory</style></title><secondary-title><style face="normal" font="default" size="100%">2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">spo</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/103Lung2009a.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Vancouver, BC, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">103 - 106</style></pages><isbn><style face="normal" font="default" size="100%">978-1-4244-3493-0</style></isbn><abstract><style face="normal" font="default" size="100%">We analyzed the gnome family of systems with the small project observatory, our online ecosystem visualization platform. We begin by briefly introducing the model of SPO. We then observe and discuss several phases in the activity of the gnome ecosystem. We follow and look at how the contributors are distributed between writing source code and doing other activities such as internationalization. We end with a visual overview of the activity of more than 900 contributors in the 10 years of existence of gnome.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bo Xu</style></author><author><style face="normal" font="default" size="100%">Donald R. Jones</style></author><author><style face="normal" font="default" size="100%">Bingjia Shao</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Volunteers' involvement in online community based software development</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Management</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">age</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">effectiveness</style></keyword><keyword><style  face="normal" font="default" size="100%">function points</style></keyword><keyword><style  face="normal" font="default" size="100%">ideology</style></keyword><keyword><style  face="normal" font="default" size="100%">leadership</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">status</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword><keyword><style  face="normal" font="default" size="100%">Volunteers</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6VD0-4VP1CN0-1/2/8e1c7be4fcedd1419209c5c843ffa923</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">46</style></volume><pages><style face="normal" font="default" size="100%">151 - 158</style></pages><abstract><style face="normal" font="default" size="100%">We sought to gain understanding of voluntary developers' involvement in open source software (OSS) projects. Data were collected from voluntary developers working on open source projects. Our findings indicated that a voluntary developer's involvement was very important to his or her performance and that involvement was dependent on individual motivations (personal software needs, reputation and skills gaining expectation, enjoyment in open source coding) and project community factors (leadership effectiveness, interpersonal relationship, community ideology). Our work contributes theoretically and empirically to the body of OSS research and has practical implications for OSS project management.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Data were collected through an online survey and by searching project archives. On Sourceforge.net, each developer was uniquely identified with a user account, and the developer’s performance was assessed through the number of function points accepted by the project in a certain time period, obtained through conversion and calculation from the project’s code repository. Data for other constructs were obtained from the developers’ response to the online survey. &quot;
&quot;a developer’s performance was measured by the number of function points made and accepted into the project during the observed time period.&quot;

project age, development status, license type, number of developers</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Valentin Vlasceanu</style></author><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Laurière, Stéphane</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Weaving a Semantic Web across OSS repositories: a spotlight on bts­link, UDD, SWIM</style></title><secondary-title><style face="normal" font="default" size="100%">4th Workshop on Public Data about Software Development (WoPDaSD 2009)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bts-link</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracker</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">ecosystem</style></keyword><keyword><style  face="normal" font="default" size="100%">helios</style></keyword><keyword><style  face="normal" font="default" size="100%">mandriva</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic Web</style></keyword><keyword><style  face="normal" font="default" size="100%">swim</style></keyword><keyword><style  face="normal" font="default" size="100%">udd</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/HELIOS-WOPDASD-improved-Olivier.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">Several  public  repositories  and  archives  of  facts  about  libre software  projects,  developed either  by open  source  communities  or by research communities,  have been flourishing over  the Web in  the  recent  years.  These  enable  new analysis  and  support  new quality assurance tasks. 

By  using  Semantic  Web  techniques,  the  databases  containing data  about  open-source  software projects development can  be interconnected,  hence  letting  OSS  partakers  identify  resources, annotate  them  and  further  interlink  them  using  dedicated properties,  collectively  designing  a  distributed  semantic  graph. Such  links  expressed  with  standard  Semantic  techniques  are paving  the  way  to  new  applications  (including  ones  meant  for “end-users”).  For  instance  this  may have  an  impact  on  the  way research efforts  are  conducted  (less  fragmented),  and  could  also be  used  by  development  communities  to  improve  Quality Assurance tasks. 

A goal  of the  research  conducted  within  the  HELIOS project, is to  address  bugtracker  synchronization  issues.  For that, the potential of using Semantic  Web  technologies  in  navigating between many different  bugtracker  systems scattered all  over the open source ecosystem is being investigated. 

This  position  paper  presents  some  existing  tools,  projects  and models  proposed  by  OSS  actors  that  are  complementary  to research  initiatives,  and  that  are  likely to  lead  to  useful  future  developments:  UDD (Ultimate  Debian  Database)  and  bts-link, developed by the  Debian community,  and  SWIM (Semantic Web enabled Issue Manager) developed by Mandriva. 

The  HELIOS team welcomes  comments  on the  future  paths  that  can  be  considered  in  using  the  Semantic  Web  approach  for improving these projects. </style></abstract><notes><style face="normal" font="default" size="100%">position paper; non-experimental</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Radtke, Nicholas P.</style></author><author><style face="normal" font="default" size="100%">Janssen, Marco A.</style></author><author><style face="normal" font="default" size="100%">Collofello, James S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What Makes Free/Libre Open Source Software (FLOSS) Projects Successful? An Agent-Based Model of FLOSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Open Source Software and Processes</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">1 - 13</style></pages><abstract><style face="normal" font="default" size="100%">The last few years have seen a rapid increase in the number of Free/Libre Open Source Software (FLOSS) projects. Some of these projects, such as Linux and the Apache web server, have become phenomenally successful. However, for every successful FLOSS project there are dozens of FLOSS projects which never succeed. These projects fail to attract developers and/or consumers and, as a result, never get off the ground. The aim of this research is to better understand why some FLOSS projects flourish while others wither and die. This article presents a simple agent-based model that is calibrated on key patterns of data from SourceForge, the largest online site hosting open source projects. The calibrated model provides insight into the conditions necessary for FLOSS success and might be used for scenario analysis of future developments of FLOSS.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Harper, F. Maxwell</style></author><author><style face="normal" font="default" size="100%">Moy, D.</style></author><author><style face="normal" font="default" size="100%">Konstan, J.A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Facts or Friends? Distinguishing Informational and Conversational Questions in Social QnA Sites (forthcoming)</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chen, J</style></author><author><style face="normal" font="default" size="100%">Geyer, W.</style></author><author><style face="normal" font="default" size="100%">Dugan, C.</style></author><author><style face="normal" font="default" size="100%">Muller, M.</style></author><author><style face="normal" font="default" size="100%">Guy, I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Making New Friends, but Keep the Old - Recommending People on Social Networking Sites (forthcoming)</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Terry, M.</style></author><author><style face="normal" font="default" size="100%">Kay, M.</style></author><author><style face="normal" font="default" size="100%">Lafreniere, B.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Perceptions and Practices of Usability in the Free/Open Source Software (FOSS) Community</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><number><style face="normal" font="default" size="100%">CS-2009-26</style></number><publisher><style face="normal" font="default" size="100%">David R. Cheriton School of Computer Science, University of Waterloo</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Lyytinen, K.</style></author><author><style face="normal" font="default" size="100%">Loucopoulos, P.</style></author><author><style face="normal" font="default" size="100%">Mylopoulos, J.</style></author><author><style face="normal" font="default" size="100%">Robinson, W.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding Requirements for Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Design Requirements Engineering: A Ten-Year Perspective</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">Lecture Notes in Business Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2009</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer-Verlag</style></publisher><volume><style face="normal" font="default" size="100%">14</style></volume><pages><style face="normal" font="default" size="100%">467-494</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Amit Deshpande</style></author><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Continuous Integration in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Conference on Open Source Software</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/oss-2008-continuous-integration-final.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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'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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andreas Meiszner</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">FLOSS-like education transfer report</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FLOSSCOM_WP5_PHASE_3_REPORT.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free/Libre and Open Source Software (FLOSS) communities are not only an exemplar for successful software development, but also for well working learning environments. Yet little is known about how learning occurs in the FLOSS communities and what the underlying success factors are. FLOSS communities might be seen as an example of 'Best Practice' in how ICT can help to improve education in terms of learning processes, up to date content and open inclusive education where no learner is excluded from participation.The FLOSSCOM project was undertaken in order to evaluate how learning in FLOSS is organised and if, to which degree, and how FLOSS learning principles can be transferred to and used for the improvement of ICT supported formal education. Precisely, the FLOSSPOLS project intended to- identify the factors that contribute to successful knowledge construction in informal learning communities, such as the FLOSS communities- analyze the effectiveness of a FLOSS-like learning community in a formal educational setting- provide case studies, scenarios and guidelines for teachers and decision-makers on how to successfully embed such learning communities within formal educational environments to enhance student progression, retention and achievement- evaluate the project and disseminate the results to the wider community.This report is the third and final report of the FLOSSCOM project. It aims to provide scenarios and guidelines for teachers and decision-makers as practical documentation on how principles of FLOSS-like informal learning communities might be transferred to formal educational environments.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andreas Meiszner</style></author><author><style face="normal" font="default" size="100%">Rüdige Glott</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Preparing the Ne(x)t Generation: Lessons learnt from Free/Libre Open Source Software and their Communities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/GUNI_paper_proceedings_Meiszner_Glott_Sowe.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this article, the authors Andreas Meiszner, RÃ¼diger Glott and Sulayaman K. Sowe, examine the lessons that can be learnt from the Free / Libre Open and Source Software (FLOSS) communities. FLOSS communities, as good practice examples of Open Participatory Learning Ecosystems, illustrate possible pathways for higher education to go beyond the limits of the current Open Educational Resource move.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mike Chege</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Ubuntuism, Commodification, and the Software Dialectic.</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Ubuntuism_Commodification_and_the_Software_Dialectic.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&quot;Free as in speech, but not free as in beer,&quot; is the refrain made famous by Richard Stallman, the standard-bearer of the free software movement. However, many free software advocates seem to be of the opinion that the purity of free software is somehow tainted by any preoccupation with money or profit. Inevitably, this has implications for the economic sustainability of free software, for without a source of income, how can free software hope to survive? The challenge of finding a way to ensure economic sustainability without sacrificing the ideals of free software is what we have termed the &quot;software dialectic.&quot;&quot;While the literature on the economics of free software is already quite substantial, in this essay we approach the subject by considering first principles, such as the difference between wealth and money, how the market chooses what to produce, and what the laws of thermodynamics have to do with economics. Finally, even though the ideas expressed in this essay apply to free software in general, here we shall be focusing on that particular incarnation of free software known as the GNU/Linux system.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gilberto Munoz</style></author><author><style face="normal" font="default" size="100%">Carolyn Seaman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Investigation into the Adoption of Open Source Software in Hospitals</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software (OSS) has gained considerable attention recently in health care. Yet, how and why OSS is being adopted within hospitals in particular remains a poorly understood issue. This research attempts to further this understanding. A mixed-method research approach was used to explore the extent of OSS adoption in hospitals as well as the factors facilitating and inhibiting adoption. The findings suggest a very limited adoption of OSS in hospitals. Hospitals tend to adopt general-purpose instead of domain-specific OSS. We found that software vendors are the critical factor facilitating the adoption of OSS in hospitals. Conversely, lack of in-house development, as well as a perceived lack of security, quality, and accountability of OSS products were factors inhibiting adoption. An empirical model is presented to illustrate the factors facilitating and inhibiting the adoption of OSS in hospitals.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jan Fredrik Stoveland</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Managing Firm-Sponsored Open Source Communities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The interest and use of open source software and methodology has gained an increasing amount of commercial attention, and we are currently witnessing that established proprietary software firms are taking a step further by opening their own software projects in an attempt to create firm-sponsored open source communities. Siobhan O'Mahony's research finds that these firms have to handle a tension between openness and control in their product development, but little research has been done to detail how this balance is achieved. I have studied the American software company Novell and the openSUSE project, largely guided by an inductive, qualitative approach supplemented by some quantitative methods. In the study I draw upon Niklas Luhmann's theory of autopoietic social systems to create a distinction between the sponsor firm and the sponsored community, and I investigate the mechanisms that hold the two systems together despite their differences in interests. I argue that there are several elements that ensure a tight coupling between the two systems, including the boundary objects situated between them, the shared communication channels and the efforts of the marginal people whom have roles in both systems. A primary contribution to the theory of boundary objects is a distinction between what I describe as supportive-objects and target-objects. I argue that the latter holds a strong motivating power that should be appended to our understanding of individuals' and collectives' motivation to participate in open source software projects. I explore several possible future scenarios for the evolution of firm-sponsored communities, and find that Novell is pursuing a strategy for managing openness in such a community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Replication of FLOSS Research as eResearch</style></title><secondary-title><style face="normal" font="default" size="100%">Oxford e-Research Conference 2008</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">eResearch eScience</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Wiggins-FLOSS-eResearch.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We are working to introduce the ideas of eResearch to a multi-disciplinary research domain: those researchers examining Free/Libre and Open Source Software (FLOSS) and its development (Howison, Wiggins, &amp; Crowston, 2008).The first phase of this work focused on building a repository for data on FLOSS teams, FLOSSmole (Howison, Conklin, &amp; Crowston, 2006), and collaborating with other nascent data repositories in the field. Recently we have begun a second phase, which is to introduce another established principle of eResearch, that of broader collaboration through shared workflows accessing these data repositories. To provide an example of the potential value of this principle, we are replicating seminal FLOSS papers using eResearch approaches. This paper describes research outcomes and lessons learned from translating published literature into eResearch workflows.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">James Caverle</style></author><author><style face="normal" font="default" size="100%">Steve Webb</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A large-scale study of MySpace: Observations and implications for online social networks</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Weblogs and Social Media (ICWSM 2008)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March 30–April 2</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Seattle, WA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jamil Alkhatib</style></author><author><style face="normal" font="default" size="100%">Mohab Anis</style></author><author><style face="normal" font="default" size="100%">Hamid Noori</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source: The Next Big Thing In Technology Transfer to Developing Nations</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/1569088836.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free Open Source (FOS) should be one of the least expensive and most effective solutions for technology and knowledge transfer to developing nations. This concept has diffused to several fields such as software, hardware, and content. FOS offers not only a low cost alternative for technology acquisition, but also for networking based on cooperation. In addition, the transaction costs of communication, licensing and negotiations are minimized, freeing up funds for real development. In this paper, FOS incentives, indicators, and measures are explained and the advantages of FOS as a viable technology and knowledge transfer tool for developing countries are highlighted.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oliver Alexy</style></author><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?</style></title><secondary-title><style face="normal" font="default" size="100%">Working Paper</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Most firms that use or develop software today face the questions of whether and how to engage in open source software (OSS). Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the models of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a theoretical framework of how job function influences individuals? proclivity to support their employers? adoption of OSS and OSS practices. We argue that job function determines an individual?s tasks, and that different tasks are differentially affected by OSS. Our study is based on interviews and a large-scale survey in a multinational corporation. Distinguishing between developers, testers, software architects, project managers, and managers, we find greater engagement in OSS to be favored most strongly by testers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate OSS engagement. A corporation interested in adopting OSS should thus take into account the job function-related incentives of each individual. More generally, we propose that models predicting IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which will be determined largely by their job functions.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The indirect debate and the community. How the periphery and the core relate in the Free/Open Source Software community</style></title><secondary-title><style face="normal" font="default" size="100%">DRUID conference 2008 paper</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/rullani_periphery.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The present paper analyzes the relationship between the core and the periphery in the Free/Open Source innovation model. Considering the core as the &quot;sparring partner&quot; of the periphery, and not vice versa, the present discussion tries to apply a view opposite to the most diffused one. The first passages of the paper are meant to characterize the periphery, its functions, and the source of the realized division of labor with the core. It is shown that this specific schema is the consequence of the self-organizing nature of the FOSS model, that needs to dissipate resources to assure that the whole dynamics does not cease. However, this peculiar division of labor is possible only if the periphery and the core share the same set of interpretative schemes, norms and vision of the authoritative configuration of the community. To understand how this last passage is possible, I develop a conceptual model based on Wenger's concept of imagination and alignment, usually kept in the background by the literature on FOSS, and on the idea of dissonance (e.g. Kuran, 1998). Eventually, the paper tries discuss the relevant properties of the periphery (invisibility, atomization and instability) emerging from the analysis of the possible flaws of the process</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Involving Software Engineering Students in Open Source Software Projects: Experiences from a Pilot Study</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/bazaars_of_learning.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Anecdotal and research evidences show that the Free and Open Source Software (F/OSS) development model has produced a paradigm shift in the way we develop, support, and distribute software. This shift is not only redefining the software industry but also the way we teach and learn in our software engineering (SE) courses. But for many universities F/OSS is seen as an optional low cost technology to support the IT infrastructure and administrational duties. Few see F/OSS as an opportunity for students to learn the SE concepts and skills we teach. Furthermore, it is still an open question as to whether the F/OSS methodology can be effectively used to teach SE courses within the formally structured curriculum in most universities. This paper discusses F/OSS projects as bazaars of learning that offer a meaningful learning context. The discussion is centered on a pilot study in which students were involved in software testing in F/OSS projects. We present the teaching and learning framework we used in the pilot study and report on our experiences, lessons learned, and some practical problems we encountered. Our grading and evaluation approach show that the students did relatively well as bug hunters and reporters. Results from two online surveys indicate that students are motivated in participating in software testing in the bazaar, and they are willing to participate in project activities long after their graduation. The study reveals one possible way SE educators can teach and integrate F/OSS into their formal curricular structure.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Eileen Allen</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Asynchronous Decision-Making in Distributed Teams</style></title><secondary-title><style face="normal" font="default" size="100%">Computer Supported Cooperative Work 2008</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CSCW2008FLOSSposter_sub.pdf</style></url><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CSCW2008Poster11x17sub.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">1–2</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Extensive use of CSCW applications can influence group decision-making practices. Unlike previous research focused on the influence of synchronous ICTs, our study examines how group decisions are made in asynchronous communication channels. Our inductive qualitative analysis of 360 decision episodes of six FLOSS projects revealed diversity in decision-making practices, which appears to be related to differences in project effectiveness and task type. We also find that standardization of procedures through CSCW tools transforms the nature of some software development work from non-routine to standard procedure.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">eResearch Workflows for Studying Free and Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275</style></volume><pages><style face="normal" font="default" size="100%">405–411</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology, then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one?Taverna?and introducing its features. To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Pia Waugh</style></author><author><style face="normal" font="default" size="100%">Randy Metcalfe</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Foundations of Openness</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jul</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Foundations-of-openness-V2-release.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This project explores the notion of openness in software projects. It contextualizes different facets of openness and considers their individual and collective usefulness. It provides a tentative evaluative schema to allow others to weigh up specific criteria that may be important to them. It acknowledges that these criteria may have different weightings for different people, e.g. governance vs open standards vs code licence. The object is *not* a blanket recommendation for openness in all facets of a project. Rather it is a tool for projects, and those who use those projects, to investigate and illuminate the choices being made as well as the implication of open and closed approaches.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Saskia van de Nieuwenhof</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Licensing Freedom; An Ethical Analysis of Free and Open Source Software Licenses</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Thesis_SaskiavandeNieuwenhof.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free and open source software enables users to use, read and modify the source code of computer programs. In proprietary software, access to the source code is not given and users are generally not permitted to use, read and modify the source code. Opponents of a proprietary system state that proprietary software is morally wrong and in this thesis, the arguments they use are evaluated.Several licensing schemes can be used as an addition to copyright law to give users the rights described above. The most important division between these different licenses can be made on the basis of the use of the copyleft principle. This principle obliges the licensee to distribute modified versions of the software under the same, or similar terms as the original license. In this thesis, this obligation is seen as a restriction on the freedom of the individual. Comparisons and possible justifications will give better insight in this supposed contradiction.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Champions of Revealing - The Role of Open Source Developers in Commercial Firms</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Henkel_Champions_of_revealing_2008-01.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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'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's role. However, neither interview data nor regression analysis show indications of commercially harmful revealing behavior induced by &quot;&quot;Free Software ideology.&quot;&quot; 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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Greg R Vetter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Claiming Copyleft in Open Source Software:  What if the Free Software Foundation's General Public License (GPL) had been Patented?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Vetter.ClaimingCopyleftInOSS-WhatIfGPLPatented.2008Mich.St_.L.Rev_.279.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Patent law, by necessity, needs some way to evaluate inventiveness. Otherwise, it will grant rights to advances not worth &quot;&quot;the embarrassment of an exclusive patent.&quot;&quot; The innovations of version two of the Free Software Foundation'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's criteria, often referred to as the five elements of patentability. The first element of patentability, statutory subject matter, would have excluded the GPLv2's copyright-based licensing technique as a &quot;&quot;business method.&quot;&quot; A variety of industry developments in the decades following GPLv2's arrival, combined with the license'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's unique licensing technique. This then raises the counter-factual inquiry for this symposium article: what might have occurred differently if GPLv2'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's two-decade trajectory through information technology and the Internet? If so, can we estimate in what ways? The Article'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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author><author><style face="normal" font="default" size="100%">Lars Risan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Guest Editorial of the Special Issue on Socio-technical Dynamics in the Free/Libre Open Source Software (FLOSS) Social World</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Guest_editorial_Lin&amp;Risan.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This special issue is the first volume in academia dedicated to a qualitative inquiry on dynamics in the FLOSS development and implementation, even if it is not alone in this endeavour (see e.g., Coleman, 2004; Kelty, 2005). Such a qualitative inquiry challenges the universally vocal and normative way of depicting FLOSS culture and practices (e.g., a homogeneous gift-giving and volunteering culture). The special issue encourages a practice-based and holistic view to exploring multiple cultures and practices in developing, localising, appropriating, and customising FLOSS. It also addresses the diversity in FLOSS communities through asking how seemingly global FLOSS cultures are translated into different contexts and locales. The importance of such an emphasis on how FLOSS technologies and practices diffract as they travel is nicely encapsulated by Haraway (1992) in her optic metaphor of white light that diffracts through a prism and becomes a rainbow. In light of this metaphor, a piece of FLOSS software is never really the same; when reproduced and shared, it is both the same (the standard) and something else in the mean time.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Isabelle Fagnot</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The motivational arc of massive virtual collaboration</style></title><secondary-title><style face="normal" font="default" size="100%">IFIP WG 9.5, International Working Conference on Virtuality and Society: Massive Virtual Communities</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">February</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/crowston_fagnot_ifip.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">1–13</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Massive virtual collaborations (MVC) involve large numbers of mostly unpaid contributors collectively creating new content. Wikipedia is the most dramatic example of MVC; smaller-scale examples include contributors to blogs and discussion groups and teams of programmers and users developing free/libre open source software (FLOSS). In this paper, we propose a model of motivations for contribution to MVC that integrates various theoretical perspectives. The model extends prior work by distinguishing three different levels of contribution to projects (initial, sustained and meta) and by capturing the dynamic and recursive effects of contributions on emergent individual and project states.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Anita Say Chan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">PhD Candidate Paper</style></title><secondary-title><style face="normal" font="default" size="100%">Science Studies</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Feb</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Chan_ScienceStudies.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">National legislation to mandate the use or consideration of Free/Libre and Open Source Software (FLOSS) in government institutions is increasingly emerging as a strategy for FLOSS advocates in Latin America and the broader developing world. Such movements for the political use and regulation of FLOSS mark a distinct turn in the objectives and work of FLOSS advocates, whose activities largely focused on the dissemination of FLOSS as a technological artifact. This paper investigates the network of diverse actors involved in promoting FLOSS legislation in Peru, one of the first nations where a movement for FLOSS legislation emerged. It emphasizes that crucial to the work of FLOSS' network actors is not their merely technological productivity, but their cultural and political productivity - that is, their ability to produce diverse body of meaning made both evident and mobile in narratives of FLOSS use and adoption.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Linus Dahlander</style></author><author><style face="normal" font="default" size="100%">M Magnusson</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Do Firms Make Use of Open Source Communities?</style></title><secondary-title><style face="normal" font="default" size="100%">Long Range Planning</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">cendio</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">roxen</style></keyword><keyword><style  face="normal" font="default" size="100%">secondary data</style></keyword><keyword><style  face="normal" font="default" size="100%">sot</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Dec</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.acm.jhu.edu/~paulproteus/tmp/sdarticle.pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dahlandermagnusson2008.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">6</style></number><volume><style face="normal" font="default" size="100%">41</style></volume><pages><style face="normal" font="default" size="100%">629-649</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Relying on four in-depth case studies of firms involved with open source software, we investigate how firms make use of open source communities, and how that use is associated with their business models. Three themes - accessing, aligning and assimilating -are inductively developed for how the firms relate to the external knowledge created in the communities. For each theme, we make an argument about the tactics associated with each theme and their positive and negative consequences. The findings are related to the literature on the open and distributed nature of innovation, and various theoretical and managerial implications are discussed.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;To obtain more information about the firms’ relationships with their respective communities, we followed mailing lists and forums over a three-month period, checking them at least three times a week. &quot;
&quot;Firm data. Secondary sources, including annual reports, company directories, business and specialist press and homepages, were used to gather information on firms&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Greg R Vetter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Slouching toward Open Innovation:  Free and Open Source Software (FOSS) for Electronic Health Information</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Dec</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/VetterSlouchingTowardOpenInnovation-FOSSforEHI_6.29.2008.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The potential for Free and Open Source Software (FOSS) to enable open innovation in a particular software market depends on the characteristics of that market. From this premise, using a case study approach, this Article argues that some software markets have characteristics that inherently disfavor initiating or expanding the use of FOSS and its unique mode of licensing the intellectual property that underlies software. The case study involves software to manage health information for hospitals or physician groups in the form of the electronic medical record, or EMR. Proprietary software venders supply most of the products for this software market. Recently, the U.S. government undertook experimental steps to promote a FOSS package for EMR, raising the question as to whether the EMR software market is amenable to FOSS. This Article describes various factors that might signal a FOSS disfavoring market, including low technical aptitude among users, differences among users in their work flow and software interface needs, users with dispassionate computing agendas, and entrenched proprietary competitors in an area supporting minimal complementary goods or services. FOSS, however, might be able to overcome these impedances in a particular software market if its unique motivational mix is strong enough. This Article describes potential facilitators to support this possibility. One such facilitator, specifically for the EMR market, but perhaps generally for other markets, may be safe harbors for FOSS development within any relevant anti-collaboration and anti-tinkering laws. Licensing facilitators include emphasizing approaches such as dual licensing or promoting FOSS contributions by contractors engaged by users. This Article concludes by mentioning potential non-licensing facilitators to augment the FOSS motivational mix for markets that might disfavor it.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">eScience for Free/Libre Open Source Software Researchers</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/eResearch2008iCS-working.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">FLOSSpapers</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents a case study of the application of eScience tools and practices for the social science research community studying Free/Libre Open Source Software (FLOSS) development practices. We first describe what we mean by eScience and introduce research on FLOSS to motivate the need for eScience tools and approaches. We then describe our initial efforts to introduce eScience tools for FLOSS research, potential obstacles, and how the use of such tools might affect the practice of research in this field.</style></abstract><work-type><style face="normal" font="default" size="100%">Working Paper</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jai Asundi</style></author><author><style face="normal" font="default" size="100%">Octavian Carare</style></author><author><style face="normal" font="default" size="100%">Kutsal Dogan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Competitive Implications of Software Open-Sourcing</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Aug</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1185374</style></url></web-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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' 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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jim Bessen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software: Free Provision of a Complex Public Good</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lakhanivonhippelusersupport.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software, developed by volunteers, appears counter to conventional wisdom about private provision of public goods. Standard arguments suggest that proprietary provision should be more efficient. But complex open source products challenge commercially-developed software in quality and market share. I argue that the complexity of software changes the results. With complex software, standard products cannot address all consumer needs and proprietary custom solutions are not always offered. Open source allows consumers to create their own customizations. When such user-customizations are then shared, open source products grow in quality and features. Open source extends the market for complex products.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jim Bessen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software: Free Provision of a Complex Public Good</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/opensrc.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software, developed by volunteers, appears counter to conventional wisdom about private provision of public goods. Standard arguments suggest that proprietary provision should be more efficient. But complex open source products challenge commercially-developed software in quality and market share. I argue that the complexity of software changes the results. With complex software, standard products cannot address all consumer needs and proprietary custom solutions are not always offered. Open source allows consumers to create their own customizations. When such user-customizations are then shared, open source products grow in quality and features. Open source extends the market for complex products.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Nejdl, W., Kay, J., Pu, P., Herder, E.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Altruism, Selfishness, and Destructiveness on the Social Web</style></title><secondary-title><style face="normal" font="default" size="100%">5th International Conference on Adaptive Hypermedia and Adaptive Web-Based Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">7/29/2008</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer-Verlag</style></publisher><pub-location><style face="normal" font="default" size="100%">Hannover, Germany</style></pub-location><pages><style face="normal" font="default" size="100%">9-11</style></pages><isbn><style face="normal" font="default" size="100%">978-3-540-70984-8 </style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author><author><style face="normal" font="default" size="100%">Lakhani, Karim</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Getting Clear About Communities in Open Innovation</style></title><secondary-title><style face="normal" font="default" size="100%">Industry &amp; Innovation</style></secondary-title><short-title><style face="normal" font="default" size="100%">CIAI</style></short-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">4/2008</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">15</style></volume><pages><style face="normal" font="default" size="100%">223 - 231</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author><author><style face="normal" font="default" size="100%">Siobhan O'Mahony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Role of Participation Architecture in Growing Sponsored Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">Industry &amp; Innovation</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">4/2008</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">15</style></volume><pages><style face="normal" font="default" size="100%">145 - 168</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matthew Van Antwerp</style></author><author><style face="normal" font="default" size="100%">Madey, Greg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Advances in the Sourceforge Research Data Archive</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">forges</style></keyword><keyword><style  face="normal" font="default" size="100%">repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/srda2008.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">25-29</style></pages><abstract><style face="normal" font="default" size="100%">The SourceForge Research Data Archive (SRDA), located at http://zerlot.cse.nd.edu, is a collection of Open Source Software (OSS) data and resources [6]. Over 100 researchers worldwide use the archive for research in many ﬁelds. In this paper, we describe the recent changes, the work in progress, and future plans for making the archive easier to use and for allowing more advanced research to be done with the data available.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fagerholm, Fabian</style></author><author><style face="normal" font="default" size="100%">Taina, Juha</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collecting data from distributed FOSS projects</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bitkeeper</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">distributed</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">fork rate</style></keyword><keyword><style  face="normal" font="default" size="100%">git</style></keyword><keyword><style  face="normal" font="default" size="100%">life cycle</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">linux kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">merge rate</style></keyword><keyword><style  face="normal" font="default" size="100%">subversion</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/fagerholm.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">8-13</style></pages><abstract><style face="normal" font="default" size="100%">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 eﬀect of highly distributed software development, as found in the Linux kernel project, on collection and modelling of software development data. We ﬁnd 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. </style></abstract><notes><style face="normal" font="default" size="100%">&quot;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.&quot;
&quot;To acquire data from each data source, we wrote special programs based on the earlier prototypes....The ﬁrst 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.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Cross-repository data linking with RDF and OWL</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">data integration</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">forges</style></keyword><keyword><style  face="normal" font="default" size="100%">integration</style></keyword><keyword><style  face="normal" font="default" size="100%">owl</style></keyword><keyword><style  face="normal" font="default" size="100%">RDF</style></keyword><keyword><style  face="normal" font="default" size="100%">repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic Web</style></keyword><keyword><style  face="normal" font="default" size="100%">sparql</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2009</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/howison2008.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">15-22</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract><notes><style face="normal" font="default" size="100%">non-experimental</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hauge, Øyvind</style></author><author><style face="normal" font="default" size="100%">Sørensen, Carl-Fredrik</style></author><author><style face="normal" font="default" size="100%">Conradi, Reidar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Adoption of Open Source in the Software Industry</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Adaption of Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">211 - 221</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Is Open Source Software (OSS) undergoing a transformation to a more commercially viable form? We have performed a survey to investigate the adoption of OSS in the Norwegian software industry. The survey was based on an extensive screening of software companies, with more than 700 responses. The survey results support the transformation predicted by Fitzgerald [4]. Close to 50% of the software industry integrate OSS components into vertical solutions serving all major business sectors. In addition, more than 30% of the 95 respondents in our survey have more than 40% of their income from OSS related services or software. The extensive adoption of OSS in the software industry may be a precursor of the OSS adoption in other business sectors.
</style></abstract><section><style face="normal" font="default" size="100%">17</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kamei, Yasutaka</style></author><author><style face="normal" font="default" size="100%">Matsumoto, Shinsuke</style></author><author><style face="normal" font="default" size="100%">Maeshima, Hirotaka</style></author><author><style face="normal" font="default" size="100%">Onishi, Yoji</style></author><author><style face="normal" font="default" size="100%">Ohira, Masao</style></author><author><style face="normal" font="default" size="100%">Matsumoto, Ken-ichi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysis of Coordination Between Developers and Users in the Apache Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Analysis of Coordination.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">81 - 92</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Coordination is one of the keys for the success of open source software (OSS) communities because geographically distributed members need to collaborate on their work using communication tools (e.g., mailing lists, bulletin board systems, bug tracking systems, and so on). In this paper, we investigated the informal social structure among developers and users by analyzing two mailing lists of developers and users in the Apache community based on betweenness centrality, one centrality measure proposed by Freeman. From the analysis results, we found that (1) participants with high betweenness coordinated activities between developers and users and (2) some participants have been functioning as coordinators in the community for a long time.
</style></abstract><section><style face="normal" font="default" size="100%">7</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Juho Lindman</style></author><author><style face="normal" font="default" size="100%">Rossi, Matti</style></author><author><style face="normal" font="default" size="100%">Marttiin, Pentti</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Applying Open Source Development Practices Inside a Company</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Applying Open Source Development.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">381 - 387</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software development is seen as a panacea by many companies. The promise of community-style development, innovation and cost savings drive the wider adoption of OSS in companies. However, it is still difficult to institutionalize the open and agile culture of sharing innovation especially into larger departmentalized organizations. The aim of this research paper is to investigate the characteristics of one successful OSS development implementation approach limited inside a company (Inner source). Based on our data, we argue that there are possibilities for employing OSS as a new kind of development process within a company and leveraging thus the innovation potential inside the company.
</style></abstract><section><style face="normal" font="default" size="100%">36</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Umarji, Medha</style></author><author><style face="normal" font="default" size="100%">Sim, Susan</style></author><author><style face="normal" font="default" size="100%">Lopes, Crista</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Archetypal Internet-Scale Source Code Searching</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Archetypal Internet-Scale Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">257 - 263</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Programmers often search for Open Source code to use in their projects. To understand how and why programmers search for source code, we onducted a web-based survey and collected data from 69 respondents, including 58 specific examples of searches. Analyzing these anecdotes, we found that they could be categorized along two orthogonal dimensions: motivation (reuse vs. reference example) and size of search target. The targets of these searches could range in size from a block (a few lines of code) to a subsystem (e.g. library or API), to an entire system. Within these six combinations of motivations and target sizes, nine repeating motifs, or archetypes, were created to characterize Internet-scale source code searching. Tools used for searching and the criteria for selecting a component are also discussed. We conclude with guidance on how these archetypes can inform better evaluation of Internet-scale code search engines, as well as the design of new features for these tools.
</style></abstract><section><style face="normal" font="default" size="100%">21</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dario Lorenzi</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assessing Innovation in the Software Sector: Proprietary vs. FOSS Production Mode. Preliminary Evidence from the Italian Case</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Assessing Innovation in the Software Sector.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">325 - 331</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Innovation in the software sector is a widely debated issue. Which are the most important dimensions to assess innovation in this field? Can we measure innovative processes carried out by software companies and what kind of innovation do they develop? Are FOSS solutions more innovative than proprietary ones? These are the research questions we endeavor to answer in this paper providing some empirical evidence, obtained using an original methodology of collecting experts’ evaluations on the innovation level of 134 solutions provided by a group of Italian Small and Medium Enterprises.
</style></abstract><section><style face="normal" font="default" size="100%">29</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Masmoudi, Héla</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Channeling Firefox Developers: Mom and Dad Aren’t Happy Yet</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Channeling Firefox Developers.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">265 - 271</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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’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 “alpha-geek power user” in the early stages of development, it also makes it difficult for “mom and dad” to let their voice be heard even after they have adopted Firefox.
</style></abstract><section><style face="normal" font="default" size="100%">22</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Amit Deshpande</style></author><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Continuous Integration in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Continous Integration.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">273 - 280</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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’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.
</style></abstract><section><style face="normal" font="default" size="100%">23</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Adams, Paul</style></author><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">de Groot, Adriaan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Detecting Agility of Open Source Projects Through Developer Engagement</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Detecting Agility of Open Source Projects.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">333 - 341</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The principles behind the agile development methods and common practise within the Open Source community are vastly different. In recent years there has been a rise of interest in these, in order to detect and inform on areas of compatible shared practises. This paper argues that it is possible to quantify the level of agility displayed by Open Source projects. An indicator of agility, the Mean Developer Engagement (MDE) metric is introduced and tested through the analysis of public project data. Projects sampled from two repositories (KDE and SourceForge) are studied and a hypothesis is formulated: projects from the two samples display a similar level of MDE. This paper provides two main contributions: first, the MDE metric is shown to vary significantly between the KDE and SourceForge projects. Second, by combining MDE with a project’s lifespan, it is also shown that SourceForge projects have insufficient uptake of new developers resulting in more active, shorter, initial activity, and in a quicker “burning out” of the projects.
</style></abstract><section><style face="normal" font="default" size="100%">30</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Francalanci, Chiara</style></author><author><style face="normal" font="default" size="100%">Merlo, Francesco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Empirical Analysis of the Bug Fixing Process in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Empirical Analysis of the Bug Fixinf Process.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">187 - 196</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Monitoring the performance of processes is often considered critical in classic engineering fields. However, in the area of software engineering (and especially in the Open Source context) it seems that the literature has not yet taken into consideration the problem of identifying the process characteristics and performance of debugging. The aim of this paper is the identification of the performance characteristics of the bug fixing process of Open Source applications, focusing on continuity and efficiency indicators. The importance of such indicators is even more relevant today, since Open Source software is now adopted also in many business contexts. We have analyzed the debugging process of 9 active and popular Open Source projects, collecting a dataset comprising more than 65,000 closed bugs. Results have highlighted four types of bug fixing processes that can be distinguished by considering temporal continuity and efficiency dimensions.
</style></abstract><section><style face="normal" font="default" size="100%">15</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">eResearch Workflows for Studying Free and Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/eResearch Workflows.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">405 - 411</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology,then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one—Taverna—and introducing its features.To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.
</style></abstract><section><style face="normal" font="default" size="100%">39</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Torkar, Richard</style></author><author><style face="normal" font="default" size="100%">Feldt, Robert</style></author><author><style face="normal" font="default" size="100%">Gorschek, Tony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Extracting Generally Applicable Patterns from Object-Oriented Programs for the Purpose of Test Case Creation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Extracting Generally Applicable Patterns.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">281 - 287</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents an experiment performed on three large open source applications. The applications were instrumented automatically with a total of 10,494 instrumentation points. The purpose of the instrumentation was to collect and store data during the execution of each application that later could be analyzed off-line. Data analysis, on the collected data, allowed for the creation of test cases (test data, test fixtures and test evaluators) in addition to finding object message patterns for object-oriented software.
</style></abstract><section><style face="normal" font="default" size="100%">24</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Balieiro, Marco</style></author><author><style face="normal" font="default" size="100%">de Júnior, Samuel</style></author><author><style face="normal" font="default" size="100%">De Souza, Cleidson</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Facilitating Social Network Studies of FLOSS using the OSSNetwork Environment</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Facilitating Social Network Studies.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">343 - 350</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source projects are typical examples of successful distributed software development projects. Understanding how coordination in these projects takes place can provide important lessons to Software Engineering researchers and practitioners. This understanding has been achieved using different research methods, including, surveys, case studies and social network analysis. However, to conduct these studies each researcher needs to build his own infra-structure from the scratch, a time consuming and error-prone task. This paper aims to alleviate this problem by describing an environment, the OSSNetwork, which allows the automatic data collection of open source repositories. Data collected by the OSSNetwork is aimed to support the construction, visualization, and analysis of social networks. This environment is extensible, therefore facilitating empirical studies of open source projects.
</style></abstract><section><style face="normal" font="default" size="100%">31</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Järvensivu, Juha</style></author><author><style face="normal" font="default" size="100%">Mikkonen, Tommi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Forging A Community – Not: Experiences On Establishing An Open Source Project</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/forging a community.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">15 - 27</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source has recently become a practical and advocated fashion to develop, integrate, and license software. As a consequence, open source communities that commonly perform the development work are becoming important in the practice of software engineering. A community that is lively can often produce high-quality systems that continuously grow in terms of features, whereas communities that do not gain interest will inevitably perish. Despite their newly established central role, creation, organization, and management of such communities have not yet been widely studied from the viewpoint of software engineering practices. In this paper, we discuss experiences gained in the scope of Laika, an open source project established to develop an integrated software development environment for developing applications that run in Linux based mobile devices.
</style></abstract><section><style face="normal" font="default" size="100%">2</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capra, Eugenio</style></author><author><style face="normal" font="default" size="100%">Wasserman, Anthony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Framework for Evaluating Managerial Styles in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/framework for evaluating Mangerial Style.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">1 - 14</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents the Software Project Governance Framework (SPGF) for characterizing management of software projects, based on mechanisms used for communication and collaboration, the organizational structure of projects, and testing and quality assurance procedures. The framework was developed and validated from interviews and surveys with leaders of more than 70 commercial and community-based software projects, including both closed and open source projects.
</style></abstract><section><style face="normal" font="default" size="100%">1</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Corbiere, Alain</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Framework to Abstract The Design Practices of e-Learning System Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A Framework to Abstract the Design Project.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">317 - 323</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The use of ALT (Advanced Learning Technologies) creates dynamic sharing and exchanging between open source communities that diffuse e-learning systems. In our opinion, the designer practices define new perspectives on e-learning design which are not structured and highlighted enough. This article shows the capabilities of a generic framework to analyse the design practices on a open source project and to explicit these practices. We describe how the semantics for architectural specifications proposed by RM-ODP (Reference Model-Open Distributed Process) framework were applied on an e-learning system project to analyse the principles of invariants, structural and functional.
</style></abstract><section><style face="normal" font="default" size="100%">28</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Melian, Catharina</style></author><author><style face="normal" font="default" size="100%">Mähring, Magnus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Lost and Gained in Translation: Adoption of Open Source Software Development at Hewlett-Packard</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Lost &amp; Gained in Translation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">93 - 104</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">What happens when an organization form that has emerged in one context is brought into a different context? In this paper, a longitudinal field study approach is used to explore how Hewlett-Packard (HP) molded open source software development (OSSD) into a proprietary software development approach called “Progressive Open Source” (POS). With the help of actornetwork theory, we understand this as a process of translation and find that some central characteristics of OSSD where lost in the translation into POS while other characteristics were gained.
</style></abstract><section><style face="normal" font="default" size="100%">8</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, C.</style></author><author><style face="normal" font="default" size="100%">Damiani, E.</style></author><author><style face="normal" font="default" size="100%">Ioini, N.</style></author><author><style face="normal" font="default" size="100%">Frati, F.</style></author><author><style face="normal" font="default" size="100%">Giovannini, P.</style></author><author><style face="normal" font="default" size="100%">Tchokpon, R.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mapping Linux Security Targets to Existing Test Suites</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Mapping Linux Security Targets.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">29 - 45</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Common Criteria standard provides an infrastructure for evaluating security functions of IT products and for certifying that security policies claimed by product suppliers are correctly enforced by the security functions themselves. Certifying Open Source software (OSS) can pave the way to OSS adoption in a number of security-conscious application environments. Recent experiences in certifying Linux distributions has pointed out the problem of finding a mapping between descriptions of OSS security functions and existingtest suites developed independently, such as the Linux Test Project. In this paper, we describe a mechanism, based on matching techniques, which semiautomatically associates security functions to existing test suite such as the ones developed by Open Source communities.
</style></abstract><section><style face="normal" font="default" size="100%">3</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dobusch, Leonhard</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Migration Discourse Structures: Escaping Microsoft’s Desktop Path</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Migration Discourse Structure.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">223 - 235</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Most studies of FOSS organizational migration projects focus solely on technological and economical aspects, neglecting the importance of organizational discourse structures for migration decisions as well as success. In looking at the case of the municipality of Munich this paper uses structuration theory in combination with discourse analysis to explain why and how in this case actors were able to overcome strong barriers to migration in the field of desktop software.
</style></abstract><section><style face="normal" font="default" size="100%">18</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Rossi, Alessandro</style></author><author><style face="normal" font="default" size="100%">Gaio, Loris</style></author><author><style face="normal" font="default" size="100%">Loubser, Max</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining for Practices in Community Collections: Finds From Simple Wikipedia</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Mining for Practices.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">105 - 120</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The challenges of commons based peer production are usually associated with the development of complex software projects such as Linux and Apache. But the case of open content production should not be treated as a trivial one. For instance, while the task of maintaining a collection of encyclopedic articles might seem negligible compared to the one of keeping together a software system with its many modules and interdependencies, it still poses quite demanding problems. In this paper, we describe the methods and practices adopted by Simple Wikipedia to keep its articles easy to read. Based on measurements of article readability and similarity, we conclude that while the mechanisms adopted by the community had some effect, in the long run more efforts and new practices might be necessary in order to maintain an acceptable level of readability in the Simple Wikipedia collection.
</style></abstract><section><style face="normal" font="default" size="100%">9</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author><author><style face="normal" font="default" size="100%">Martínez, Andrés</style></author><author><style face="normal" font="default" size="100%">Polo, Alvaro</style></author><author><style face="normal" font="default" size="100%">Hierro, Juan</style></author><author><style face="normal" font="default" size="100%">Reyes, Marcos</style></author><author><style face="normal" font="default" size="100%">Soriano, Javier</style></author><author><style face="normal" font="default" size="100%">Fernández, Rafael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Networked Forge: New Environments for Libre Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Networked Forge.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">299 - 306</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Libre (free, open source) software forges (sites hosting the development infrastructure for a collection of projects) have been stable in architecture, services and concept since they become popular during the late 1990s. During this time several problems that cannot be solved without dramatic design changes have become evident. To overcome them, we propose a new concept, the “networked forge”, focused on addressing the core characteristics of libre software development and the needs of developers. The key of this proposal is to re-engineer forges as a net of distributed components which can be composed and configured according to the needs of users, using a combination of web 2.0, semantic web and mashup technologies. This approach is flexible enough to accommodate different development processes, while at the same time interoperates with current facilities.
</style></abstract><section><style face="normal" font="default" size="100%">26</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Acampora, Giovanni</style></author><author><style face="normal" font="default" size="100%">Loia, Vincenzo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Open Integrated Environment for Transparent Fuzzy Agents Design</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/An Open Integrated Environment.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">249 - 255</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Recently, computational agents received significant attention in computer science research community. In fact, intelligent agents is a powerful artificial intelligence technology showing considerable promise as a new paradigm for mainstream software development and able to offer new ways of abstraction, decomposition, and organization that fit well with our natural view of the world. However, despite their promise, intelligent agents are still scarce in the market place. A key reason for this is that developing intelligent agent software requires significant training and skill. Artificial Intelligence methodologies and computer networking tools represent the necessary basic knowledge to design and implement advanced agents oriented systems. This papers introduces an integrated development environment supporting the agents developers to design fuzzy-based agents in a simple and fast way. Proposed framework has been realized by integration of theoretical methodologies as fuzzy logic and labeled tree, together with OSS tools as JaxMe2.
</style></abstract><section><style face="normal" font="default" size="100%">20</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bosin, Andrea</style></author><author><style face="normal" font="default" size="100%">Dessí, Nicoletta</style></author><author><style face="normal" font="default" size="100%">Fugini, Maria</style></author><author><style face="normal" font="default" size="100%">Liberati, Diego</style></author><author><style face="normal" font="default" size="100%">Pes, Barbara</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Environments for Collaborative Experiments in e-Science</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Environments.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">415 - 416</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) for e-Science should make reference to the paradigm of a distributed surrounding over a multi system mix of Web Services and Grid technologies, allowing data exchanging through services, according to standards in the area of the Grid and of Service Oriented Computing (SOC). In fact, biologists, medical doctors, and scientists are often involved in time consuming experiments and are aware of the degree of difficulty in validating or rejecting a given hypothesis by lab experiments. The benefits of OSS for e-Science consider that as many operating nodes as possible can work cooperatively sharing data, resources, and software, thus avoiding the bottleneck of licenses for distributed use of tools needed to perform cooperative scientific experiments. In particular, this chapter presents an architecture based on nodes equipped with a Grid and with Web Services in order to access OSS, showing how scientific experiments can be enacted through the use of a cooperation among OSS sites. Such a choice, besides reducing the cost of the experiments, would support distributed introduction of OSS among other actors of the dynamical networks, thus supporting the awareness about OSS and their diffusion. An OSS environment for cooperative scientific experiments (e-experiments) can effectively support the distributed execution of different classes of experiments, from visualization to model identification through clustering and rules generation, in various application fields, such as bioinformatics, neuro-informatics, tele-monitoring,or drug discovery. By applying Web Services and Grid computing, an experiment or a simulation can be executed in a cooperative way on various computation nodes of a network equipped with OSS, allowing data exchange among researchers. Our environment  formalizes experiments as cooperative services on various computational nodes of a grid network. Basic elements are models, languages, and support tools creating a virtual
network of organizational responsibility of the global experiments, according to rules under which each node can execute local services to be accessed by other nodes in order to achieve the whole experiment’s results.
</style></abstract><section><style face="normal" font="default" size="100%">41</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author><author><style face="normal" font="default" size="100%">Stix, Volker</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Project Categorization Based on Growth Rate Analysis and Portfolio Planning Methods</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Project Categorization.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">375 - 380</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we propose to arrive at an assessment and evaluation of open source projects based on an analysis of their growth rates in several aspects. These include code base, developer number, bug reports and downloads. Based on this analysis and assessment, a well-known portfolio planning method, the BCG matrix, is employed for arriving at a very broad classification of open source projects. While this approach naturally results in a loss of detailed information, a top-level categorization is in some domains necessary and of interest.
</style></abstract><section><style face="normal" font="default" size="100%">35</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mayoue, Aurélien</style></author><author><style face="normal" font="default" size="100%">Petrovska-Delacrétaz, Dijana</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Reference Systems for Biometric Verification of Identity</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Reference Systems.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">397 - 404</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper focuses on the common evaluation framework which was developed by the BioSecure Network of Excellence during the European FP6 project BioSecure (Biometrics for Secure authentication). This framework, which is composed of open-source reference systems, publicly available databases, assessment protocols and benchmarking results, introduces a new experimental methodology for conducting, reporting and comparing experiments for biometric systems, participating to standardisation efforts. Its use will permit to make a link between different published works. It provides also the necessary tools to assure the reproducibility of the benchmarking biometric experiments. This framework can be considered as a re-liable and innovative process to evaluate the progress of research in the field of bio-metrics.
</style></abstract><section><style face="normal" font="default" size="100%">38</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">D’Andrea, Vincenzo</style></author><author><style face="normal" font="default" size="100%">De Paoli, Stefano</style></author><author><style face="normal" font="default" size="100%">Teli, Maurizio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open to Grok. How do Hackers’ Practices Produce Hackers?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open to Grok.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">121 - 129</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">How do hackers’ practices produce hackers’ identities? In this paper we argue that the association between science fiction and software programs is rooted in hackers’ practices, defining how hackers’ knowledge’ emerge. The mediation is the one of the Heinlein verb “to grok”, part of the Jargon file and of the name of a code browser, OpenGrok, the technology mediating the relationship between OpenSolaris developers and the code base. Starting with a description of the peculiarity of the verb “to grok”, and its connection with a non-Cartesian view of knowledge, we discuss how the history of OpenGrok and its use by developers make this knowledge part of hackers’ practices and identities, as someone involved in a true, deep understanding of software.
</style></abstract><section><style face="normal" font="default" size="100%">10</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Petrinja, Etiel</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Overview on Trust in Large FLOSS Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Overview on Trust.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">47 - 56</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper presents a survey of mature Free/Libre Open Source Software communities. The main focus of the survey is the collection of data related to the practices of these communities related to trust elements in their products. The survey is carried out using a structured questionnaire about thoughts and practices followed by Free/Libre Open Source Software communities. The survey focuses on the analysis of the development processes adopted by such communities. The results of the survey confirms basic ideas related to Free/Libre Open Source Software and explains in more detail specific issues related to trust and trustworthiness of the Free/Libre Open Source Software development process.
</style></abstract><section><style face="normal" font="default" size="100%">4</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Feller, Joseph</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Marttiin, Pentti</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Schellingerhout, Nico</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Panel: Opportunities and Risks for Open Source Software in Industry</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Panel Opportunities &amp; Risks.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">413 - 414</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) is a multi-faceted phenomenon which has become an issue of strategic importance for many commercial organisations. Stemming from an ideological issue, with emphasis on freedom and community values, we have recently seen a broader interest in the Open Source phenomenon amongst practitioners in many companies. A number of SMEs and large companies are currently exploring the potential of Open Source, and for some it has become core to their business and development activities.
</style></abstract><section><style face="normal" font="default" size="100%">40</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Colombo, Alberto</style></author><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">PMLite: An Open Source Solution for Process Monitoring</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/PMLite.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">57 - 68</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Process Monitoring represents a big challenge for organizations that aim to manage software projects adopting different development paradigms. In fact, across-process enterprise-level measurement campaigns can be difficult to enact since process attributes to retrieve are semantically diverse and may be difficult to integrate. In this paper, we present PMLite (Process Monitoring Lite) an open source solution to this problem. PMLite is based on an open metamodel and paves the way to the definition of ad-hoc open monitoring frameworks.
</style></abstract><section><style face="normal" font="default" size="100%">5</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reflection on Knowledge Sharing in F/OSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Reflection on Knowledge Sharing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">351 - 358</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Knowledge sharing between software project participants simplifies a range of decision-making processes and helps improve the way software is being developed, distributed, and supported. However, research in this area has traditionally been very difficult because the source of knowledge, the code, has been a guarded secret and software developers and users inhabit different worlds. F/OSS projects have changed the way we perceive and understand knowledge sharing in distributed software development. This short paper presents our current understanding, and what needs to be done in terms of empirical research in knowledge sharing in F/OSS projects.
</style></abstract><section><style face="normal" font="default" size="100%">32</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Noll, John</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Requirements Acquisition in Open Source Development: Firefox 2.0</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Requirements Acquisition.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">69 - 79</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines features of the latest major release of the Firefox web browser in attempt to understand how prevalent this phenomenon is. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, to determine the process by which requirements are proposed, adopted, and implemented in Firefox. The results confirm the importance of user participation as developers of open source products.
</style></abstract><section><style face="normal" font="default" size="100%">6</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Wiggins</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social Dynamics of FLOSS Team Communication Across Channels</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Social Dynamics of Floss.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">131 - 142</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper extends prior investigation into the social dynamics of free and open source (FLOSS) teams by examining the methodological questions arising from research using social network analysis on open source projects. We evaluate the validity of data sampling by examining dynamics of communication centralization, which vary across multiple communication channels. We also introduce a method for intensity-based smoothing in dynamic social network analysis.
</style></abstract><section><style face="normal" font="default" size="100%">11</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Di Cerbo, Francesco</style></author><author><style face="normal" font="default" size="100%">Dodero, Gabriella</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social Networking Technologies for Free-Open Source E-Learning Systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Social Networking Technologies.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">289 - 297</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we illustrate our methodology for academic teaching, based on cooperative learning paradigm, which also relies on cutting edge e-learning techniques. We use Web 2.0 resources to fulfill requirements for an interactive-constructivistic “learning space”, where blended-teaching paradigm may be proficiently applied. We extend an existing Free/Open Source Software Learning Management System, to create a cooperative and community-based learning space adherent to our proposal.
</style></abstract><section><style face="normal" font="default" size="100%">25</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Samoladas, Ioannis</style></author><author><style face="normal" font="default" size="100%">Gousios, Georgios</style></author><author><style face="normal" font="default" size="100%">Diomidis Spinellis</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The SQO-OSS Quality Model: Measurement Based Open Source Software Evaluation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/SQO-OSS Quality Model.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">237 - 248</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software quality evaluation has always been an important part of software business. The quality evaluation process is usually based on hierarchical quality models that measure various aspects of software quality and deduce a characterization of the product quality being evaluated. The particular nature of open source software has rendered existing models inappropriate for detailed quality evaluations. In this paper, we present a hierarchical quality model that evaluates source code and community processes, based on automatic calculation of metric values and their correlation to a set of predefined quality profiles.1
</style></abstract><section><style face="normal" font="default" size="100%">19</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Banzi, Massimo</style></author><author><style face="normal" font="default" size="100%">Bruno, Guido</style></author><author><style face="normal" font="default" size="100%">Caire, Giovanni</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">To What Extent Does It Pay to Approach Open Source Software for a Big Telco Player?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/To What Extent Does it Pay to Approach.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">307 - 315</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we describe the strategy under adoption in Telecom Italia (TI) Technology Department toward open source software. This stems from trying to create synergy among big Telco Player to increase knowledge and influence over strategic communities to the evaluation of the creation of new communities over internally developed applications. In particular here the approach and the expectations in starting the community on WADE (Workflow and Agent Development Environment) is described. This is a platform used to develop mission critical applications and is the main evolution of JADE a popular Open Source framework for the development of interoperable intelligent multi-agent systems. It adds to JADE the support for the execution of tasks defined according to the workflow metaphor as well as a number of mechanisms that help managing the complexity of the distribution both in terms of administration and fault tolerance. The idea is to use WADE as a mean to gather critical information on the opportunity of approaching OS as a strategic mean toward the development of always more important application in Operating Support System for TI, possibly also involving other great Telco Players For this reason great care is being paid in setting up the Community environment and in deciding which metrics are to be extracted from it, since the result will be the input for a strategic decision in TI.
</style></abstract><section><style face="normal" font="default" size="100%">27</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Amit Deshpande</style></author><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Total Growth of Open Source</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Total Growth of Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">197 - 209</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software development is undergoing a major change away from a fully closed software process towards a process that incorporates open source software in products and services. Just how significant is that change? To answer this question we need to look at the overall growth of open source as well as its growth rate. In this paper, we quantitatively analyze the growth of more than 5000 active and popular open source software projects. We show that the total amount of source code as well as the total number of open source projects is growing at an exponential rate. Previous research showed linear and quadratic growth in lines of source code of individual open source projects. Our work shows that open source is expanding into new domains and applications at an exponential rate.
</style></abstract><section><style face="normal" font="default" size="100%">16</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gasser, Les</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Towards a Global Research Infrastracture.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">143 - 158</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Free/Open Source Software (F/OSS) research community is growing across and within multiple disciplines. This community faces a new and unusual situation. The traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available public data from many disparate sources (online discussion forums, source code directories, bug reports, OSS Web portals, etc.). Consequently, these data are being discovered, gathered, analyzed, and used to support multidisciplinary research. However at present, no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research across disciplines. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on direct access to, and mining of raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper, we identify several needs and critical factors in F/OSS empirical research across disciplines, and suggest recommendations for design of a global research infrastructure for multi-disciplinary research into F/OSS development.
</style></abstract><section><style face="normal" font="default" size="100%">12</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Taibi, Davide</style></author><author><style face="normal" font="default" size="100%">del Bianco, Vieri</style></author><author><style face="normal" font="default" size="100%">Carbonare, Davide</style></author><author><style face="normal" font="default" size="100%">Lavazza, Luigi</style></author><author><style face="normal" font="default" size="100%">Morasca, Sandro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards The Evaluation of OSS Trustworthiness: Lessons Learned From The Observation of Relevant OSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Toward the Evaluation of OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">389 - 395</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">To facilitate the adoption of open-source software (OSS) in industry, it is important to provide potential users (i.e., those who could decide to adopt OSS) with the means for evaluating the trustworthiness of OS products. This paper presents part of the work done in the QualiPSo project for this purpose. A set of factors that are believed to affect the perception of trustworthiness are introduced. In order to test the feasibility of deriving a correct, complete and reliable evaluation of trustworthiness on the basis of these factors, a set of well-known OSS projects have been chosen. Then, the possibility to assess the proposed factors on each project was verified: not all the factors appear to be observable or measurable. The paper reports what information is available to support the evaluation and what is not. This knowledge is considered to be useful to users, who are warned that there are still dark areas in the characterization of OSS products, and to developers, who should provide more data and characteristics on their products in order to support their adoption.
</style></abstract><section><style face="normal" font="default" size="100%">37</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Orsila, Heikki</style></author><author><style face="normal" font="default" size="100%">Geldenhuys, Jaco</style></author><author><style face="normal" font="default" size="100%">Ruokonen, Anna</style></author><author><style face="normal" font="default" size="100%">Hammouda, Imed</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Update Propagation Practices in Highly Reusable Open Source Components</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Update Propagation Practice.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">159 - 170</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In today’s business and software arena, more and more companies are adopting open source software. An example of this rising phenomenon is to base software products on highly reusable open source components. In this scenario, the evolution of the software product is coupled with the evolution of the open source component. A common assumption is that component updates are immediately and regularly propagated to the project. This paper investigates this assumption empirically by studying update propagation practices in two popular open source libraries, zlib and FFmpeg. For each library, we analyze various repository sources with information such as bug reports, revision history, and source code. The results of the case studies suggest that update propagation is subject to several technical and non-technical factors including the way the open source library is used, the extent to which updates are documented, and the degree of community involvement. Based on these findings, we propose a set of recommendations that would allow better follow-up of updates and smoother update propagation.
</style></abstract><section><style face="normal" font="default" size="100%">13</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Iivari, Netta</style></author><author><style face="normal" font="default" size="100%">Hedberg, Henrik</style></author><author><style face="normal" font="default" size="100%">Kirves, Tanja</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Usability in Company Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">359 - 365</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In the company open source software (OSS) development context, usability is becoming an important issue due to a growing user population, who is only interested in usable applications, not in their development. Companies try to gain a competitive advantage of OSS by utilizing available components, but the openness is difficult to achieve in the business world with licenses, patents and intellectual property rights. This paper analyses usability and user-interface (UI) development in the company OSS context through an interpretive case study in a software development unit of a large, global corporation. Our initial findings suggest that there is a need for human computer interaction specialists in the OSS context. It is revealed that with the software based on OSS, more time can be spent on usability and UI design. In the company’s viewpoint, there are still many issues involved in deciding what parts of the product will be open source. Especially UI code may remain closed due to competitive advantage and patents.
</style></abstract><section><style face="normal" font="default" size="100%">33</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martinez-Romo, Juan</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author><author><style face="normal" font="default" size="100%">Ortuño-Perez, Miguel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Social Network Analysis Techniques to Study Collaboration between a FLOSS Community and a Company</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Using Social Network.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">171 - 186</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Because of the sheer volume of information available in FLOSS repositories, simple analysis have to face the problems of filtering the relevant information. Hence, it is essential to apply methodologies that highlight that information for a given aspect of the project. In this paper, some techniques from the social sciences have been used on data from version control systems to extract information about the development process of FLOSS projects with the aim of highlighting several processes that occur in FLOSS projects and that are difficult to obtain by other means. In particular, the collaboration between the FLOSS community and a company has been studied by selecting two projects as case studies. The results highlight aspects such as efficiency in the development process, release management and leadership turnover.
</style></abstract><section><style face="normal" font="default" size="100%">14</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ravesteyn, Pascal</style></author><author><style face="normal" font="default" size="100%">Silvius, Gilbert</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Willingness to Cooperate Within the Open Source Software Domain</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Willingness to Cooperate.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">275/2008</style></volume><pages><style face="normal" font="default" size="100%">367 - 373</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) is an increasingly hot topic in the business domain. One of the key benefits mentioned is the unlimited access to the source code, which enables large communities to continuously improve a software application and prevents vendor lock-in. How attractive these benefits may be, the market for OSS however remains limited. In the Netherlands research consisting of 7 interviews and a survey among 206 Open Source Software Service providers (with a 34% response rate) was done to determine whether service providers wanted to cooperate in an Association that will set quality levels and guarantees to its members and their customers.
</style></abstract><section><style face="normal" font="default" size="100%">34</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Taylor, Quinn C.</style></author><author><style face="normal" font="default" size="100%">Stevenson, James E.</style></author><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Author Entropy: A Metric for Characterization  of Software Authorship Patterns</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">entropy</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/entropy2008.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">42-47</style></pages><abstract><style face="normal" font="default" size="100%">We propose the concept of author entropy and describe how ﬁle-level entropy measures may be used to understand and characterize authorship patterns within individual ﬁles, as well as across an entire project. As a proof of concept, we compute author entropy for 28,955 ﬁles from 33 open-source projects. We explore patterns of author entropy, identify techniques for visualizing author entropy, and propose avenues for further study. </style></abstract><notes><style face="normal" font="default" size="100%">used flossmole to get sample of SF developers</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Computer support for discovering oss processes</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">artifacts</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">process management</style></keyword><keyword><style  face="normal" font="default" size="100%">zotero</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/jensen2008.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">31-33</style></pages><abstract><style face="normal" font="default" size="100%">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. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wray, Barry</style></author><author><style face="normal" font="default" size="100%">Mathieu, Richard</style></author><author><style face="normal" font="default" size="100%">Teets, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating the performance of open source software projects using data envelopment analysis</style></title><secondary-title><style face="normal" font="default" size="100%">Information Management &amp; Computer Security</style></secondary-title><short-title><style face="normal" font="default" size="100%">Information Management &amp; Computer Security</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">dea</style></keyword><keyword><style  face="normal" font="default" size="100%">efficiency</style></keyword><keyword><style  face="normal" font="default" size="100%">Project performance</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2008</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">16</style></volume><pages><style face="normal" font="default" size="100%">449 - 462</style></pages><abstract><style face="normal" font="default" size="100%">	

Purpose – The purpose of this paper is to develop and test a model of the relative performance of open source software (OSS) projects.

Design/methodology/approach – This paper evaluates the relative performance of OSS projects by evaluating multiple project inputs and multiple project outputs by using a data envelopment analysis (DEA) model. The DEA model produces an efficiency score for each project based on project inputs and outputs. The method of producing an efficiency score is based on the convex envelopment technology structure. The efficiency measure quantifies a “distance” to an efficient frontier.

Findings – The DEA model produced an index of corresponding intensities linking an inefficient project to its benchmark efficient project(s). The inefficiency measures produced an ordering of inefficient projects. Eight projects were found to be “efficient” and used as benchmarking projects.

Research limitations/implications – This research is limited to only security-based OSS projects. Future research on other areas of OSS projects is warranted.

Practical implications – The result of this research is a practical model that can be used by OSS project developers to evaluate the relative performance of their projects and make resource decisions.

Originality/value – This research extends the work of previous studies that have examined the relative performance of software development projects in a traditional development environment. As a result of this research, OSS projects can now be adequately benchmarked and evaluated according to project performance. An OSS project manger can effectively use these results to critically evaluate resources for their project and judge the relative efficiency of the resources.</style></abstract><issue><style face="normal" font="default" size="100%">5</style></issue><notes><style face="normal" font="default" size="100%">&quot;The data set used for this research consists of 34 OSS software projects listed on sourceforge.net.&quot; &quot;only highly ranked projects in the security domain were considered.&quot;
&quot;Ultimately data were collected on the 34 highest ranked security-based OSS software projects on Sourcefore.net.&quot;[sic]
fields: bug (?), developers, rank, downloads, Kperdownload (?)</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Effort modeling and programmer participation in open source software projects</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy (Empirical Issues in Open Source Software)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">Software repository mining</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">12/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V8J-4SSND1J-1/2/c857fa1493e19aa7fe4297dedb077b3a</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/KochEffortModeling.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">345 - 355</style></pages><abstract><style face="normal" font="default" size="100%">This paper develops models for programmer participation and effort estimation in open source software projects and employs the results to assess the efficiency of open source software creation. Successful development of such models will be important for decision makers of various kinds. We propose hypotheses based on a prior case study on manpower function and effort modeling. A large data set retrieved from a project repository is used to test these hypotheses. The main results are that if Norden-Rayleigh-based approaches are used, they need to be complemented in order to account for the addition of new features during a product life cycle, and that programmer-participation based effort models result in distinctly lower estimations of effort than those based on output metrics, such as lines of code.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Using a two-step approach, first a detailed case study on one project, GNOME, will be undertaken, then a large data set retrieved from a project hosting site, SourceForge.net, will be used to validate the results.&quot;

CVS was the main source of data

&quot;e-mails sent to the different project discussion lists were identified as an additional source of information especially on communication and coordination besides the CVS-repository&quot;

basic counts were calculated for developer discussion levels</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mateos Garcia, J.</style></author><author><style face="normal" font="default" size="100%">Steinmueller, W.E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The institutions of open source software: Examining the Debian community☆</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></secondary-title><short-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">authority</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">conflict</style></keyword><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">decentralization</style></keyword><keyword><style  face="normal" font="default" size="100%">growth</style></keyword><keyword><style  face="normal" font="default" size="100%">institutions</style></keyword><keyword><style  face="normal" font="default" size="100%">leadership</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">12/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/The_institutions_of_open_source_software-_IR.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">333 - 344</style></pages><abstract><style face="normal" font="default" size="100%">Free and open source software activities involve and, perhaps, evolve institutions (rules, norms and standards) that influence the formation, growth, and demise of communities. Community institutions are attractors for some individuals while discouraging other individuals from entering or continuing to participate. Their suitability may change as a community grows. This paper examines the institutions of the Debian community where issues of community identity, distribution of authority, and decentralisation have facilitated growth and development. These same institutions have also resulted in conflicts regarding community purposes and the quality and delivery of the community’s output. We examine the institutional redesign undertaken to address these problems and derive implications for F/LOS communities and companies.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue><notes><style face="normal" font="default" size="100%">&quot;using primary data from its mailing lists archives, handbooks written to inform potential and actual community members, and previous analyses of institutional evolution and political conflict&quot;

no discussion of which lists, how many, or when they were gathered...?[ms]</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capra, E.</style></author><author><style face="normal" font="default" size="100%">Francalanci, C.</style></author><author><style face="normal" font="default" size="100%">Merlo, F.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">IEEE Transactions on Software Engineering</style></secondary-title><short-title><style face="normal" font="default" size="100%">IIEEE Trans. Software Eng.</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">effort estimation</style></keyword><keyword><style  face="normal" font="default" size="100%">governance</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">11/2008</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">34</style></volume><pages><style face="normal" font="default" size="100%">765 - 782</style></pages><abstract><style face="normal" font="default" size="100%">The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.</style></abstract><issue><style face="normal" font="default" size="100%">6</style></issue><notes><style face="normal" font="default" size="100%">&quot;empirical data from a sample of 75 major OS projects&quot;
no PDF to confirm [ms]</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Samoladas, Ioannis</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Lefteris Angelis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Are FLOSS developers committing to CVS/SVN as much as  they are talking in mailing lists? Challenges for Integrating  data from Multiple Repositories</style></title><secondary-title><style face="normal" font="default" size="100%">3rd Workshop on Public Data about Software Development (WoPDaSD 2008)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmetrics</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">mlstats</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">09/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/49-542008.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">49-54</style></pages><abstract><style face="normal" font="default" size="100%">This paper puts forward a framework for investigating Free and Open Source Software (F/OSS) developers activities in both source code and mailing lists repositories. We used data dumps of fourteen pro jects from the FLOSSMetrics (FM) retrieval system. Our intentions are (i) to present a possible methodology, its advantages and disadvantages which can beneﬁt future researchers using some aspects of the FM retrieval system’s data dumps, and (ii) discuss our initial research results on the contributions developers make to both coding and lists activities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">David, P. A.</style></author><author><style face="normal" font="default" size="100%">Rullani, F.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Dynamics of innovation in an &quot;open source&quot; collaboration environment: lurking, laboring, and launching FLOSS projects on SourceForge</style></title><secondary-title><style face="normal" font="default" size="100%">Industrial and Corporate Change</style></secondary-title><short-title><style face="normal" font="default" size="100%">Industrial and Corporate Change</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">SFnetDataset</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual communities</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual organization</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual organizations</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2008</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">17</style></volume><pages><style face="normal" font="default" size="100%">647 - 710</style></pages><abstract><style face="normal" font="default" size="100%">A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March's (1991) framework and applies it to characterize the “innovation system” of a “distributed organization” of interacting agents in a virtual collaboration environment, rather than to innovation within a firm. March (1991) views the process of innovation at the organizational level as the coupling of sub-processes of exploration and exploitation. Correspondingly, the innovation system of the virtual collaboration environment represented by SF.net is an emergent property of two “coupled” processes: one involves the interactions among agents searching the locale for information and knowledge resources to use in designing novel software products (i.e., exploration), and the other involves the mobilization of individuals’ capabilities for application in the software development projects that become established on the platform (i.e., exploitation). The micro-dynamics of this system are studied empirically by constructing transition probability matrices representing the movements of 222,835 SF.net users among seven different activity states, which range from “lurking” (not contributing or contributing to projects without becoming a member) to “laboring” (joining one or more projects as members), and to “launching” (founding one or more projects) within each successive 6-month interval. The estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible the computation of the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project joining and project launching. The latter show the FLOSS innovation process on SF.net to be highly dissipative: a very large proportion of the registered “developers” fail to become even minimally active on the platform. There is nevertheless an active core of mobile project joiners, and a (still smaller) core of project founders who persist in creating new projects. The structure of these groups’ interactions (as displayed within the 3-year period examined) is investigated in detail, and it is shown that it would be sufficient to sustain both the exploration and exploitation phases of the platform's global dynamics.</style></abstract><issue><style face="normal" font="default" size="100%">4</style></issue><notes><style face="normal" font="default" size="100%">&quot;For the purposes of this study, we are able to draw upon micro-level data pertaining to the activities undertaken during the period between the beginning of September 2000 and December 2002 by the entire cohort of 222,835 individuals who had registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001.&quot;
&quot;The statistical analysis in this article is based upon an edited dataset (referred to here as the SFnetDataset) covering the SourceForge cohort of 222,835 individuals who registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001.&quot;
They appear to be using their own dataset which is from 2000-2001 even though this paper is from 2008</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Chris Jensen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Governance in Open Source Software Development Projects: Towards a Model for Network-Centric Edge Organizations</style></title><secondary-title><style face="normal" font="default" size="100%">13th International Command and Control Research and Technology Symposium</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2008</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Bellevue, WA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alspaugh, Thomas</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Emerging Issues in the Acquisition of Open Source Software within the U.S. Department of Defense</style></title><secondary-title><style face="normal" font="default" size="100%">5th Annual Acquisition Research Symposium</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2008</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Naval Postgraduate School, Monterey, CA</style></pub-location><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">230-244</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hill, Emily</style></author><author><style face="normal" font="default" size="100%">Fry, Zachary P.</style></author><author><style face="normal" font="default" size="100%">Boyd, Haley</style></author><author><style face="normal" font="default" size="100%">Sridhara, Giriprasad</style></author><author><style face="normal" font="default" size="100%">Novikova, Yana</style></author><author><style face="normal" font="default" size="100%">Pollock, Lori</style></author><author><style face="normal" font="default" size="100%">Vijay-Shanker, K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">AMAP: automatically mining abbreviation expansions in programs to enhance software maintenance tools</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">automatic abbreviation expansion</style></keyword><keyword><style  face="normal" font="default" size="100%">azureus</style></keyword><keyword><style  face="normal" font="default" size="100%">itext.net</style></keyword><keyword><style  face="normal" font="default" size="100%">liferay</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">natural language</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice.org</style></keyword><keyword><style  face="normal" font="default" size="100%">program comprehension</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">tiger envelopes</style></keyword><keyword><style  face="normal" font="default" size="100%">tools</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370771</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p79-hill.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">79–88</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">When writing software, developers often employ abbreviations in identifier names. In fact, some abbreviations may never occur with the expanded word, or occur more often in the code. However, most existing program comprehension and search tools do little to address the problem of abbreviations, and therefore may miss meaningful pieces of code or relationships between software artifacts. In this paper, we present an automated approach to mining abbreviation expansions from source code to enhance software maintenance tools that utilize natural language information. Our scoped approach uses contextual information at the method, program, and general software level to automatically select the most appropriate expansion for a given abbreviation. We evaluated our approach on a set of 250 potential abbreviations and found that our scoped approach provides a 57% improvement in accuracy over the current state of the art.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Spacco, Jamie</style></author><author><style face="normal" font="default" size="100%">Williams, Chadd C.</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Branching and merging in the repository</style></title><secondary-title><style face="normal" font="default" size="100%">the 2008 international workshopProceedings of the 2008 international workshop on Mining software repositories  - MSR '08</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '08</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">changes</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs2svn</style></keyword><keyword><style  face="normal" font="default" size="100%">diffj</style></keyword><keyword><style  face="normal" font="default" size="100%">revision</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p19-williams.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">19-22</style></pages><isbn><style face="normal" font="default" size="100%">9781605580241</style></isbn><abstract><style face="normal" font="default" size="100%">Two of the most complex operations version control software allows a user to perform are branching and merging. Branching provides the user the ability to create a copy of the source code to allow changes to be stored in version control but outside of the trunk. Merging provides the user the ability to copy changes from a branch to the trunk. Performing a merge can be a tedious operation and one that may be error prone. In this paper, we compare file revisions found on branches with those found on the trunk to determine when a change that is applied to a branch is moved to the trunk. This will allow us to study how developers use merges and to determine if merges are in fact more error prone than other commits.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">González-Barahona, Jesús M.</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Determinism and evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international workshop on Mining software repositories  - MSR '08</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '08</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">changes</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p1-herraiz.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-9</style></pages><isbn><style face="normal" font="default" size="100%">9781605580241</style></isbn><abstract><style face="normal" font="default" size="100%">It has been proposed that software evolution follows a Self-Organized Criticality (SOC) dynamics. This fact is supported by the presence of long range correlations in the time series of the number of changes made to the source code over time. Those long range correlations imply that the current state of the project was determined time ago. In other words, the evolution of the software project is governed by a sort of determinism. But this idea seems to contradict intuition. To explore this apparent contradiction, we have performed an empirical study on a sample of 3,821 libre (free, open source) software projects, finding that their evolution projects is short range correlated. This suggests that the dynamics of software evolution may not be SOC, and therefore that the past of a project does not determine its future except for relatively short periods of time, at least for libre software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chang, Hung-Fu</style></author><author><style face="normal" font="default" size="100%">Audris Mockus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluation of source code copy detection methods on freebsd</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">cloning</style></keyword><keyword><style  face="normal" font="default" size="100%">code copying</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370766</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p61-chang.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">61–66</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Studies have shown that substantial code reuse is common in open source and in commercial projects. However, the precise extent of reuse and its impact on productivity and quality are not well investigated in the open source context. Previously, we have introduced a simple-to-use method that needs only a set of file pathnames to identifies directories that share filenames and partially validated its performance on a set of closed-source projects. To evaluate this method and to improve reuse detection at the file level, we apply it and four additional file copy detection methods that utilize the underlying content of multiple versions of the source code on the FreeBSD project. The evaluation quantified unique advantages of each method and showed that the filename method detected roughly half of all reuse cases. We are still faced with a challenge to scale the content based methods to large repositories containing all versions of open source files.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alonso, Omar</style></author><author><style face="normal" font="default" size="100%">Premkumar T. Devanbu</style></author><author><style face="normal" font="default" size="100%">Gertz, Michael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Expertise identification and visualization from CVS</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">committers</style></keyword><keyword><style  face="normal" font="default" size="100%">components</style></keyword><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise identification</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370780</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p125-alonso.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">125–128</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">As software evolves over time, the identification of expertise becomes an important problem. Component ownership and team awareness of such ownership are signals of solid project. Ownership and ownership awareness are also issues in open-source software (OSS) projects. Indeed, the membership in OSS projects is dynamic with team members arriving and leaving. In large open source projects, specialists who know the system very well are considered experts. How can one identify the experts in a project by mining a particular repository like the source code? Have they gotten help from other people?

We provide an approach using classification of the source code tree as a path to derive the expertise of the committers. Because committers may get help from other people, we also retrieve their contributors. We also provide a visualization that helps to further explore the repository via committers and categories. We present a prototype implementation that describes our research using the Apache HTTP Web server project as a case study.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Premraj, Rahul</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Bettenburg, Nicolas</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Extracting structural information from bug reports</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international workshop on Mining software repositories  - MSR '08</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '08</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">enumerations</style></keyword><keyword><style  face="normal" font="default" size="100%">infozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">natural language</style></keyword><keyword><style  face="normal" font="default" size="100%">patches</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">stack trace</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p27-bettenburg.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">27-30</style></pages><isbn><style face="normal" font="default" size="100%">9781605580241</style></isbn><abstract><style face="normal" font="default" size="100%">In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches. Neglecting such structural elements is a loss of valuable information; structure usually leads to a better performance of machine learning approaches. In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them. We anticipate that infoZilla can be used to leverage data from bug reports at a different granularity level that can facilitate interesting research in the future.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gobeille, Robert</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The FOSSology project</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">abiword</style></keyword><keyword><style  face="normal" font="default" size="100%">fossology</style></keyword><keyword><style  face="normal" font="default" size="100%">license analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">licenses</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370763</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p47-gobeille.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">47–50</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">By its nature, the availability of FOSS has given computer scientists a large body of software and software projects to analyze. By having available source, version control system metadata, and open project communities, much can be learned about a software project, software development and collaborative project development. The goal of the FOSSology project is to create a public, open source software repository, together with tools to facilitate analysis, storage, and sharing of open source software and its metadata. FOSSology does license detection today.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Parnin, Chris</style></author><author><style face="normal" font="default" size="100%">Görg, Carsten</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Improving change descriptions with change contexts</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bytecode analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cecil</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">change pairs</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic diff</style></keyword><keyword><style  face="normal" font="default" size="100%">zedgraph</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370765</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p51-parnin.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">51–60</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Software archives are one of the best sources available to researchers for understanding the software development process. However, much detective work is still necessary in order to unravel the software development story. During this process, researchers must isolate changes and follow their trails over time. In support of this analysis, several research tools have provided different representations for connecting the many changes extracted from software archives. Most of these tools are based on textual analysis of source code and use line-based differencing between software versions. This approach limits the ability to process changes structurally resulting in less concise and comparable items. Adoption of structure-based approaches have been hampered by complex implementations and overly verbose change descriptions. We present a technique for expressing changes that is fine-grained but preserves some structural aspects. The structural information itself may not have changed, but instead provides a context for interpreting the change. This in turn, enables more relevant and concise descriptions in terms of software types and programming activities. We apply our technique to common challenges that researchers face, and then we discuss and compare our results with other techniques.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schuler, David</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining usage expertise from version archives</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">api</style></keyword><keyword><style  face="normal" font="default" size="100%">computer-supported cooperative work</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">recommendation</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">software repository</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370779</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p121-schuler.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">121–124</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">In software development, there is an increasing need to find and connect developers with relevant expertise. Existing expertise recommendation systems are mostly based on variations of the Line 10 Rule: developers who changed a file most often have the most implementation expertise. In this paper, we introduce the concept of usage expertise, which manifests itself whenever developers are using functionality, e.g., by calling API methods. We present preliminary results for the ECLIPSE project that demonstrate that our technique allows to recommend experts for files with no or little history, identify developers with similar expertise, and measure the usage of API methods.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sigmund, Thomas</style></author><author><style face="normal" font="default" size="100%">Gall, Harald C.</style></author><author><style face="normal" font="default" size="100%">Ratzinger, Jacek</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">On the relation of refactorings and software defect prediction</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international workshop on Mining software repositories  - MSR '08</style></secondary-title><short-title><style face="normal" font="default" size="100%">MSR '08</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">defects</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">jboss</style></keyword><keyword><style  face="normal" font="default" size="100%">liferay</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">spring</style></keyword><keyword><style  face="normal" font="default" size="100%">weka</style></keyword><keyword><style  face="normal" font="default" size="100%">xdoclet</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p35-ratzinger.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, New York, USA</style></pub-location><pages><style face="normal" font="default" size="100%">35-38</style></pages><isbn><style face="normal" font="default" size="100%">9781605580241</style></isbn><abstract><style face="normal" font="default" size="100%">This paper analyzes the influence of evolution activities such as refactoring on software defects. In a case study of five open source projects we used attributes of software evolution to predict defects in time periods of six months. We use versioning and issue tracking systems to extract 110 data mining features, which are separated into refactoring and non-refactoring related features. These features are used as input into classification algorithms that create prediction models for software defects. We found out that refactoring related features as well as non-refactoring related features lead to high quality prediction models. Additionally, we discovered that refactorings and defects have an inverse correlation: The number of software defects decreases, if the number of refactorings increased in the preceding time period. As a result, refactoring should be a significant part of both bug fixes and other evolutionary changes to reduce software defects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weißgerber, Peter</style></author><author><style face="normal" font="default" size="100%">Neu, Daniel</style></author><author><style face="normal" font="default" size="100%">Diehl, Stephan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Small patches get in!</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">flac</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">openafs</style></keyword><keyword><style  face="normal" font="default" size="100%">patch acceptance</style></keyword><keyword><style  face="normal" font="default" size="100%">patches</style></keyword><keyword><style  face="normal" font="default" size="100%">revision control</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370767</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p67-weissgerber.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">67–76</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">While there is a considerable amount of research on analyzing the change information stored in software repositories, only few researcher have looked at software changes contained in email archives in form of patches. In this paper we look at the email archives of two open source projects and answer questions like the following: How many emails contain patches? How long does it take for a patch to be accepted? Does the size of the patch influence its chances to be accepted or the duration until it gets accepted? Obviously, the answers to these questions can be helpful for the authors of patches, in particular because some of the answers are surprising.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Thummalapenta, Suresh</style></author><author><style face="normal" font="default" size="100%">Xie, Tao</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SpotWeb: detecting framework hotspots via mining open source repositories on the web</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">code reuse</style></keyword><keyword><style  face="normal" font="default" size="100%">code search engine</style></keyword><keyword><style  face="normal" font="default" size="100%">frameworks</style></keyword><keyword><style  face="normal" font="default" size="100%">hotspots</style></keyword><keyword><style  face="normal" font="default" size="100%">junit</style></keyword><keyword><style  face="normal" font="default" size="100%">log4j</style></keyword><keyword><style  face="normal" font="default" size="100%">repositories</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370775</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p109-thummalapenta.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">109–112</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">The essentials of modern software development (such as low cost and high efficiency) demand software developers to make intensive reuse of existing open source frameworks or libraries (generally referred as frameworks) available on the web. However, developers often face challenges in reusing these frameworks due to several factors such as the complexity and lack of proper documentation. In this paper, we propose a code-search-engine-based approach that tries to detect hotspots in a given framework by mining code examples gathered from open source repositories available on the web; these hotspots are the APIs that are frequently reused.

Hotspots can serve as starting points for developers in understanding and reusing the given framework. We developed a tool, called SpotWeb, for frameworks or libraries written in Java and conducted two case studies with two open source frameworks JUnit and Log4j. We also show that the detected hotspots of Log4j and JUnit are consistent with their respective documentations.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Siy, Harvey</style></author><author><style face="normal" font="default" size="100%">Chundi, Parvathi</style></author><author><style face="normal" font="default" size="100%">Subramaniam, Mahadevan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Summarizing developer work history using time series segmentation: challenge report</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">temporal segmentation</style></keyword><keyword><style  face="normal" font="default" size="100%">time series</style></keyword><keyword><style  face="normal" font="default" size="100%">work history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370784</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">137–140</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Temporal segmentation partitions time series data with the intent of producing more homogeneous segments. It is a technique used to preprocess data so that subsequent time series analysis on individual segments can detect trends that may not be evident when performing time series analysis on the entire dataset.

This technique allows data miners to partition a large dataset without making any assumption of periodicity or any other a priori knowledge of the dataset's features.

We investigate the insights that can be gained from the application of time series segmentation to software version repositories. Software version repositories from large projects contain on the order of hundreds of thousands of timestamped entries or more. It is a continuing challenge to aggregate such data so that noise is reduced and important characteristics are brought out.

In this paper, we present a way to summarize developer work history in terms of the files they have modified over time by segmenting the CVS change data of individual Eclipse developers. We show that the files they modify tends to change significantly over time though most of them tend to work within the same directories.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Pattison, David S.</style></author><author><style face="normal" font="default" size="100%">Bird, Christian A.</style></author><author><style face="normal" font="default" size="100%">Premkumar T. Devanbu</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Talk and work: a preliminary report</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">ant</style></keyword><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370776</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p113-pattison.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">113–116</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Developers in Open Source Software (OSS) projects communicate using mailing lists. By convention, the mailing lists used only for task-related discussions, so they are primarily concerned with the software under development, and software process issues (releases, etc.). We focus on the discussions concerning the software, and study the frequency with which software entities (functions, methods, classes, etc) are mentioned in the mail. We find a strong, striking, cumulative relationship between this mention count in the email, and the number of times these entities are included in changes to the software. When we study the same phenomena over a series of time-intervals, the relationship is much less strong. This suggests some interesting avenues for future research.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hindle, Abram</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Holt, Ric</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What do large commits tell us?: a taxonomical study of large commits</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">boost</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">egroupware</style></keyword><keyword><style  face="normal" font="default" size="100%">enlightenment</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">firebird</style></keyword><keyword><style  face="normal" font="default" size="100%">large commits</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">samba</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">source control system</style></keyword><keyword><style  face="normal" font="default" size="100%">spring</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">05/2008</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370773</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p99-hindle.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">99–108</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Research in the mining of software repositories has frequently ignored commits that include a large number of files (we call these large commits). The main goal of this paper is to understand the rationale behind large commits, and if there is anything we can learn from them. To address this goal we performed a case study that included the manual classification of large commits of nine open source projects. The contributions include a taxonomy of large commits, which are grouped according to their intention. We contrast large commits against small commits and show that large commits are more perfective while small commits are more corrective. These large commits provide us with a window on the development practices of maintenance teams.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Diomidis Spinellis</style></author><author><style face="normal" font="default" size="100%">Gousios, Georgios</style></author><author><style face="normal" font="default" size="100%">Vassilios Karakoidas</style></author><author><style face="normal" font="default" size="100%">Panagiotis Louridas</style></author><author><style face="normal" font="default" size="100%">Paul J. Adams</style></author><author><style face="normal" font="default" size="100%">Samoladas, Ioannis</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating the Quality of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Electronic Notes in Theoretical Computer Science</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">process quality attributes</style></keyword><keyword><style  face="normal" font="default" size="100%">product quality attributes</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">SQO-OSS</style></keyword><keyword><style  face="normal" font="default" size="100%">wiki</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year><pub-dates><date><style  face="normal" font="default" size="100%">03/2009</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">The Reengineering Forum</style></publisher><volume><style face="normal" font="default" size="100%">233</style></volume><pages><style face="normal" font="default" size="100%">5–28</style></pages><abstract><style face="normal" font="default" size="100%">Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. </style></abstract><notes><style face="normal" font="default" size="100%">&quot;the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way&quot;
&quot;The data collection system collects the raw data from open source projects&quot;
Mailing lists are measured in: Number of unique subscribers, Number of messages in user/support list per month, Number of messages in developers list per month, Average thread depth</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author><author><style face="normal" font="default" size="100%">Galia, Fabrice</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The allocation of collaborative efforts in open-source software</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">age</style></keyword><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">division of labor</style></keyword><keyword><style  face="normal" font="default" size="100%">functions</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">gcc</style></keyword><keyword><style  face="normal" font="default" size="100%">ghostscript</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">netbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">openssh</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">revision control</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">Stigmergy</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V8J-4SSG4PN-1/2/88b3824c30a31c18929d8a5ca6d64f62</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">316 - 322</style></pages><abstract><style face="normal" font="default" size="100%">The article investigates the allocation of collaborative efforts among core developers (maintainers) of open-source software by analyzing on-line development traces (logs) for a set of 10 large projects. Specifically, we investigate whether the division of labor within open-source projects is influenced by characteristics of software code. We suggest that the collaboration among maintainers tends to be influenced by different measures of code complexity. We interpret these findings by providing preliminary evidence that the organization of open-source software development would self-adapt to characteristics of the code base, in a 'stigmergic' manner.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we have selected a set of 10 large open-source projects&quot;
apache, cvs, gaim, gcc, ghostscript, mozilla, netbsd, openssh, postgresql, python
&quot;Our data were extracted from logs of development activity generated by software version control systems. For each project in the selection, we extracted CVS development logs&quot;
&quot;We notably computed for each file in the sample, and for each month in its history, the number of distinct maintainers that had committed a change during that month, and the number of commits, the blocks of code addition, each file had received during that month.&quot;
&quot;other variables used in the regressions are proxies for the size, age, and granularity of files; the size of a file is represented as its number of lines of code (LOCs), its age by its creation date (Youth), and its granularity by the number of functions it contains.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wermelinger, Michel</style></author><author><style face="normal" font="default" size="100%">Yu, Yijun</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analyzing the evolution of eclipse plugins</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">architectural evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">releases</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370783</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">133–136</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Eclipse is a good example of a modern component-based complex system that is designed for long-term evolution, due to its architecture of reusable and extensible components. This paper presents our preliminary results about the evolution of Eclipse's architecture, based on a lightweight and scalable analysis of the metadata in Eclipse's sources. We find that the development of Eclipse follows a systematic process: most architectural changes take place in milestones, and maintenance releases only make exceptional changes to component dependencies. We also found a stable architectural core that remains since the first release.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Barbara Scozzi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Bug Fixing Practices within Free/Libre Open Source Software Development Teams</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of Database Management</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">activity</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracker</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">downloads</style></keyword><keyword><style  face="normal" font="default" size="100%">dynapi</style></keyword><keyword><style  face="normal" font="default" size="100%">effectiveness</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">kicq</style></keyword><keyword><style  face="normal" font="default" size="100%">phpmyadmin</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">status</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CrowstonScozziJDBM2008.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">19</style></volume><pages><style face="normal" font="default" size="100%">1–30</style></pages><abstract><style face="normal" font="default" size="100%">Free/libre open source software (FLOSS, e.g., Linux or Apache) 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, yet some how profit from the advantages and evade the challenges of distributed software development. In this article 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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Projects to be studied were selected from those hosted on SourceForge, (http://sourceforge.net/)&quot;
&quot;we chose projects for which data we need for our analysis are publicly available, meaning a large number of bug reports&quot;
&quot;we chose teams with more than 8 developers&quot;
&quot;Only 140 projects of SourceForge met the first two requirements in 2002 when we drew our sample&quot;
kicq, gaim, phpmyadmin, dynapi
&quot;First, we obtained data indica- tive of the effectiveness of each project, such as its level of activity, number of downloads and development status&quot;
&quot;we elected to use objective data about the bug- fixing process. Hence, the main source of data about the bug-fixing process was obtained from the archives of the bug tracking system, which is the tool used to support the bug-fixing process&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Singh, V</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The confusion of crowds: non-dyadic help interactions</style></title><secondary-title><style face="normal" font="default" size="100%">CSCW '08: Proceedings of the 2008 ACM conference on Computer supported cooperative work</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">help-giving</style></keyword><keyword><style  face="normal" font="default" size="100%">technical help</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">699–702</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-007-4</style></isbn><abstract><style face="normal" font="default" size="100%">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. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nicolas Jullien</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Developing 'FLOSS' - A Market Driven Investment: First Evidence from a Francophone Companies Survey</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/NJullien_firms_strategies_regarding_FLOSS_octobre.pdf</style></url><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Jullien_4-2008.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Over the last few years, FLOSS (&quot;&quot;Free Libre Open Source Software&quot;&quot;) has become a commercially viable reality of the first order. It is viewed as an extreme case of open innovation (Chesbrough, 2003), and thus of a laboratory for analysing innovation production in Internet based/knowledge based industries.

It the FLOSS field an increasing number of companies are getting involved in the communities of development (Lakhani &amp; Wolf 2005). Scholars (see, for instance Dahlander &amp; Wallin 2006) has analysed this as a way to control a complementary asset, without owning it (as defined by Teece 1986, Teece &amp; al. 1997). In this article, we defend the idea that involvement can be of different intensity, from complementary to specific asset, and that this intensity depends of the market of the firm.

To do so, we surveyed francophone companies (France, Belgium, Switzerland) affirming a utilization of FLOSS in their commercial activity. Based on roughly 500 companies concerned, we obtained 141 usable responses and, via an ascendant hierarchical clustering (AHC) we statistically verified a link between FLOSS commercial strategies and degree of involvement into communities. We propose a typology of commercial strategies explaining this differences in involvement.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paola Giuri</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author><author><style face="normal" font="default" size="100%">Salvatore Torrisi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Explaining leadership in virtual teams: The case of open source software</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">Human capital</style></keyword><keyword><style  face="normal" font="default" size="100%">leadership</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V8J-4SRW10C-1/2/5ce36096ba3947338962268b54a5a7a9</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">305 - 315</style></pages><abstract><style face="normal" font="default" size="100%">This paper contributes to the open source software (OSS) literature by investigating the likelihood that a participant becomes a project leader. Project leaders are key actors in a virtual community and are crucial to the success of the OSS model. Knowledge of the forces that lead to the emergence of project managers among the multitude of participants is still limited. We aim to fill this gap in the literature by analyzing the association between the roles played by an individual who is registered with a project, and a set of individual-level and project-level characteristics. In line with the theory of occupational choice elaborated by (Lazear, E.P., 2002. Entrepreneurship. NBER Working Paper No. 9109, Cambridge, Mass; Lazear, E.P., 2004. Balanced skills and entrepreneurship, American Economic Review 94, pp. 208-211), we find that OSS project leaders possess diversified skill sets which are needed to select the inputs provided by various participants, motivate contributors, and coordinate their efforts. Specialists, like pure developers, are endowed with more focused skill sets. Moreover, we find that the degree of modularity of the development process is positively associated with the presence of project leaders. That result is consistent with the modern theory of modular production (Baldwin, C.Y., Clark, K.B., 1997. Managing in an age of modularity. Harvard Business Review September-October. pp. 84-93; Mateos-Garcia, J., Steinmueller, W.E., 2003. The Open Source Way of Working: A New Paradigm for the Division of Labour in Software Development? SPRU - Science and Technology Policy Studies. Open Source Movement Research INK Working Paper, No. 1; Aoki, M., 2004. An organizational architecture of T-form: Silicon Valley clustering and its institutional coherence. Industrial and Corporate Change 13, pp. 967-981).</style></abstract><notes><style face="normal" font="default" size="100%">Empirical Issues in Open Source Software</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hata, Hideaki</style></author><author><style face="normal" font="default" size="100%">Mizuno, Osamu</style></author><author><style face="normal" font="default" size="100%">Kikuno, Tohru</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An extension of fault-prone filtering using precise training and a dynamic threshold</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">fault-prone modules</style></keyword><keyword><style  face="normal" font="default" size="100%">spam filter</style></keyword><keyword><style  face="normal" font="default" size="100%">text mining</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370772</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p89-hata.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">89–98</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Fault-prone module detection in source code is important for assurance of software quality. Most previous fault-prone detection approaches have been based on software metrics. Such approaches, however, have difficulties in collecting the metrics and in constructing mathematical models based on the metrics. To mitigate such difficulties, we have proposed a novel approach for detecting fault-prone modules using a spam-filtering technique, named Fault-Prone Filtering. In our approach, fault-prone modules are detected in such a way that the source code modules are considered as text files and are applied to the spam filter directly. In practice, we use the training only errors procedure and apply this procedure to fault-prone. Since no pre-training is required, this procedure can be applied to an actual development field immediately. This paper describes an extension of the training only errors procedures. We introduce a precise unit of training, &quot;modified lines of code,&quot; instead of methods. In addition, we introduce the dynamic threshold for classification. The result of the experiment shows that our extension leads to twice the precision with about the same recall, and improves 15% on the best F1 measurement.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Roberto Andradas-Izquierdo</style></author><author><style face="normal" font="default" size="100%">Rishab Aiyer Ghosh</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Geographic origin of libre software developers</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email address</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">geography</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">timezone</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V8J-4T3DCPK-1/2/3981dfbc523eae1d1ce65fb1f0c0edb7</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">356 - 363</style></pages><abstract><style face="normal" font="default" size="100%">This paper examines the claim that libre (free, open source) software involves global development. The anecdotal evidence is that developers usually work in teams including individuals residing in many different geographical areas, time zones and even continents and that, as a whole, the libre software community is also diverse in terms of national origin. However, its exact composition is difficult to capture, since there are few records of the geographical location of developers. Past studies have been based on surveying a limited (and sometimes biased) sample and extrapolating that sample to the global distribution of developers. In this paper we present an alternate approach in which databases are analyzed to create traces of information from which the geographical origin of developers can be inferred. Applying this technique to the SourceForge users database and the mailing lists archives from several large projects, we have estimated the geographical origin of more than one million individuals who are closely related to the libre software development process. The paper concludes that the result is a good proxy for the actual distribution of libre software developers working on global projects.</style></abstract><notes><style face="normal" font="default" size="100%">Empirical Issues in Open Source Software</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author><author><style face="normal" font="default" size="100%">Floyd, I.R.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Infrastructures From the Bottom-Up and the Top-Down: Can They Meet in the Middle?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings PDC 2008</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><pages><style face="normal" font="default" size="100%">238-241</style></pages><abstract><style face="normal" font="default" size="100%">Based on a study of participatory design in the development of cyberinfrastructure involving the rapid composition of open source software and web services, we consider cases where researchers create their own ad hoc infrastructures out of available software. We compare &quot;top- down&quot; and &quot;bottom-up&quot; cyberinfrastructure development and speculate on whether the two approaches can be productively combined.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author><author><style face="normal" font="default" size="100%">Floyd, I.R.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Infrastructures From the Bottom-Up and the Top-Down: Can They Meet in the Middle?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings Participatory Design Conference 2008</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://hdl.handle.net/2142/9526</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">238-241.</style></pages><abstract><style face="normal" font="default" size="100%">Based on a study of participatory design in the development of cyberinfrastructure involving the rapid composition of open source software and web services, we consider cases where researchers create their own ad hoc infrastructures out of available software. We compare &quot;top- down&quot; and &quot;bottom-up&quot; cyberinfrastructure development and speculate on whether the two approaches can be productively combined.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zhang, Hongyu</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An initial study of the growth of eclipse defects</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">defect growth model</style></keyword><keyword><style  face="normal" font="default" size="100%">defect prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">polynomial regression</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370785</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">141–144</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">We analyze the Eclipse defect data from June 2004 to November 2007, and find that the growth of the number of defects can be well modeled by polynomial functions. Furthermore, we can predict the number of future Eclipse defects based on the nature of defect growth.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">von Engelhardt, Sebastian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Intellectual Property Rights and Ex-Post Transaction Costs: the Case of Open and Closed Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/wp_2008_047.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The economic characteristics of software and transaction costs explain, why closed source and open source software co-exist. It is about the efficient use of a non- and anti-scarce resource. But because of ex-post transaction costs that lead to information asymmetries, some property rights regarding the resource &quot;&quot;source code&quot;&quot; are not exclusively separable. Thus, the first best allocation of property rights, that would yield an optimal usage of a source code, is not realizable. Or, that is to say, a first best realization of contracts is not feasible.

Hence, open and closed source software are two second best arrangements, both with specific assets and drawbacks. The principle of closed source benefits from direct (monetary) incentives and control, but has limits in its scope (size) because of transaction costs. Open source, on the one hand, benefits from its openness that creates spillovers and enables to incorporate human capital that is not acquirable for closed source firms. On the other hand, there are costs of openness, such as coordination costs (consensus finding, etc.) the danger of free riding or under provision, or forking.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stephanie Freeman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Material and Social Dynamics of Motivation: Contributions to Open Source Language Technology Development</style></title><secondary-title><style face="normal" font="default" size="100%">Science Studies</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice</style></keyword><keyword><style  face="normal" font="default" size="100%">openoffice.org</style></keyword><keyword><style  face="normal" font="default" size="100%">secondary data</style></keyword><keyword><style  face="normal" font="default" size="100%">Volunteers</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Freeman.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Volunteer motivation has been a central theme in Free/Libre/Open Source Software (FLOSS) literature. This research has been largely dominated by economists who rely in their surveys on the distinction between intrinsic and extrinsic motivations and the &quot;hacker ethic&quot; for profit juxtaposition. The paper argues that survey-based analytical frameworks and research designs have led to a focus on some motivational attributions at the expense of others. It then presents a case study that explores dynamic, non individualistic and content-sensitive aspects of motivations. The approach is based on socio-cultural psychology and the author's observations of a hybrid firm-community FLOSS project, OpenOffice.org. Instead of separating intrinsic motivations from extrinsic ones, it is argued that complex and changing patterns of motivations are tied to changing objects and personal histories prior to and during participation. The boundary between work and hobby in an individual's participation path is blurred and shifting.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;I conducted a two-phased qualitative analysis on multiple data (thematic phone-inter- views, notes from OpenOffice.org conference 2004 meetings, historical documents, mailing list discussions, homepages, Google, blogs, real-time video and audio presentations from OpenOffice.org conference 2005).&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Holmes, Reid</style></author><author><style face="normal" font="default" size="100%">Walker, Robert J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A newbie's guide to eclipse APIs</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">API popularity</style></keyword><keyword><style  face="normal" font="default" size="100%">documentation</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">module</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">PopCon</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370787</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">149–152</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Eclipse has evolved from a fledgling Java IDE into a mature software ecosystem. One of the greatest benefits Eclipse provides developers is flexibility; however, this is not without cost. New Eclipse developers often find the framework to be large and confusing. Determining which parts of the framework they should be using can be a difficult task as Eclipse documentation tends to be either very high-level, focusing on the design of the framework, or low-level, focusing on specific APIs. We have developed a tool called PopCon that provides a bridge between high-level design documentation and low-level API documentation by statically analyzing a framework and several of its clients and providing a ranked list of the relative popularity of its APIs. We have applied PopCon to the Eclipse framework for this challenge to help newbie Eclipse developers identify some of the most relevant APIs for their tasks.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rahul Kala</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Open and Closed Styles of Talent Acquisition and Management:  Which takes an edge where</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/paper.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The phenomenal success of Free/Open Source Software during the recent years has led researchers in all related fields to re-think and re-evaluate the studies and concepts, especially those which the open source violates. Talent management and talent acquisition is no exception to this. The sudden rise in open source projects and their success is a cause of motivation for all of us to evaluate their philosophy and implement the same. Proper talent management and acquisition of talent can play a key role in strengthening the industry. Traditional closed management with their classic way of functioning may still look at the open source model as a big mystery. Open source has violated many of the theories of Software Engineering like limited team size, decentralized project management, etc. The concepts of self-motivated individuals, adaptive division of labor, informal or indirect leadership, etc. are the contributions of the open source to the world.

In this paper we discuss these concepts and state their differences with the way of working of closed talent management. Even though open source has various benefits in working, but requirement of a good coordination process, redundancy of development, versioning problems, etc. pose a limitation. We present an analogy of the talent management in the two concepts with that of the natural ecosystem. Talent in open source works in a manner similar to the ant colonies. Here the process is more community oriented and there is no single dictator power. The proprietary, on the other hand, works on talent as the lions ruling the den. There is a hierarchy and that needs to be respected. Only the leader has the right to make final decision, and that is binding. We also take a look into the present conditions of meltdown and show how the open source way is better suited for this scenario. Even though the present firms may be seeing a setback at this time of recession, the impact on firms with an open source way of working is much lighter or none at all. We also discuss the interactions between the two styles of talent management and present a model that can be adopted by the proprietary companies to benefit from open model. Our arguments of the paper not only deal with software, but also on content that comes under the domain of Creative Commons. We have taken the examples of Wikipedia, Sourceforge.net, Linux etc. for the various issues we discuss.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin J. Weller</style></author><author><style face="normal" font="default" size="100%">Andreas Meiszner</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Athanasis Karoulis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Report on the effectiveness of a FLOSS-like learning community in formal educational settings</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FLOSSCOM_Wp4_PHASE2_REPORT_d1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This report examines some of the pedagogic principles embodied in Free / Libre Open Source Software (FLOSS) communities and briefly looks at case studies of FLOSS-like approaches in education. It analyzes and evaluates the differences between Free / Libre Open Source Software (FLOSS) communities as informal learning environments and on the other side formal educational settings. The report also point out ways on transferring those FLOSS principles to formal educational settings and looks at existing examples of eLearning delivery and examines why these do not provide the types of constructivist learning environments as observed in FLOSS communities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a simplification of the bug report form in eclipse</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug report</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">severity</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370786</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">145–148</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">We believe that the bug report form of Eclipse contains too many fields, and that for some fields, there are too many options. In this MSR challenge report, we focus in the case of the severity field. That field contains seven different levels of severity. Some of them seem very similar, and it is hard to distinguish among them. Users assign severity, and developers give priority to the reports depending on their severity. However, if users can not distinguish well among the various severity options, they will probably assign different priorities to bugs that require the same priority. We study the mean time to close bugs reported in Eclipse, and how the severity assigned by users affects this time. The results shows that classifying by time to close, there are less clusters of bugs than levels of severity. We therefore conclude that there is a need to make a simpler bug report form.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bert M. Sadowski</style></author><author><style face="normal" font="default" size="100%">Gaby Sadowski-Rasters</style></author><author><style face="normal" font="default" size="100%">Geert Duysters</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Transition of governance in a mature open software source community: Evidence from the Debian case</style></title><secondary-title><style face="normal" font="default" size="100%">Information Economics and Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">governance</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6V8J-4SHF4BS-1/2/579ba679ee43d7c77302f3595334dd24</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">323 - 332</style></pages><abstract><style face="normal" font="default" size="100%">As open source software (OSS) communities mature, they have to introduce a variety of governance mechanisms to manage the participation of their members and to coordinate the launch of new releases. The Debian community introduced new mechanisms of informal administrative control based on a constitution, elected leaders, and used interactive communication channels. We show that these control mechanisms were introduced as a response to emerging innovative opportunities due to the usage of source packages and to the need to build a responsive organization within the Debian OSS community.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We primarily used internal documents related to the contents and context of different Debian projects.&quot;
&quot;Furthermore, we attended several Debian conferences and were ‘‘lurking around” on the Debian mailing lists, websites, IRC channels, etc.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sudakrishnan, Sangeetha</style></author><author><style face="normal" font="default" size="100%">Madhavan, Janaki</style></author><author><style face="normal" font="default" size="100%">Whitehead,Jr., E. James</style></author><author><style face="normal" font="default" size="100%">Renau, Jose</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding bug fix patterns in verilog</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2008 international working conference on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '08</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">error classification</style></keyword><keyword><style  face="normal" font="default" size="100%">hdl</style></keyword><keyword><style  face="normal" font="default" size="100%">verilog</style></keyword><keyword><style  face="normal" font="default" size="100%">VHDL</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1370750.1370761</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/p39-sudakrishnan.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">39–42</style></pages><isbn><style face="normal" font="default" size="100%">978-1-60558-024-1</style></isbn><abstract><style face="normal" font="default" size="100%">Today, many electronic systems are developed using a hardware description language, a kind of software that can be converted into integrated circuits or programmable logic devices. Like traditional software projects, hardware projects have bugs, and significant developer time is spent fixing them. A useful first step toward reducing bugs in hardware is developing an understanding of the frequency of different types of errors. Once the most common types are known, it is then possible to focus attention on eliminating them. As most hardware projects use software configuration management repositories, these can be mined for the textual bug fix changes. In this project, we analyze the bug fix history of four hardware projects written in Verilog and manually define 25 bug fix patterns. The frequency of each bug type is then computed for all projects. We find that 29 -- 55% of the bug fix pattern instances in Verilog involve assignment statements, while 18 -- 25% are related to if statements.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Lefteris Angelis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding knowledge sharing activities in free/open source software projects: An empirical study</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of Systems and Software</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/JSS_0.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">81</style></volume><pages><style face="normal" font="default" size="100%">431-446</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free/Open Source Software (F/OSS) projects are people-oriented and knowledge intensive software development environments. Many researchers focused on mailing lists to study coding activities of software developers. How expert software developers interact with each other and with non-developers in the use of community products have received little attention. This paper discusses the altruistic sharing of knowledge between knowledge providers and knowledge seekers in the Developer and User mailing lists of the Debian project. We analyze the posting and replying activities of the participants by counting the number of email messages they posted to the lists and the number of replies they made to questions others posted. We found out that participants interact and share their knowledge a lot, their positing activity is fairly highly correlated with their replying activity, the characteristics of posting and replying activities are different for different kinds of lists, and the knowledge sharing activity of self-organizing Free/Open Source communities could best be explained in terms of what we called &quot;Fractal Cubic Distribution&quot; rather than the power-law distribution mostly reported in the literature. The paper also proposes what could be researched in knowledge sharing activities in F/OSS projects mailing list and for what purpose. The research findings add to ' our understanding of knowledge sharing activities in F/OSS projects. (C) 2007 Elsevier Inc. All rights reserved.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000254709200010</style></accession-num><notes><style face="normal" font="default" size="100%">&quot;Our study utilized data from the Debian project lists archives.... The Debian project hosts over 100 lists on all aspects related to the project. From the Debian lists archives (Debian Mailing Lists) we selected two high volume mailing lists. The following lists are analyzed in our study:
• Debian-user. This list is specifically dedicated to help and discussion among users of Debian who speak English. • Debian-devel. This list is specifically dedicated to discus-
sion about technical development topics.
Our data collection period for both lists was from January 2000 to December 2005. We obtained archived mbox files of the two lists. Each file is a single text file containing one month of archived email messages. Every email message has a unique message-id, together with other identification fields defined by the Internet Message Format (RFC) 2822 (Internet Message Format, 2001).&quot;</style></notes><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">computational?</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Janet Hope</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Biobazaar: The Open Source Revolution and Biotechnology</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">Harvard University Press</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">book</style></custom3><label><style face="normal" font="default" size="100%">hope2008</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Watson, R. T.</style></author><author><style face="normal" font="default" size="100%">Boudreau, M. C.</style></author><author><style face="normal" font="default" size="100%">York, P. T.</style></author><author><style face="normal" font="default" size="100%">Greiner, M. E.</style></author><author><style face="normal" font="default" size="100%">Wynn, D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The business of open source</style></title><secondary-title><style face="normal" font="default" size="100%">Communications of the ACM</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">51</style></volume><pages><style face="normal" font="default" size="100%">41-46</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><accession-num><style face="normal" font="default" size="100%">WOS:000254780700009</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Drenner, S.</style></author><author><style face="normal" font="default" size="100%">Sen, S.</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Crafting the initial user experience to achieve community goals</style></title><secondary-title><style face="normal" font="default" size="100%">ACM Conference on recommender Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Lausanne, Switzerland</style></pub-location><isbn><style face="normal" font="default" size="100%">978-1-60558-093-7</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conley, Caryn A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design for quality: The case of Open Source Software Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">New York University</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY</style></pub-location><volume><style face="normal" font="default" size="100%">PhD</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><work-type><style face="normal" font="default" size="100%">doctoral dissertation</style></work-type><custom3><style face="normal" font="default" size="100%">phdthesis</style></custom3><label><style face="normal" font="default" size="100%">conley2008design-for-qual</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Kraemer, K.L.</style></author><author><style face="normal" font="default" size="100%">Elliott, M.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Emerging Patterns of Intersection and Segmentation when Computerization Movements Interact</style></title><secondary-title><style face="normal" font="default" size="100%">Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%"> Information Today, Inc.</style></publisher><pages><style face="normal" font="default" size="100%">381-404</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Coleman, E.G.</style></author><author><style face="normal" font="default" size="100%">Golub, A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Hacker practice: Moral genres and the cultural articulation of liberalism</style></title><secondary-title><style face="normal" font="default" size="100%">Anthropological Theory</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">8</style></volume><pages><style face="normal" font="default" size="100%">255</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">article</style></custom3><label><style face="normal" font="default" size="100%">coleman2008</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Quang Vu Dang</style></author><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Xuan Sang Dao</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Improving community awareness in software forges by semantical aggregation of tools feeds</style></title><secondary-title><style face="normal" font="default" size="100%">3nd International Workshop on Public Data about Software Development (WoPDaSD 2008), Milano, Italy, September 2008</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">community of practice</style></keyword><keyword><style  face="normal" font="default" size="100%">DOAF.</style></keyword><keyword><style  face="normal" font="default" size="100%">FOAF</style></keyword><keyword><style  face="normal" font="default" size="100%">free and open source software development</style></keyword><keyword><style  face="normal" font="default" size="100%">public data</style></keyword><keyword><style  face="normal" font="default" size="100%">RDF</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic Web</style></keyword><keyword><style  face="normal" font="default" size="100%">social filtering</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Paper4.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">It is rather difficult to monitor or visualize what can be the contribution of a member in a project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that use Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, and FOAF. Resulting data can then be processed, republished or displayed to project members. We implemented this approach in a supervision module that has been integrated into the PicoForge platform. This module is able do draw a live graph of the social community out of the different sources of data, and in turn export semantic feeds for other uses.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bellifemine, F.</style></author><author><style face="normal" font="default" size="100%">Caire, G.</style></author><author><style face="normal" font="default" size="100%">Poggi, A.</style></author><author><style face="normal" font="default" size="100%">Rimassa, G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">JADE: A software framework for developing multi-agent applications. Lessons learned</style></title><secondary-title><style face="normal" font="default" size="100%">Information and Software Technology</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><volume><style face="normal" font="default" size="100%">50</style></volume><pages><style face="normal" font="default" size="100%">10-21</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Since a number of years agent technology is considered one of the most innovative technologies for the development of distributed software systems. While not yet a mainstream approach in software engineering at large, a lot of work on agent technology has been done, many research results and applications have been presented, and some software products exists which have moved from the research community to the industrial community. One of these is JADE, a software framework that facilitates development of interoperable intelligent multi-agent systems and that is distributed under an Open Source License. JADE is a very mature product, used by a heterogeneous community of users both in research activities and in industrial applications. This paper presents JADE and its technological components together with a discussion of the possible reasons for its success and lessons learned from the somewhat detached perspective possible nine years after its inception. (c) 2007 Elsevier B.V. All rights reserved.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000252196700004</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Elliott, M.</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mobilization of Software Developers: The Free Software Movement</style></title><secondary-title><style face="normal" font="default" size="100%">(revised version in) Information, Technology and People</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">4-33</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><issue><style face="normal" font="default" size="100%">1</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dedrick, Jason</style></author><author><style face="normal" font="default" size="100%">Joel West</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Kraemer, Kenneth L.</style></author><author><style face="normal" font="default" size="100%">Elliott, Margaret</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Movement Ideology vs. User Pragmatism in the Organizational Adoption of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">Information Today</style></publisher><pub-location><style face="normal" font="default" size="100%">Medford, NJ</style></pub-location><pages><style face="normal" font="default" size="100%">427-452</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sentas, P.</style></author><author><style face="normal" font="default" size="100%">Lefteris Angelis</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A statistical framework for analyzing the duration of software projects</style></title><secondary-title><style face="normal" font="default" size="100%">Empirical Software Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">13</style></volume><pages><style face="normal" font="default" size="100%">147-184</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The duration of a software project is a very important feature, closely related to its cost. Various methods and models have been proposed in order to predict not only the cost of a software project but also its duration. Since duration is essentially the random length of a time interval from a starting to a terminating event, in this paper we present a framework of statistical tools, appropriate for studying and modeling the distribution of the duration. The idea for our approach comes from the parallelism of duration to the life of an entity which is frequently studied in biostatistics by a certain statistical methodology known as survival analysis. This type of analysis offers great flexibility in modeling the duration and in computing various statistics useful for inference and estimation. As in any other statistical methodology, the approach is based on datasets of measurements on projects. However, one of the most important advantages is that we can use in our data information not only from completed projects, but also from ongoing projects. In this paper we present the general principles of the methodology for a comprehensive duration analysis and we also illustrate it with applications to known data sets. The analysis showed that duration is affected by various factors such as customer participation, use of tools, software logical complexity, user requirements volatility and staff tool skills.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000254743000003</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes><custom1><style face="normal" font="default" size="100%">software engineering</style></custom1><custom2><style face="normal" font="default" size="100%">statistical modeling</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gasser, Les</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Russo, B.</style></author><author><style face="normal" font="default" size="100%">Damiani, E.</style></author><author><style face="normal" font="default" size="100%">Hissan, S.</style></author><author><style face="normal" font="default" size="100%">Lundell, B.</style></author><author><style face="normal" font="default" size="100%">Succi, G.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">Open Source Development, Communities and Quality</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pub-location><style face="normal" font="default" size="100%">Boston</style></pub-location><volume><style face="normal" font="default" size="100%">275</style></volume><pages><style face="normal" font="default" size="100%">143-158</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christoper Kelty</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Two Bits: The Cultural Significance of Free Software and the Internet</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><publisher><style face="normal" font="default" size="100%">Duke University Press</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">book</style></custom3><label><style face="normal" font="default" size="100%">kelty2008tbc</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oliver Alexy</style></author><author><style face="normal" font="default" size="100%">Martin Leitner</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Norms, Rewards, and their Effect on the Motivation of Open Source Software Developers</style></title><secondary-title><style face="normal" font="default" size="100%">working paper</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Alexy_Leitner_-_Norms_Rewards_and_Their_Effect_on_the_Motivation_of_OSS_Developers.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this study, we conduct a scenario experiment testing the effect of monetary rewards on intrinsic motivation of open source software (OSS) developers. While we observe no difference in intrinsic motivation between the payment and no payment scenario, total motivation increases when a monetary reward is offered. We find that self-reported interest increases in the payment scenario when there is a norm for payment, whereas it decreases when there is a norm for no payment. We conclude that, under certain preconditions, monetary rewards may well be used in OSS development.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mahmoud Refaat Nasr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The use of open source GIS software and its impact on organizations</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OS_GIS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI???s ArcIMS, Intergraph???s GeoMedia WebMap, and MapInfo???s MapXtreme. The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author><author><style face="normal" font="default" size="100%">Enrico Zini</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/libre open source software implementation in schools: Evidence from the field and implications for the future</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Lin&amp;Zini.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software to support the needs of local users better. This also allows users to participate more proactively in the development and implementation process of a FLOSS-based system. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization - including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jeremy Malcolm</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Development as a Model for Internet Governance</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Internet governance and open source software development alike are most effectively achieved through a balance of decentralisation and control. For Internet governance, this is found in governance by network, in which governmental and private stakeholders, and the hierarchical and decentralised mechanisms of governance they respectively favour, are brought together. However if the stakeholders' power is unequal, so will be the balance of the network. The case of open source software development provides the key to ensuring that stakeholders are not oppressed in a network unbalanced by hierarchical power. This relies on the phenomenon of exit-based empowerment that flows from the open source software licence. However, it can be extended to the design of governance networks given certain idealising assumptions, and even when these do not hold, useful lessons for the future reform of Internet governance arrangements remain.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Siefkes</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From Exchange to Contributions: Generalizing Peer Production into the Physical World</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/peer-economy.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Peer production is a new mode of production that has emerged in the areas of software and content production during the last decades – a mode of production based on sharing and cooperation. We discuss whether and how peer production can be extended into the realm of physical production and whether a society is possible in which peer production is the primary mode of production. We investigate which problems need to be solved for the generalization of peer production and how they can be addressed in the context of individual peer projects as well as society as a whole. Our findings indicate there is no inherent reason for peer production to remain limited to the sphere of information. We analyze how we may expect a society whose economy is based on free cooperation in a multitude of peer projects to work and how such a society compares with societies based on market production or planned production. We show that the differences are striking, and that such a peer economy would grant people an unprecedented amount of control over their own lives, while avoiding the unpleasant effects of other modes of production.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Linus Dahlander</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Penguin in a new suit: A tale of how de novo entrants emerged to harness free and open source communities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dahlander2007.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">A growing body of literature has explored the motivations for individuals to take part in free and open source software (FOSS), yet how firms participate is largely an unattended research area. Building on information from an extensive dataset of secondary sources and 30 in-depth interviews, I show that de novo entrants have emerged in conjunction with a changing institutional infrastructure and a more pragmatic attitude toward firms that focus on technological benefits rather than ideology. To understand how these firms try to harness the work of these communities, I use the empirical data to derive a 2*2 matrix of different approaches. The X axis reflects whether or not the firms initiated a new community or relied on communities founded by peers, whereas the Y axis represents the degree of participation of the firm in the community. This taxonomy illustrates how de novo entrant are initiating new forms of communities or joining communities established by peers. This suggests that while many of the central pillars of FOSS remains, de novo entrants have emerged to find new ways of making business resulting in various implications for firm strategies and knowledge disclosure. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oliver Alexy</style></author><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Putting a Value on Openness: The Effect of Product Source Code Releases on the Market Value of Firms</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Alexy_-_Putting_a_Value_on_Openness.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study examines the effect of releasing the source code of commercial software products as open source software on the market value of firms. Using a sample of 30 software companies in the time span from 1 January 1999 to 30 April 2007, I find that market valuation is influenced by investor sentiment???abnormal returns take a curvilinear shape over time???and the business model firms choose for their OSS efforts???non-existence of an explicit revenue model is punished by the capital market. From my findings, I deduce several implications for IT-related event studies and research on open innovation processes.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yi Wang</style></author><author><style face="normal" font="default" size="100%">Defeng Guo</style></author><author><style face="normal" font="default" size="100%">Shi, Huihui</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Measuring the evolution of open source software systems with their communities</style></title><secondary-title><style face="normal" font="default" size="100%">SIGSOFT Softw. Eng. Notes</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">launchpad</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">open source community</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">Ubuntu</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1317471.1317479</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><volume><style face="normal" font="default" size="100%">32</style></volume><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) has become the subject of much commercial and academic interest in last few years. As traditional software, OSS also evolves to fulfill the need of stakeholders. Therefore, providing quantitative metrics for OSS evolution has also become an urgent issue. However, most existing studies of software evolution have been performed on systems developed within a single company using traditional management techniques. These metrics models are inadequate to measure OSS evolution. In this paper, we describe a preliminary evolution metrics set for evaluating OSS. The most significant novelty of this model is that it takes specific properties of Open Source Community (OSC) into consideration. In another word, we measure the evolution of OSS and OSC together. We also provide a lightweight case study on Ubuntu project using this metrics set. We find out that the Open Source Community and its members also play essential role in OSS evolution. We expect this metrics model can bring better understandings and explanations of phenomena in open source development and evolution.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;1. M1: The number of modules in software system at a series of specific moment.
2. CD: The number of developers (code contributors) at a series of specific moment.
3. MC: The correlation of M1 and CD.&quot;
&quot;We get the information of Modules from the Launchpad[1] which is a distributed collaborative infrastructure for Ubuntu and other open source software development. Ubuntu mainly grows though a manner of adding new packages. So, we treat packages as the modules we mention before. In Ubuntu community, some members are in charge of auditing the packages and add them to Ubuntu, here developers are refers them.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Elliott, M.</style></author><author><style face="normal" font="default" size="100%">Ackerman, Mark S.</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Knowledge Work Artifacts: Kernel Cousins for Free/Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">ACM Conference on Support of Group Work (GROUP07)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Nov 4-7</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Sanibel Island, FL</style></pub-location><pages><style face="normal" font="default" size="100%">177-186</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Evangelia Berdou</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Managing the Bazaar: Commercialization and peripheral participation in mature, community-led Free/Open source software projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Nov</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/PhD_Berdou.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The thesis investigates two fundamental dynamics of participation and collaboration in mature, community-led Free/Open Source (F/OS) software projects - commercialization and peripheral participation. The two primary case studies of the research are the GNOME and KDE communities.The thesis contributes insights into how the gift economy is embedded in the exchange economy and the role of peripheral contributors. The analysis indicates that community-integrated paid developers have a key role in project development, maintaining the infrastructure aspects of the code base. The analysis suggests that programming and non-programming contributors are distinct in their make-up, priorities and rhythms of participation, and that learning plays an important role in controlling access. The results show that volunteers are important drivers of peripheral activities, such as translation and documentation. The term &quot;autonomous peripherality&quot;&quot; is used to capture the unique characteristics of these activities. These findings support the argument that centrality and peripherality are associated with the division of labour, which, in turn, is associated with employment relations and frameworks of institutional support. The thesis shows how the tensions produced by commercialization and peripheral participation are interwoven with values of meritocracy, ritual and  strategic enactment of the idea of community as well as with tools and techniques developed to address the emergence of a set of problems specific to management and governance. These are characterized as &quot;technologies of communities.&quot;</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Carlo Daffara</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Business models in FLOSS-based companies</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OSSEMP07-daffara.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The sustainability of Free/Libre/Open Source Software (FLOSS) has recently become an important aspect of the overall open source phenomenon, and as such has received a significant research attention. Since 1999, several articles addressed the role of licenses, communities and business models in FLOSS-based companies, but mostly from a theoretical point of view. In this article, we present the result of a detailed analysis of 80 FLOSS-based companies and business models, using publicly available data on service offers, mailing list archives, online articles and when available public financial data. The result is a simplified and effective classification that can be used as a guide to companies willing to offer services in the same area, and an analysis on how the community process is influenced by the choice of licensing and business model.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stefano Comino</style></author><author><style face="normal" font="default" size="100%">Fabio M. Manenti</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Dual Licensing in Open Source Software Markets</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dual_lic.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Dual licensing has proved to be a sustainable business model for various commercial software vendors employing open source strategies. In this paper we study the main characteristics of dual licensing and under which conditions it represents a profitable commercial strategy. We show that dual licensing is a form of versioning, whereby the software vendor uses the open source licensing terms in order to induce commercial customers to select the proprietary version of the software. Furthermore, we show that the software vendor prefers dual licensing to a fully proprietary strategy when the customers are very sensitive to the reciprocal terms of the open source license.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Si Chen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Economic Model of Open Source Software Adoption</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/economic_model_of_open_source_adoption.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper examines the competitive strengths of open source versus commercial software from an economic perspective. It uses a simple model of rational software selection to derive the competitive strengths of open source and commercial software models, how they can balance each other, and what the threshold or tipping point for mass adoption of open source software would be. It shows that open source software has the advantage when their commercial competitors have excessively high profit margins or when the software product???s features are not scalable due to heterogeneous user requirements.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Guido Hertel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Motivating job design as a factor in open source governance</style></title><secondary-title><style face="normal" font="default" size="100%">J Manage Governance</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/fulltext.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><publisher><style face="normal" font="default" size="100%">Springer Science+Business Media</style></publisher><volume><style face="normal" font="default" size="100%">11</style></volume><pages><style face="normal" font="default" size="100%">129–137</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Successful open source software (OSS) projects can be considered as examples of how ambitious work results can be achieved in web-based collaboration even when monetary incentives are low or absent. While former explorations of motivational processes in OSS projects primarily focused on person-oriented aspects such as motives, interests, and expected benefits of contributors, job-related factors have been largely neglected. After discussing the limitations of a personoriented focus, a research perspective is suggested that concentrates on job design and work context in OSS based on frameworks from work psychology. A theoretical analysis is presented discussing job characteristics of successful OSS projects as potential explanations of the high motivation of OSS contributors. Compared to a person-oriented perspective, the results of a job-oriented approach might be better transferable to other projects (both OSS and ??closed source?? software development) and provide guidelines for the governance of successful web-based collaboration.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Role Migration and Advancement Processes in OSSD Projects: A Comparative Case Study</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Jensen-Scacchi-ICSE-2007.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Socio-technical processes have come to the forefront of recent analysis of the open source software development (OSSD) world. Interest in making these processes explicit is mounting from industry and the software process community, as well as among those who may become contributors to an OSSD organization. This paper serves to close this gap by providing an analysis of the role migration and project career advancement process, and role-sets within, that we have observed within three large OSSD project organizations: Mozilla.org, Apache.org, and NetBeans.org.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yi Wang</style></author><author><style face="normal" font="default" size="100%">Defeng Guo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">EMOS/1: An Evolution Metrics Model for Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/EMOS1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) has become the subject of much commercial and academic interest of last. Providing quantitative metrics for OSS evolution has also become an urgent issue. However, most existing studies of software evolution have been performed on systems developed within a single company using traditional management techniques. These metrics models are not suitable for measuring OSS evolution. In this paper, we designed a preliminary evolution metrics model named EMOS/1 which contains a set of new metrics defined for evaluating OSS specially. The most significant novelty of this model is that it takes some properties of Open Source Community (OSC) into consideration. In another word, we measure the evolution of OSS and OSC together. We also provide a lightweight case study on Ubuntu project using EMOS/1. We find out the Open Source Community and its members also play essential role in OSS evolution. We expect our model can bring better understandings and explanations of phenomena in open source development and evolution.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality Improvement in Volunteer Free and Open Source Software Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/michlmayr-phd.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free and open source software has had a major impact on the computer industry since the late 1990s and has changed the way software is perceived, developed and deployed in many areas. Free and open source software, or FOSS, is typically developed in a collaborative fashion and the majority of contributors are volunteers. Even though this collaborative form of development has produced a significant body of software, the development process is often described as unstructured and unorganized. This dissertation studies the FOSS phenomenon from a quality perspective and investigates where improvements to the development process are possible. In particular, the focus is on release management since this is concerned with the delivery of a high quality product to end-users. This research has identified considerable interest amongst the FOSS community in a novel release management strategy, time based releases. In contrast to traditional development which is feature-driven, time based releases use time rather than features as the criterion for the creation of a new release. Releases are made after a specific interval, and new features that have been completed and sufficiently tested since the last release are included in the new version. This dissertation explores why, and under which circumstances, the time based release strategy is a viable alternative to feature-driven development and discusses factors that influence a successful implementation of this release strategy. It is argued that this release strategy acts as a coordination mechanism in large volunteer projects that are geographically dispersed. The time based release strategy allows a more controlled development and release process in projects which have little control of their contributors and therefore contributes to the quality of the output.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paola Giuri</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author><author><style face="normal" font="default" size="100%">Salvatore Torrisi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A test of Lazear's theory of entrepreneurship in the Open Source Software virtual community</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/giurirullanitorrisi.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper studies the emergence of entrepreneurs and their skill profile in the open source software community. We test the hypothesis that entrepreneurs, carrying out complex, multi-task activities, have more balanced skill sets compared with individuals who are less involved in project management activities. Our empirical analysis employs the SourceForge dataset containing information on 77,039 individuals working in 54,229 OSS projects. We estimate logit and ordered logit models to explore the likelihood that an individual is a project founder or manager. Our main regressors include individual attributes like skill level and diversity, and project-level controls. Results support our hypothesis.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andreas Lloyd</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">&quot;A system that works for me&quot; - an anthropological analysis of computer hackers' shared use and development of the Ubuntu system</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/ubuntu.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Based on 6 months of anthropological fieldwork both on-line and in-person among the developers working to develop and maintain the Ubuntu Linux system, this thesis examines the individual and collaborative day-to-day practices of these developers as they relate to the computer operating system that is the result of their labour. Despite being spread across the industrialized world, these &quot;&quot;hackers&quot;&quot; socialise, share their knowledge, and come to depend on each other in their work across the Internet, as well as in their in-person meetings at conferences and summits. I argue that these shared and negotiated on-line and in-person practices constitute a community of practice (Wenger 1998) rooted in a more than 40-year old &quot;oral&quot;computing tradition based on the Unix operating system.
Taking the Ubuntu system as my point of departure, I examine the network of practices, processes and actors in which it has been constructed, and
through a strategically selected constellation of theories drawn from anthropology, philosophy, and new media studies, I seek to describe and analyze the three central dimensions of a community of practice. I conclude by suggesting that it is the possibility to adopt, learn, configure, and even build the system according to their own needs, which opens the meritocratic community of practice for new contributors to scale the steep curve of learning necessary to enter and learn among them. In this way, the Ubuntu hackers come to share more than just the same system, they come to share a common history, and, to a certain extent, a shared identity through their practice.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Görkem Çetin</style></author><author><style face="normal" font="default" size="100%">Damiano Verzulli</style></author><author><style face="normal" font="default" size="100%">Sandra Frings</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Analysis of Involvement of HCI Experts in Distributed Software Development: Practical Issues</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/cetin-verzulli-sandra</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Abstract. Traditionally, free and open source software (F/OSS) developers have focused more on the features of a specific application, most of the time ignoring the necessity of user-centric design. This has mainly stemmed from the fact that developers have little interaction with HCI studies, knowledge bases and reports. Moreover, the lack of user interface designers has resulted in a lack of awareness of this area. As a consequence, the user centric design phenomenon within F/OSS applications has been neglected. In this paper, we have mentioned various problems that would slow down a F/OSS project development towards a user-engineered software, and investigated the ways that HCI experts and developers interact with each other and researched bug reporting systems by means of eligibility to issue usability bugs. For the conclusion part, we have explored possible ways to achieve a user-centric design in a project with asynchronous interaction among geographically distributed developers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rüdige Glott</style></author><author><style face="normal" font="default" size="100%">Andreas Meiszner</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysis of the Informal Learning Environment of FLOSS (Free / Libre Open Source Software) Communities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FLOSSCom_WP2_Phase_1_Report_v070709_1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The general concept behind Free/Libre/Open Source Software (henceforth FLOSS) is making the source code of software accessible to anyone who wants to obtain it. Binaries or executables are available via the Internet and can be 'freely' downloaded and used. Prolific licensing agreements such as the General Public License (GPL) define the rights users have over the product. In the literature, many terms are in use to describe the FLOSS phenomenon. Notably, Free Software (FS), a term used by Free Software Foundation (FSF) and Open Source Software (OSS) used by the Open Source Initiative (OSI). In addition, Free Open Source Software (FOSS), Libre Software (LS), and Free/Libre/Open Source Software (FLOSS) are terms frequently used by researchers. In this report the term FLOSS is used to refer to users??? freedom to use, modify, distribute, or even sell the software with little obligations as in propriety or closed source software. When a user modifies the software, he/she can either choose to keep changes made private or altruistically return them to the FLOSS community so that everyone can benefit from his derived work. FLOSS development did not begin with the inception of the Linux operating system, in 1991. Rather, the concept existed since the formation of SHARE ??? a working group set up to coordinate the programming work of the IBM 701, in 1952 (Sowe, 2007b). In the academic environment, software development and distribution among researchers and departments is not new, and goes back to the earliest days of software in university environments when software was developed to solve practical problems and could be freely shared. However, what is now true is that FLOSS has fundamentally changed the way we develop and distribute software. Enable by the Internet, geographically distributed individuals voluntarily contribute to a project by means of the Bazaar model (Raymond, 1999). Extensive peer collaboration allows project participants to write code, debug, test, and integrate software. Communities in various projects provide support services such as suggestions for products features, act as distributing organs, answer queries, help new members having problems with the software. FLOSS development not only exemplifies a viable software development approach, but also a model for the creation of self-learning and self-organizing communities (Sowe, et al. 2006c). FLOSS is also a virtual learning context in which both professional software developers and novice users benefit by leveraging their knowledge and information access repertoire. The context enable them to participate at their own convenience and learn (coding or other software related task) at their own pace (Sowe, et al. 2005; page 297). Furthermore, learners can conclude on the learning scope themselves (what to do) and decide on the method of acquiring the knowledge (how to do it). Knowledge acquisition is accomplished, for example, by having access to a large code-base, studying online documentation, asking more experienced members for assistance. In essence knowledge is acquired in FLOSS through learning by doing, which represents the drill-and-practice approach in normal constructivist environments. However, the FLOSS virtual learning context is not without its downside. Apart from physical isolation and detachment from face-to-face interaction commonly associated with virtual learning environments, learning in FLOSS requires access to Internet and moderate computer facilities. In addition, a high degree of computer literacy, reading, writing, and typing is required to participate effectively. The environment is also not conflict free. Flaming, the feeling of being ignored in a dominant discussion, disinterestedness, long delays in receiving responses from communities, the expenditure of searching through discussion archives to see issues previously raised in the communities, access rights to participate in some community activities are all major concerns in the management of the FLOSS learning context (Sowe, et al. 2005). In recent times, FLOSS is making inroads not only in business and software industries but in colleges and universities as well. There is increased interest in the FLOSS learning environment (Sowe, et al., 2004; Bacon and Dillion, 2006) and in FLOSS projects as bazaars of learning (Sowe, et al., 2006). As Faber (2002) noted, FLOSS is both an alternative teaching methodology and an educational model. The main objective of FLOSSCom is using the principles of informal learning environments of FLOSS communities to improve Information and Communication Technology (ICT) supported formal education. Despite the influence and popularity of FLOSS and the benefit inherent in its methodology, educational institutions have been slow to adapt. This can partly due to the fact that the FLOSS environment is fundamentally different from the formal learning environment in most institutions. The focus of this report is collate and report on the learning activities of individuals in various FLOSS communities. The report benefits from the experiences and expositions of various authors in order to provide a synergy and a fresh look into the learning environment of FLOSS communities. FLOSS communities, like other online communities (e.g. Community of Practice (CoPs)) have many interrelated elements that define the dynamics of the community. As such, this report is divided into 5 major sections, each focusing on a specific aspect of the learning environment of FLOSS communities with a 6th section summarizing the main findings. Section 1: The first part of the report is an introduction to FLOSS. The historical account of FLOSS is presented together with the many meanings of the term. This is followed by the demographic distribution of FLOSS participants and an explanation of what FLOSS communities are. Section 2: The next chapter examines the role of learning and knowledge exchange within the FLOSS community. It includes a description of the composition and roles of members within communities and what motivates various groups of individuals to participate in FLOSS. Section 3: After clarifying the role of learning in the FLOSS community the next chapter focuses on the content of learning processes in FLOSS. This chapter examines both, what skills are learnt and how the skills learnt within the FLOSS community are evaluated. The latter aspect is considered from the perspective of FLOSS community members as well as from the perspective of employers. Section 4: The fourth chapter examines how learning is organized within the FLOSS community. It examines the interaction between community members with regard to learning processes, the learning resources (except for technological resources) that are available and used within FLOSS communities, and the concrete learning processes. Section 5: This section looks at the technological resources used within FLOSS communities. FLOSS projects are almost exclusively administered online and one of the most important prerequisites for their coordination and cooperation is provided by the functionality of various communication and groupware tools. Section 6: The last section of the report proposes the project???s approach to learning in FLOSS. A preliminary set of guidelines as they apply to the principles of informal learning environments of FLOSS communities to improve ICT supported formal education are offered. These preliminary guidelines will be continuously amended in the following phase of the FLOSSCom project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Göktürk Mehmet</style></author><author><style face="normal" font="default" size="100%">Görkem Çetin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Out of Box Experience Issues of Free and Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/gokturkcetin</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Abstract. This study addresses the Out-Of-Box Experience (OOBE) usability issues of Free and Open Source Software (F/OSS) considering outcomes of distributed development process and high number of available product choices. A methodology is presented, usability experiments are conducted and results are discussed. The objective was to determine key factors that affect usability of F/OSS during OOBE and first hours of use. We concluded that OOBE of F/OSS was significant in software usability perception and possible adoption. User experience, visible structure, consistency and functionality of the interface had significant impact on OOBE and first hours of use. Neither online support, nor product box appearance appeared as important.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oh, Wonseok</style></author><author><style face="normal" font="default" size="100%">Jeon, Sangyong</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Membership herding and network stability in the open source community: The Ising perspective</style></title><secondary-title><style face="normal" font="default" size="100%">Management Science</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">BEHAVIOR</style></keyword><keyword><style  face="normal" font="default" size="100%">DYNAMICS</style></keyword><keyword><style  face="normal" font="default" size="100%">ECONOMICS</style></keyword><keyword><style  face="normal" font="default" size="100%">INNOVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">INVESTMENT</style></keyword><keyword><style  face="normal" font="default" size="100%">Ising theory</style></keyword><keyword><style  face="normal" font="default" size="100%">membership herding</style></keyword><keyword><style  face="normal" font="default" size="100%">MODEL</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">network connectivity</style></keyword><keyword><style  face="normal" font="default" size="100%">network stability</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">PHASE-TRANSITION</style></keyword><keyword><style  face="normal" font="default" size="100%">UNCERTAINTY</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jul</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">7</style></number><volume><style face="normal" font="default" size="100%">53</style></volume><pages><style face="normal" font="default" size="100%">1086-1101</style></pages><isbn><style face="normal" font="default" size="100%">0025-1909</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The aim of this paper is twofold: (1) to conceptually understand membership dynamics in the open source software (OSS) community, and (2) to explore how different network characteristics (i.e., network size and connectivity) influence the stability of an OSS network. Through the lens of Ising theory, which is widely accepted in physics, we investigate basic patterns of interaction and present fresh conceptual insight into dynamic and reciprocal relations among OSS community members. We also perform computer simulations based on empirical data collected from two actual OSS communities. Key findings include: (1) membership herding is highly present when external influences (e.g., the availability of other OSS projects) are weak, but decreases significantly when external influences increase, (2) propensity for membership herding is most likely to be seen in a large network with random connectivity, and (3) for large networks, when external influences are weak, random connectivity will result in higher network strength than scale-free connectivity (as external influences increase, however, the reverse phenomenon is observed). In addition, scale-free connectivity appears to be less volatile than random connectivity in response to an increase in the strength of external influences. We conclude with several implications that may be of significance to OSS stakeholders in particular, and to a broader range of online communities in general.</style></abstract><accession-num><style face="normal" font="default" size="100%">ISI:000248750100005</style></accession-num><custom1><style face="normal" font="default" size="100%">management</style></custom1><custom2><style face="normal" font="default" size="100%">SNA</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jabulani Mzaliya</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Creation of the Entrepreneurial Spirit and the Formation Of Alliances With Africa</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/WITTENBERG.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Bonaccorsi</style></author><author><style face="normal" font="default" size="100%">Dario Lorenzi</style></author><author><style face="normal" font="default" size="100%">Monica Merito</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Do firms take part in the projects of the OS community. Some preliminary evidence and a research agenda</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/paper_firm_involvement_MIT.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Open Source (OS) software has progressively gained economic importance in recent years, and more and more commercial firms are getting involved, to various extents, in the OS movement. While a number of studies have investigated motivations and business models of OS-based software companies, very few works have examined whether and how firms actively participate to open projects. This paper contributes to the literature by providing empirical evidence on the role and the activities of software houses in community developed projects. The research also proposes an original methodology of large-scale primary data collection from OS project repositories and linked Web sites. The findings show how different today???s OS movement is from its origins and how important firm involvement has become, not only numerically but also for the deepness of its impact on community projects. Finally, further research developments are suggested.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Dragging developers towards the core. How the Free/Libre/Open Source Software community enhances developers' contribution</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/rullani_socenv.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper presents a dynamic perspective on the landscape of Free/Libre/Open Source Software (FLOSS) developers' motivations and tries to isolate mechanisms sustaining developers' contribution over time. The first part of the paper uses data gathered by the empirical studies relative to the FLOSS case to judge the relative importance of each group of incentives detected by the literature. In the second part of the paper, the same data are used to further characterize developers' motivations in dynamics terms, showing how the relative importance of different incentives changes over time. Drawing inspiration from these results, the third part of the paper identifies a specific mechanism fostering developers' contribution to the community activities, namely that: &quot;Independently of developers' exogenous preferences, the more their exposure to the FLOSS community social environment, the more their contribution to the community activities&quot;. The key point of this hypothesis is that, if the exposure to the FLOSS community social environment is able to foster developers' contribution beyond the level granted by their predetermined preferences, this leads directly to the evidence that the FLOSS community is provided with a mechanism sustaining and enhancing developers' incentives to produce and diffuse code. In the last part of the paper, data relative to 14,497 developers working on SourceForge.net during two years (2001-2002) are employed to estimate a model testing the aforementioned hypothesis. Endogeneity problems are explicitly accounted for, and robustness checks are performed in order to make sure that the observed confirmation of the hypothesis is actually an empirically grounded result.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Param Vir Singh</style></author><author><style face="normal" font="default" size="100%">Ming Fan</style></author><author><style face="normal" font="default" size="100%">Yong Tan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Investigation of Code Contribution, Communication Participation and Release Strategies in Open Source Software Development: A Conditional Hazard Model Approach</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/singh_fan_tan.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study uses data from over 200 open source software (OSS) projects hosted at Sourceforge to empirically examine how OSS development characteristics affect project progress. Consistent with prior studies, we find that core developers (i.e., top 20 % of the most contributing developers) develop about 80% of the code. We also find that a group of developers that is about 50% larger than the core group is responsible for 80% of the communication. On average, the top 30% developers contribute about 81% of the messages. It is observed that projects with a clearly identified core group of developers conducting most of the coding are more efficient for project progress. We also find that highly participative peripheral group in communication positively affects project progress. In addition, high level of communication interactivity, measured by the number of email threads and average thread depth, enables a project to progress well. Our results also show that projects that draw upon the larger OSS community for beta testing progress faster. We find that the projects that do not progress well are associated with the following major factors: (i) lack of a core developer group, (ii) dormant peripheral group in communication, (iii) low communication interactivity exemplified by the lack of depth in threaded communications, and (iv) over-dependence on internal community for beta testing.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gilberto Câmara</style></author><author><style face="normal" font="default" size="100%">Frederico Fonseca</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Information Policies and Open Source Software in Developing Countries</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of American Society of Information Science and Technology</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/camara_fonseca_OSS_developing_countries.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">58</style></volume><pages><style face="normal" font="default" size="100%">121–132</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Many authors propose that open source software (OSS) is a good strategy to bring information and communication technologies to developing countries. Nevertheless, the use of OSS needs to be more than just adopting Linux as the standard for operating systems. Adoption of OSS is not only a choice of software, but also a means of acquiring knowledge. Developing countries have to use OSS as a way to gain knowledge about the technology itself and as a way of creating technology products that fit their specific needs. In this article, the authors introduce a model of OSS based on its essential characteristics to understand how developing countries may use OSS to achieve their development goals. The authors argue that there are two defining properties of any open source software. The first property is the potential for shared conceptualization and the second is the potential for modularity. By assessing how each OSS project satisfies these two conditions, a taxonomy is built for open source projects. This taxonomy will help the development of more sensible policies to promote the use of open source in developing countries.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gilberto Câmara</style></author><author><style face="normal" font="default" size="100%">Frederico Fonseca</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Information Policies and Open Source Software in Developing Countries</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/camara_fonseca_jasist_oss_submission_jan06.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Many authors propose that open source software (OSS) is a good strategy to bring information and communication technologies to developing countries. Nevertheless, the use of OSS needs to be more than just adopting Linux as the standard for operating systems. Adoption of OSS is not only a choice of software, but also a means of acquiring knowledge. Developing countries have to use OSS as a way to gain knowledge about the technology itself and as a way of creating technology products that fit their specific needs. In this article, the authors introduce a model of OSS based on its essential characteristics to understand how developing countries may use OSS to achieve their development goals. The authors argue that there are two defining properties of any open source software. The first property is the potential for shared conceptualization and the second is the potential for modularity. By assessing how each OSS project satisfies these two conditions, a taxonomy is built for open source projects. This taxonomy will help the development of more sensible policies to promote the use of open source in developing countries.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paul A. David</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Micro-dynamics of Free and Open Source Software Development. Lurking, laboring and launching new projects on SourceForge</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/davidrullani.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Quantitative methods are employed to describe two fundamental processes in the creation of free (libre) and open source software (FLOSS) that are at work in the collaborative development environment of the SourceForge.Net platform: resource mobilization and &quot;entrepreneurial initiatives&quot; which generate new development projects. The micro dynamics of the individuals' involvements in these processes are analysed by defining &quot;activity states&quot; that correspond to &quot;lurking&quot; (not contributing or contributing to projects without become a member), &quot;laboring&quot; (joining one or more projects as members), and &quot;launching&quot; (founding one or more projects). The transition probability matrices constructed from observations on the activities of 222,835 individuals who registered on SF.net (during a 14-month period, mainly in 2001) characterize first-order Markov chains describing processes that are ergodic. The computation of the limiting &quot;equilibrium&quot; distribution of individual joining and launching activities is not used here to produce long-run predictions, because the time window of the available data is too short. Instead, it is conceived as an instrument to isolate the main forces acting in the underlying entrepreneurial and recruitment dynamics at work on the platform &quot;shaking off&quot; the weaker tendencies. It is shown that, although only a small proportion of the considered cohorts of SF.net registrants become even minimally active, the active &quot;core&quot; of project members and project founders is able to attract an increasing number of developers. SourceForge is seen to be more than an attractor of projects that are being &quot;born again&quot; under open source licenses: this virtual collaborative development environment shares the regenerative properties of tangible &quot;industrial districts&quot; that give rise to new, innovative enterprises. Implications for the exploitation and exploitation processes at work in the FLOSS model and about its sustainability are also derived.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Bonaccorsi</style></author><author><style face="normal" font="default" size="100%">Monica Merito</style></author><author><style face="normal" font="default" size="100%">Rossi Cristina</style></author><author><style face="normal" font="default" size="100%">Lucia Piscitello</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source and the software industry. How firms do business out of an open innovation paradigm</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/paper_euram_2007.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) represents an ???open innovation??? paradigm based on knowledge produced and shared by developers and users. The paper inquires how OSS challenges the three Teece???s building blocks. New findings from a large survey of European software companies, show that within the OSS paradigm: (i) OSS can be a sustainable business model even in the absence of any appropriability; (ii) complementary assets are distributed collectively and made widely available without the need for dedicated contractual arrangements; (iii) a de facto dominant design may stem from a community of users/producers even independently of the presence of powerful large companies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paola Di Maio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards an Open Ontology for Emergency Response</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/TOWARDS_AN_OPEN_ONTOLOGY_FOR_ER.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Emergency Response and Relief Coordination Efforts are evolving to leverage the efficiencies offered by the internet in the area of real time communication among agents and stakeholders. There is widespread consensus both in the technical and ER community that to improve efficiency of response, information must be shared and web based protocols must be used [22]. In addition to known technical and non-technical obstacles that inhibit the effective and seamless coordination of operations, we identify issues that challenge the development of functional information and communication models. Recent studies in ontology engineering, and evidence from direct observations of open-source work groups in this field, point to the need for an easy to use 'open' conceptual and semantic framework, defined here broadly as ???Open Ontology??? (OOnt), and a corresponding design and implementation methodology that can be referenced unambiguously and universally by developers and users of information systems designed to support ER operations.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joachim Schroer</style></author><author><style face="normal" font="default" size="100%">Guido Hertel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Voluntary Engagement in an Open Web-based Encyclopedia: Wikipedians, and Why They Do It</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Schroer_Hertel_Wikipedia_Motivation.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The online encyclopedia Wikipedia can be considered as a highly successful Open Content project, written and maintained completely by volunteers. Little is known, however, about the motives and interests of these volunteers. Results from an online survey among 106 contributors to the German Wikipedia project are presented. As potential predictors of contributors??? engagement and satisfaction, both motives derived from social sciences (e.g., costs-benefits, valence of the Wikipedia goals, identification with Wikipedia, etc.) as well as perceived task characteristics (e.g., task significance, autonomy, skill variety, etc.) were measured. The results reveal that satisfaction ratings of contributors are determined by perceived benefits, identification with the Wikipedia community, and task characteristics. Contributors??? engagement (e.g., hours per week) was particularly determined by their tolerance for opportunity costs and the experienced characteristics of their tasks, the latter effect being partially mediated by intrinsic motivation. Most relevant task characteristics both for contributors??? engagement and satisfaction were autonomy, task significance, and skill variety. Additional motives reported by Wikipedia contributors suggest the importance of generativity.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oded Nov</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What motivates Wikipedians: motivations for Wikipedia content contribution</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Nov_Wikipedia_motivations_opensource.mit.edu.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Contributors??? motivations are critical for sustaining Wikipedia and other collaborative user-generated content outlets. Such outlets are based on contributions by people who volunteer their time and talent for the creation of content in return for no monetary reward. Therefore, in order to understand what underlies user-generated content contribution, we would need to find out what motivates volunteer content contributors. The results of a survey of 151 Wikipedia contributors indicate that the top motivations for contribution are Fun and Ideology. As expected, it was found that the levels of each of the motivations Fun, Values, Understanding, Enhancement, Protective, and Career were positively correlated with contribution level. Somewhat unexpectedly, contribution level was not correlated significantly with the Ideology and Social motivations.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Greg R Vetter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Licensing &amp; Scattering Opportunism in Software Standards</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Vetter.OSS_.ScatteringOpportunism.FINAL_.withAppendixA.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Despite their beneficial influence on interoperability and markets, problems of detrimental opportunism occur with technology standards, including standards implemented in software, which this Article calls &quot;Software Standards.&quot; Inspired by new perspectives on the study of semicommons in the history of real property, this Article contemplates the substitutability of free and open source software (&quot;FOSS&quot;) for traditional standard-setting approaches. Standards are analogous to semicommons, where public and private use interact, raising the possibility of opportunistic influence on the Software Standard to increase private gain at the expense of the public benefit in a more uniform standard.  With its source code disclosure requirement, FOSS shifts and dampens this opportunism, although various limits influence the reach of its effect. The political economy around a standard will express itself differently under a FOSS implementation, and clearing intellectual property rights in the standard is no more certain than under the traditional standard-setting approach.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Guillermo Flores</style></author><author><style face="normal" font="default" size="100%">Alejandro Mendighetti</style></author><author><style face="normal" font="default" size="100%">Jorge Sánchez</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Love and other demons: game theory in enterpreneurial and love relationships</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">December</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/ARTICULO_1-del_amor_y_otros_demonios-_teoria_de_juegos_en_las_relaciones_empresariales_y_amorosas.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The article studies the risk aversion and information assymetry differences in two fields of relationships: between partners and in a loving couple.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dario Lorenzi</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Innovativeness of software solutions: evidence from an alternative methodology. Comparing Free/Open Source and proprietary products</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Dec</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lorenzi_rossi_MIT_20071220.pdf</style></url><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin_-_SSRN.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The issue of innovation processes taking place in the software sector  is currently widely debated. Challenging questions arise about what products/services have to be considered innovative, and whether a specific artefact is innovative or not. In this framework, the widespread success of the Free/Open Source Software (FOSS) put forward new research issues, dealing with whether and how programs developed according to the new production paradigm turn out to be more innovative than traditional ones. In this framework, this paper aims at contributing to the literature by addressing three main research questions: (i) are software solutions produced by Small and Medium Enterprises (SMEs) innovative? (ii) What kinds of innovations are implemented? And, finally, (iii) are programs based on FOSS more innovative than proprietary ones?Basing on a sample of 134 software solutions produced by Italian SMEs and using an original methodology to asses the problem of evaluating innovation in the software field, we provides some first insights of what emerges if we set aside the traditional innovation indicators and endower to build alternative metrics, specifically developed to target the complexity of the innovation processes in the software markets.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Giampaolo Garzarelli</style></author><author><style face="normal" font="default" size="100%">Yasmina Reem Limam</style></author><author><style face="normal" font="default" size="100%">Bjørn Thomassen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software and Economic Growth: A Classical Division of Labor Perspective</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/0SSGROWTHMIT.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The article turns to classical economic insights on the division of labor and to institutional reasoning to identify some costs and benefits of Open Source Software (OSS) and proprietary software production. It suggests that, thanks to its licenses, OSS favors market expansion more than proprietary software does by tapping into spontaneous work input. The spontaneous tapping leads to a division of labor that exhibits what the article calls redundant economies. By generating a circle of knowledge growth, reuse, and sharing, redundant economies lead to increasing returns, which are crucial for economic growth.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Oliver Alexy</style></author><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Most firms that use or develop software today face the questions of whether and how to engage in open source software. Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the theoretical frameworks of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a model of how job function influences individuals??? proclivity to support their employers??? adoption of OSS and OSS practices. We argue that job function determines which tasks in the software development process are part of an individual???s daily routine, and that different tasks are differentially affected by OSS. Our study is based on interviews with 25 individuals and a large-scale survey distributed to 249 participants in the telecommunications department of a multinational company. The results, although consistent with theoretical considerations, are nevertheless surprising. Distinguishing between developers, software testers, software architects, project managers, and managers, we find greater involvement in OSS activities to be favored most strongly by software testers, followed by software architects and managers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate engagement in OSS. A corporation interested in adopting OSS and open innovation processes should thus take into account the job function-related incentives of each individual as well as various organizational factors. More generally, we propose that models developed to predict IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which we maintain will be determined largely by their job functions.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dirk Riehle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Economic Motivation of Open Source: Stakeholder Perspectives</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/computer-2007.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software has changed the rules of the game, impacting significantly the economic behavior of stakeholders in the software ecosystem. In this new environment, developers strive to be committers, vendors feel pressure to produce open source products, and system integrators anticipate boosting profits.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Long, Y.</style></author><author><style face="normal" font="default" size="100%">Siau, K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social network structures in open source software development teams</style></title><secondary-title><style face="normal" font="default" size="100%">Journal of Database Management</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">INNOVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">longitudinal study</style></keyword><keyword><style  face="normal" font="default" size="100%">MODEL</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">social</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">structure</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Apr-Jun</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">18</style></volume><pages><style face="normal" font="default" size="100%">25-40</style></pages><isbn><style face="normal" font="default" size="100%">1063-8016</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Drawing on social network theories and previous studies, this research examines the dynamics of social network structures in open source software (OSS) teams. Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure. The finding suggests that the interaction pattern of OSS projects evolves from a single hub at the beginning to a corel periphery model as the projects move forward.</style></abstract><accession-num><style face="normal" font="default" size="100%">ISI:000244332400003</style></accession-num><notes><style face="normal" font="default" size="100%">&quot;Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure.&quot;

no pdf</style></notes><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">SNA</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Okoli, C.</style></author><author><style face="normal" font="default" size="100%">Oh, Wonseok</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Investigating recognition-based performance in an open content community: A social capital perspective</style></title><secondary-title><style face="normal" font="default" size="100%">Information &amp; Management</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">open content</style></keyword><keyword><style  face="normal" font="default" size="100%">recognition-based performance</style></keyword><keyword><style  face="normal" font="default" size="100%">social capital</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">social status</style></keyword><keyword><style  face="normal" font="default" size="100%">virtual communities</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Apr</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">44</style></volume><pages><style face="normal" font="default" size="100%">240-252</style></pages><isbn><style face="normal" font="default" size="100%">0378-7206</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">As the open source movement grows, it becomes important to understand the dynamics that affect the motivation of participants who contribute their time freely to such projects. One important motivation that has been identified is the desire for formal recognition in the open source community. We investigated the impact of social capital in participants' social networks on their recognition-based performance; i.e., the formal status they are accorded in the community. We used a sample of 465 active participants in the Wikipedia open content encyclopedia community to investigate the effects of two types of social capital and found that network closure, measured by direct and indirect ties, had a significant positive effect on increasing participants' recognition-based performance. Structural holes had mixed effects on participants' status, but were generally a source of social capital. (C) 2007 Elsevier B.V. All rights reserved.</style></abstract><accession-num><style face="normal" font="default" size="100%">ISI:000247156800002</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes><custom1><style face="normal" font="default" size="100%">management</style></custom1><custom2><style face="normal" font="default" size="100%">SNA</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">N. Good</style></author><author><style face="normal" font="default" size="100%">J. Grossklags</style></author><author><style face="normal" font="default" size="100%">D. Mulligan</style></author><author><style face="normal" font="default" size="100%">Konstan, J.A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Noticing Notice: A large-scale experiment on the timing of software license agreements.</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">28/04/2007</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">San Jose, CA</style></pub-location><pages><style face="normal" font="default" size="100%">607-616</style></pages><isbn><style face="normal" font="default" size="100%">978-1-59593-593-9</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">F. Harper</style></author><author><style face="normal" font="default" size="100%">D. Frankowski</style></author><author><style face="normal" font="default" size="100%">Drenner, S.</style></author><author><style face="normal" font="default" size="100%">Y. Ren</style></author><author><style face="normal" font="default" size="100%">S. Kiesler</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author><author><style face="normal" font="default" size="100%">Kraut, R.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Talk Amongst Yourselves: Inviting Users to Participate in Online Conversations.</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Intelligent User Interfaces  </style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">Proceedings of the 12th international conference on Intelligent user interfaces</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">28/01/2007</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Honolulu, Hawaii</style></pub-location><pages><style face="normal" font="default" size="100%">62-71</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-481-2</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">F. Harper</style></author><author><style face="normal" font="default" size="100%">X. Li</style></author><author><style face="normal" font="default" size="100%">Y. Chen</style></author><author><style face="normal" font="default" size="100%">J. Konstan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social Comparisons to Motivate Contributions to an Online Community.</style></title><secondary-title><style face="normal" font="default" size="100%">Persuasive Technology</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">26/04/2007</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Palo Alto, CA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Morasca, Sandro</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">1st International Workshop on Trust in Open Source Software (TOSS)</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/1st Intl Workshop on Trust.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">371 - 373</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The 1st International Workshop on Trust in Open Source Software (TOSS) focuses on one of the major factors in the adoption of software solutions: the trustworthiness of OSS, which has influenced the widespread adoption of OSS in industry. Software quality aspects have been investigated for a long time in the academia but the usage/production of OSS is creating new challenges and the points of view of the industry and the academia may differ, especially on the trustworthiness of OSS. The aim of the workshop is to open a communication channel between the industry and the academia focusing on this issue and promote a long lasting discussion on it. The workshop tries to identify the different points of views and the different approaches that can result in benefits for the software industry.
</style></abstract><section><style face="normal" font="default" size="100%">48</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">2nd International Workshop on Public Data about Software Development (WoPDaSD 2007)</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/2nd Intl Workshop on Public Data.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">381 - 383</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Exchange of detailed data about software development between research teams, and specifically about data available from public repositories of libre (free, open source) software projects is becoming more and more common. This workshop will explore the benefits and problems of such exchange, and the steps needed to foster it. As a case example of data exchange, the workshop organizers suggest two large datasets to be analyzed by participants.
</style></abstract><section><style face="normal" font="default" size="100%">51</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Quang Vu Dang</style></author><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Hamet, Benoît</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Authenticating from multiple authentication sources in a collaborative platform</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Authenticating from multiple.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">229 - 234</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents a proposal to address the need for multiple authentication sources for users of collaborative work platforms. The proposed approach, developed for the needs of GET and Picolibre, relies on a generic solution that integrate groupware servers in a Shibboleth infrastructure. We have developed adapters for this integration, that we contributed to the phpGroupware
project. This document should serve as a basis for discussion in order to validate the level of generality of the proposed approach. We hope that this approach can also help maintainers of other collaboration platforms, who want to integrate a park of deployed platforms with external user identification and authentication services, get a better view of solutions available with Shibboleth.
</style></abstract><section><style face="normal" font="default" size="100%">20</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Morgan, Lorraine</style></author><author><style face="normal" font="default" size="100%">Finnegan, Patrick</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Benefits and Drawbacks of Open Source Software: An Exploratory Study of Secondary Software Firms</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Benefits and Drawbacks.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">307 - 312</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Much of the assessment of OSS benefits and drawbacks has been based on anecdotal evidence appearing in practitioner publications, white papers, web articles etc. To a greater extent this research has tended to concentrate more on the technical benefits and drawbacks of OSS rather than their business counterparts. Furthermore, public administrations and companies operating within the primary software sector have traditionally been the focus for research on OSS benefits and drawbacks. Taking the viewpoint of IS/IT managers in 13 companies operating in the secondary software sector in Europe, this paper examines their experiences of the benefits/drawbacks of OSS.
</style></abstract><section><style face="normal" font="default" size="100%">33</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Pfaff, Charmaine</style></author><author><style face="normal" font="default" size="100%">Hasan, Helen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Can Knowledge Management be Open Source?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Can Knowledge Management.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">59 - 70</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract><section><style face="normal" font="default" size="100%">5</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Studer, Matthias</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Community Structure, Individual Participation and the Social Construction of Merit</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Community Structure Individual.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">161 - 172</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 “membership esteem” to members involved in more prestigious activities.
</style></abstract><section><style face="normal" font="default" size="100%">13</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cabano, Michele</style></author><author><style face="normal" font="default" size="100%">Monti, Cesare</style></author><author><style face="normal" font="default" size="100%">Piancastelli, Giulio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Context-Dependent Evaluation Methodology for Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Context-Dependent Evaluation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">301 - 306</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Many evaluation methodologies have been proposed to mitigate the risks of choosing Open Source Software as an effective solution to an enterprise’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.
</style></abstract><section><style face="normal" font="default" size="100%">32</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Dueñas, Santiago</style></author><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Corporate Involvement of Libre Software: Study of Presence in Debian Code over Time</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Corporate Involvement of Libro.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">121 - 132</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract><section><style face="normal" font="default" size="100%">10</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors></contributors><titles><title><style face="normal" font="default" size="100%">Data and analyses sharing to support research on free/libre open source software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Data and analyses sharing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">355 - 356</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Research on FLOSS has relied on several different kinds of scientific evidence, such as the archives created by the FLOSS developers, versioned code repositories, mailing list messages and bug and issue tracking repositories [1]. FLOSS teams retain and make public archives of many of their activities as by-products of their open technology-supported collaboration. However, the easy availability of primary data provides a misleading picture of ease of conducting research on FLOSS. Precisely because these data are by-products, they are generally not in a form that is useful for researchers. Instead potentially useful data is locked up in HTML pages, CVS log files, text-only mailing list archives or dumps of website databases. FLOSS research projects, therefore, expend significant energy collecting and re-structuring these archives for their research, which is repetitive and wasteful [2]. Furthermore, different researchers will extract different data at different points in time, take different approaches to processing and cleaning data and make different decisions about analyses, but without all of these decisions being visible, auditable or reproducible. In principle, these latter problems can be addressed by individual researchers better documenting what they have done. However, research publications typically have restrictions on publication lengths that make complete discussion impossible. Furthermore, published papers are just the tip of the iceberg, and knowing what others have done does not necessarily make it any easier to replicate the results.
</style></abstract><section><style face="normal" font="default" size="100%">42</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Different Bug Fixing Regimes? A Preliminary Case for Superbugs</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Different Bug Fixing Regimes.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">247 - 252</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper investigates the processes by which bugs are fixed in open-source software projects. Focusing on Mozilla and combining data from both its bug tracker (Bugzilla) and from its CVS, we suggest that: a) Some bugs resist beyond the first patch applied to the main branch of the source code in relation to them, which we denote as superbugs; b) There might exist different bug fixing regimes; c) priority and severity flags as defined in bug repositories are not optimized for superbugs and might lead to a involuntary side effects; d) The survival time of superbugs is influenced by the nature of the discussions within Bugzilla, by bug dependencies and by the provision of contextual elements.
</style></abstract><section><style face="normal" font="default" size="100%">23</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Abiteboul, Serge</style></author><author><style face="normal" font="default" size="100%">Dar, Itay</style></author><author><style face="normal" font="default" size="100%">Pop, Radu</style></author><author><style face="normal" font="default" size="100%">Vasile, Gabriel</style></author><author><style face="normal" font="default" size="100%">Vodislav, Dan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">EDOS Distribution System: a P2P architecture for open-source content dissemination</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/EDOS Distribution System.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">209 - 215</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The open-source software communities currently face an increasing complexity of managing the software content among theirs developers and contributors. This is mainly due to the continuously growing size of the software, the high frequency of the updates, and the heterogeneity of the participants. We propose a distribution system that tackles two main issues in the software content management: efficient content dissemination through a P2P system architecture, and advanced information system capabilities, using a distributed index for resource location.
</style></abstract><section><style face="normal" font="default" size="100%">17</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Déchelle, François</style></author><author><style face="normal" font="default" size="100%">Mancinelli, Fabio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">EDOS-Tools Tutorial: EDOS Tools for Linux Distributions Dependencies Management and Quality Assurance</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/EDOIS- Tools Tutorials.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">363 - 364</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free and Open Source Software (FOSS) distributions are the results of the effort of third party actors in collecting independently developed software products, in a consistent and usable form. The widespread adoption of these distributions as infrastructural components in many strategic contexts of the information technology society has drawn the attention on the issues regarding how to handle the complexity of assembling and managing a huge number of (packaged) components and how to guarantee their quality. This tutorial will describe how the EDOS project has tackled these issues. First it will describe the problems related to the quality assurance of Linux distributions and will present the tools that have been developed to manage testing process. It will then introduce the problems that occur when managing inter-package relations in large package repositories and will showcase tools that can be used to analyze and manage large package repositories.
</style></abstract><section><style face="normal" font="default" size="100%">45</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Günes Koru, A.</style></author><author><style face="normal" font="default" size="100%">Zhang, Dongsong</style></author><author><style face="normal" font="default" size="100%">Liu, Hongfang</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Effect of Coupling on Defect Proneness in Evolutionary Open-Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Effect of Coupling on Defect.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">271 - 276</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Previous research on closed-source software found that highly coupled software modules were more defect prone, which makes it important to understand the effect of coupling on defect proneness in open-source software (OSS) projects. For this purpose, we used Cox proportional hazards modeling with recurrent events. We found that the effect of coupling was significant, and we quantified this effect on defect proneness.
</style></abstract><section><style face="normal" font="default" size="100%">27</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Eseryel, U.</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Eileen Allen</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Emergent Decision-Making Practices in Free/Libre Open Source Software (Floss) Development Teams</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Emergent Decision-Making.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">71 - 84</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness.
</style></abstract><section><style face="normal" font="default" size="100%">6</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jaaksi, Ari</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Experiences on Product Development with Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">gtk</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">nokia</style></keyword><keyword><style  face="normal" font="default" size="100%">tablet</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Experiences on Product Development.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">85 - 96</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This article discusses Nokia’s experiences of using open source in commercial product development. It presents the development model used in the creation of mobile consumer devices and highlights the opportunities and challenges experienced. This article concludes that the main benefits come from the utilization of already available open source components, and from their quality and flexibility. It illustrates the challenges and solutions faced when mixing open and closed development models at Nokia.
</style></abstract><section><style face="normal" font="default" size="100%">7</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Exploring the Effects of Coordination and Communication Tools on the Efficiency of Open Source Projects using Data Envelopment Analysis</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Exploring the Effects Coodination.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">97 - 108</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we propose to explore possible benefits of communication and coordination tools in open source projects using data envelopment analysis (DEA), a general method for efficiency comparisons. DEA offers several advantages: It is a non-parametric optimization method without any need for the user to define any relations between different factors or a production function, can account for economies or diseconwhile omies of scale, and is able to deal with multi-input, multi-output systems in which the factors have different scales. Using a data set of 30 open source project retrieved from SourceForge.net, we demonstrate the application of DEA, showing that the efficiency of the projects is in general relatively high. Regarding the effects of tool employment on the efficiency of projects, the results were surprising: Most of the possible tools, and overall usage, showed a negative relationship to efficiency.
</style></abstract><notes><style face="normal" font="default" size="100%">&quot;based on the date january 8, 2007, we selected the 30 most often downloaded projects from Sourceforge.net&quot;</style></notes><section><style face="normal" font="default" size="100%">8</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Botturi, Luca</style></author><author><style face="normal" font="default" size="100%">Mazza, Riccardo</style></author><author><style face="normal" font="default" size="100%">Tardini, Stefano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">FOSLET 07 — Workshop on Free and Open Source Learning Environments and Tools</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FOSLET 07 workshop.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">385 - 387</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Web-based Learning Environments supported by Course Management Systems (also known as Learning Management Systems) are nowadays a valid solution for institutions, companies, schools and universities that deliver eLearning or support blended-learning activities. Learning Environments are used to distribute information and content material to learners, prepare and deliver assignments and tests, engage in discussions, and manage distance classes without time and space restrictions.
</style></abstract><section><style face="normal" font="default" size="100%">52</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gangadharan, G.</style></author><author><style face="normal" font="default" size="100%">D’Andrea, Vincenzo</style></author><author><style face="normal" font="default" size="100%">Weiss, Michael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Open Services: Conceptualization, Classification, and Commercialization</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Free Open Services.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">253 - 258</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The concept of Free/Open Services (F/O-Services) emerges by bringing together services with Free/Open Source Software (FOSS). F/O-Services enable the creation of transparent composite services collectively and allow people and other services to access them. This paper extends the concept of F/O-Services beyond the level of open interfaces, analyzing the associated licensing interpretations and exploring the notion of open service dependencies. Further, the paper overviews the business models for F/O-Services as a part of this social mechanism of exchange.
</style></abstract><section><style face="normal" font="default" size="100%">24</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schmidbauer, Harald</style></author><author><style face="normal" font="default" size="100%">Gençer, Mehmet</style></author><author><style face="normal" font="default" size="100%">Tunalıo_lu, Vehbi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Open Source Software Adoption, Public Policies and Development Indicators: An International Comparison</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Free OSS Adoption.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">331 - 336</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Despite the growing body of research on the inner workings of FOSS development, there are few studies on its relation with broader developments in society. In this study we have attempted a preliminary investigation of (1) how FOSS prevalence is related to economic and human development indicators of countries, (2) whether public policies regarding FOSS emerge in a consistent relation with these indicators in several clusters of countries constructed from the United Nation’s human development index, and (3) the relation of software piracy to development indicators. Our results point to relative significance of non-economic factors in FOSS adoption, lack of consistent policies among public agencies, and irrelevance of non-economic factors on software piracy. In addition, the study demonstrates the possibility of developing FOSS indices for larger scale diagnosis and strategizing.
</style></abstract><section><style face="normal" font="default" size="100%">37</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Capiluppi, Andrea</style></author><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From the Cathedral to the Bazaar: An Empirical Study of the Lifecycle of Volunteer Community Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/From the Cathedral.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">31 - 44</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Some free software and open source projects have been extremely successful in the past. The success of a project is often related to the number of developers it can attract: a larger community of developers (the ‘bazaar’) identifies and corrects more software defects and adds more features via a peer-review process. In this paper two free software projects (Wine and Arla) are empirically explored in order to characterize their software lifecycle, development processes and communities. Both the projects show a phase where the number of active developers and the actual work performed on the system is constant, or does not grow: we argued that this phase corresponds to the one termed ‘cathedral’ in the literature. One of the two projects (Wine) shows also a second phase: a sudden growing amount of developers corresponds to a similar growing output produced: we termed this as the ‘bazaar’ phase, and we also argued that this phase was not achieved for the other system. A further analysis revealed that the transition between ‘cathedral’ and ‘bazaar’ was a phase by itself in Wine, achieved by creating a growing amount of new modules, which attracted new developers.
</style></abstract><section><style face="normal" font="default" size="100%">3</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Guiding the Discovery of Open Source Software Processes with a Reference Model</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Guiding the Discovery.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">265 - 270</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper describes a reference model for open source software (OSS) processes and its application towards discovering such processes from OSS project artifacts. This reference model is the means to map evidence of an enacted process to a classification of agents, resources, tools, and activities that characterize the process.
</style></abstract><section><style face="normal" font="default" size="100%">26</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How to Gather FLOSS Metrics</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/How to gather Floss Metrics.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">361 - 362</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this half-day tutorial, participants will gain hands-on exposure to key technologies for data collection about open source projects.
</style></abstract><section><style face="normal" font="default" size="100%">44</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Jokinen, Jyke</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Influence in the Linux Kernel Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Influence in the Linux Kernel.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">203 - 208</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Several success stories of open source (OS) products have been seen during last decade. Due to the economical importance of the products, it is important to know who are the ones who have the largest influence to the products. Is there a dominant player in developing communities? In this paper1 the aspect is studied with respect to the Linux Kernel community. We show that the influence is centered to a small number of core people, and corporates have a large impact to the development. Moreover, we enumerate the most influential companies.
</style></abstract><section><style face="normal" font="default" size="100%">16</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Noll, John</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Innovation in Open Source Software Development: A Tale of Two Features</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">features</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">metacity</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Innovation in OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">109 - 120</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines two features of selected open source products: “tabbed browsing” as realized in the Firefox web browser, and “edge magnetism” found in the Gnome desktop environment’s Metacity window manager. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, in attempt to discover the process by which requirements are proposed, adopted, and implemented in their respective Open Source projects. The results confirm the importance of user participation in Open Source projects.
</style></abstract><notes><style face="normal" font="default" size="100%">&quot;archives of project discussion forums were then examined to determine when the feature was first proposed, how it was debated, and when it was ultimately adopted&quot;</style></notes><section><style face="normal" font="default" size="100%">9</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Osiński, Stanisław</style></author><author><style face="normal" font="default" size="100%">Weiss, Dawid</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Introducing Usability Practices to OSS: The Insiders’ Experience</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Introducing Usability Practices.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">313 - 318</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents a case study of introducing usability practices to a small open source project called Carrot2. We describe our experiences from a point of view of an active Carrot2 developer, who is at the same time a usability enthusiast and practitioner. We perform a critical analysis of the system’s original user interface and describe the steps we took to improve it. We also analyse the success factors and the impact of the whole redesign process.
</style></abstract><section><style face="normal" font="default" size="100%">34</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Introduction to OSS 2007 Tutorial Program</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Introduction to OSS 2007.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">359 - 360</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Today, most software researchers and professionals consider Open Source as a greatly successful paradigm for large-scale production of high-quality software systems. However, most of them would probably agree that successfully applying this paradigm requires dealing with a number of important issues. One of the best reasons to attend OSS conference series is being able to discuss these issues in an unprecedented gathering of top-notch researchers, developers, and leaders from all avenues of the open source movement. Attending good tutorials, in particular, is a great opportunity for getting in touch with new ideas and discussing them in depth with real experts.
</style></abstract><section><style face="normal" font="default" size="100%">43</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sandra Slaughter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Introduction to Panel Discussions at the Third International Conference on Open Source Systems — OSS 2007</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Introduction to Panel Discussions.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">351 - 352</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Two diverse, stimulating and important panel discussions are included in this year’s programme on open source systems. The first panel explores the diverse set of legal issues and risks that arise as governments increasingly adopt open source systems. Governments are attracted to open source software systems by the potential cost savings, open standards and protocols, and the flexibility, adaptability and reliability of the systems. However, there are serious legal issues and liabilities that can arise when governments adopt open source systems. This panel identifies and examines potential legal risks and liabilities from open source systems adoption in the government context. Some of the important legal concerns discussed by this panel include intellectual property rights, licensing, and protection of sensitive or confidential information. The second panel is organized as a debate in which the panelists will consider the advantages and disadvantages of the sharing of research data and analyses by open source systems researchers. The area of open source systems has attracted numerous researchers from many different disciplines. In part, the attraction of research on open source systems is due to the public information available about open source communities. Using this information, researchers have been uncovering fascinating insights about how open source systems are developed and used and how open source communities function. Unfortunately, as noted by this panel, the work products of this research are not readily available to the public. This prevents new researchers from validating, building upon and extending the research already conducted by others. However, making research work products available to the others, while potentially valuable, has associated disadvantages. For example, certain kinds of data collected by a researcher (such as surveys or other confidential information) may not be released to the public, given human subjects concerns. In addition, it can require substantial cost and effort on the part of the researcher to make research work products understandable and usable by others. This panel debates the issues surrounding the pros and cons of making open source systems research work products available to researchers.
</style></abstract><section><style face="normal" font="default" size="100%">40</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hissam, Scott</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Introduction to Workshops at the Third International Conference on Open Source Systems — OSS 2007</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Introduction  to Workshops.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">369 - 369</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The International Conference on Open Source Systems owes its success to the increasing desire of researchers and academicians to engage in open conversation and sharing with the open source community regarding its’motivations, products, processes and data. This diverse representation of the growing practical and academic interest in Open Source Systems and its impact on the software engineering community is represented in the five workshops that accompany this year’s conference. OSS 2007 welcomes these workshops as participants engage, in an informal setting, driven by fundamental academic interests, or by more applied industrial or commercial interests to discuss technical issues, exchange research ideas, and to develop a community in the field of Open Source Software and/or Systems.
</style></abstract><section><style face="normal" font="default" size="100%">47</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Evangelia Berdou</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Learning and the imperative of production in Free/Open Source development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Learning and the imprative of production.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">235 - 240</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper examines the role of learning in structuring access and participation in F/OS communities. In particular it highlights the challenges and barriers to access faced by new developers and the expectations of senior developers regarding the mindsets and capabilities of new contributors. It is argued that learning in F/OS is inextricably connected with the demand for continuous production. The evidence presented is drawn from interviews conducted with inexperienced and experienced contributors from the GNOME and KDE projects. The author challenges the view of learning as an enculturation process and the paper contributes to the understanding of power relations among established and peripheral members in communities of practice.
</style></abstract><section><style face="normal" font="default" size="100%">21</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Persson, Anna</style></author><author><style face="normal" font="default" size="100%">Lings, Brian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Learning Through Practical Involvement in the OSS Ecosystem: Experiences from a Masters Assignment</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Learning through practical involvement.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">289 - 294</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Increased awareness of and interest in Open Source has led to a number of university teaching initiatives, at both national and European level. In this paper we present experiences from a practical assignment designed to give students on an Open Source Masters course an insight into real involvement in Open Source projects. It discusses the motivations for the assignment, and how it was set up and executed. It reports on post facto student feedback, and reflects on a parallel, reduced exercise offered at undergraduate level. We find that the learning experience was both positive and valuable in that it gave real insight into Open Source participation, and also encouraged further participation in Open Source projects by students after the course had completed.
</style></abstract><section><style face="normal" font="default" size="100%">30</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nic Suzor</style></author><author><style face="normal" font="default" size="100%">Fitzgerald, Brian</style></author><author><style face="normal" font="default" size="100%">Perry, Mark</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Legal issues for free and open source software in government</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Legal Issues for Free and OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">353 - 354</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">As more governments begin to adopt and release free and open source software, it is important to be able to readily recognise and identify the associated legal risks and potential liabilities. This panel will examine and discuss the most common of these associated risks and liabilities. These issues include, but are not limited to: 

  indemnities against claims of intellectual property  infringement from third parties
  requirements of consumer protection and antitrust legislation
  obligations to redistribute source, and when they arise
  enforceability of free software licences
  layering and combining of licences
  dual-licensing
  licence incompatibility
  software patent liability
  contemporary developments in software licensing
</style></abstract><section><style face="normal" font="default" size="100%">41</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schofield, Andrew</style></author><author><style face="normal" font="default" size="100%">Cooper, Grahame</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Levels of Formality in FOSS Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Levels of Formality.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">337 - 342</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">One of the aspects of Free and Open Source Software (FOSS) which may act as a significant deterrent to its adoption, is the method used to collaboratively develop the software and provide support through the use of communities. It is not until this method is examined more closely that its many advantages can be realised. The method can, however, seem very disorganised especially when compared with traditional proprietary development styles. A key difference between these two development approaches lies in the management of projects, and perhaps as a consequence, in the level of formality in the community environment.
This paper presents the results of empirical survey research investigating FOSS community participants’ views on the level of formality in FOSS, and the way in which this affects both development and support provision activities. The paper then concludes by analysing what can be learnt from the participant’s views.
</style></abstract><section><style face="normal" font="default" size="100%">38</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gao, Yongqin</style></author><author><style face="normal" font="default" size="100%">Madey, Greg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Network Analysis of the SourceForge.net Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Network Analysis of the SourceForge.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">187 - 200</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software is central to the functioning of modern computer-based society. The OSS (Open Source Software) phenomenon is a novel, widely growing approach to develop both applications and infrastructure software. In this research, we studied the community network of the SourceForge.net, especially the structure and evolution of the community network, to understand the Open Source Software movement. We applied three different analyses on the network, including structure analysis, centrality analysis and path analysis. By applying these analyses, we are able to gain insights of the network development and its influence to individual developments.
</style></abstract><section><style face="normal" font="default" size="100%">15</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ayala, Claudia</style></author><author><style face="normal" font="default" size="100%">Søensen, Carl-Fredrik</style></author><author><style face="normal" font="default" size="100%">Conradi, Reidar</style></author><author><style face="normal" font="default" size="100%">Franch, Xavier</style></author><author><style face="normal" font="default" size="100%">Li, Jingyue</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Collaboration for Fostering Off-The-Shelf Components Selection</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Collaboration.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">17 - 30</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The use of Off-The-Shelf software components in Component- Based Development implies many challenges. One of them is the lack of available and well-suited data to support selection of suitable OTS components. This paper proposes a feasible and incremental way to federate and reuse the different efforts for finding, selecting, and maintaining OTS components in a structured way. This is done not only for supporting OTS components selection, but also to overcome reported problems with the integration and maintenance of component repositories. It is based on the “open source collaboration” idea to incrementally build an OTS components reuse infrastructure, enabling automatic support for OTS selection processes.
</style></abstract><section><style face="normal" font="default" size="100%">2</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software and Open Data Standards as a form of Technology Adoption: a Case Study</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OSS and Open Data Standards.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">325 - 330</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The process of technology adoption has been studied for long time to give instruments to evaluate the best strategies to ease the introduction of technology. While the main research on Open Source Software focuses mainly on the development process, team collaboration and programmers’ motivations, very few studies consider Open Source Software in this context. In this paper, we provide an overview of literature on technology adoption that can be useful to relate the concepts. We then provide a case study with historical data about file generation and usage across time to evaluate the adoption of Open Source Software and Open Data Standards in the specific case provided.
</style></abstract><section><style face="normal" font="default" size="100%">36</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">van der Linden, Frank</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software and Product Lines 2007</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OSS and product lines 2007.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">375 - 376</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Embedded industries have invested a lot in the introduction of software product lines in their software development. In addition, using open source software appears to be a profitable way to obtain good software. This is also applicable for organizations doing product line engineering. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source communities. In fact, the configuration mechanisms used in open source communities may be applicable within software product lines as well. In addition, product line organisations are usually involved in distributed development, which works very efficiently within open source communities. However, at present, there is limited interaction between the open source and product line development communities. The aim for the workshop is to explore what the two communities can learn from each other and to develop a better understanding of how the two communities can benefit from each other. The workshop deals with the following issues:
 
–Community: Ownership, control and management of product line assets in an open source community
–Visibility of the code: when it is valuable to share proprietary code and how to take the right decision.
–Architecture Views: Creation of different levels of architecture visibility: proprietary, among closed consortium, public.
–Is this possible?
–Product line requirements roadmaps and planning in open source development
–Variability management: Using the open source community to evolve components and being explicit about variability
–Variability representation: in an open source community
–Deployment: Open source for the platform and in applications
–Heterogeneous processes: Cohabitation of product line management and agile processes
–Tools: Open source asset management tools in product line development
–Domain and application engineering and their meaning in an open source context
–Recovery and recognition of a product line in an open source asset base
–Legal: Aspects dealing with evolutionary, variability or distribution of development relating to legal risks involving: liability, warranties, patent infringements etc.
</style></abstract><section><style face="normal" font="default" size="100%">49</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Boccacci, Patrizia</style></author><author><style face="normal" font="default" size="100%">Carrega, Veronica</style></author><author><style face="normal" font="default" size="100%">Dodero, Gabriella</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open source technologies for visually impaired people</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Technologies for Visually .pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">241 - 246</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We describe two open source applications which we have experienced as very useful aids for the integration of people suffering from visual impairments, from hypovision to actual blindness. The first application is based on speech synthesis and has been experienced by disabled university students. The second experience is oriented to schoolchildren with low residual vision, and it provides their educators and parents with easy to use tools for image manipulation, especially designed for exploiting
residual visual abilities.
</style></abstract><section><style face="normal" font="default" size="100%">22</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Taibi, Davide</style></author><author><style face="normal" font="default" size="100%">Lavazza, Luigi</style></author><author><style face="normal" font="default" size="100%">Morasca, Sandro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OpenBQR: a framework for the assessment of OSS</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OpenBQR.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">173 - 186</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">People and organizations that are considering the adoption of OSS, or that need to choose among different OS products face the problem of evaluating OSS in a systematic, sound and complete way. While several proposals concerning the evaluation of costs and benefits exist, little attention has been given to the evaluation of technical qualities and, in general, to the “usage-oriented” issues. In this paper the existing proposals are examined, the different types of qualities and issues that are relevant to potential users are described, and a coherent and innovative method for the evaluation of OSS is proposed. The proposed method is expected to support the potential user in the evaluation and choice of OSS in a flexible way, taking into account all the aspects that are relevant to the user.
</style></abstract><section><style face="normal" font="default" size="100%">14</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ozel, Bulent</style></author><author><style face="normal" font="default" size="100%">Jovanovic, Uros</style></author><author><style face="normal" font="default" size="100%">Oba, Beyza</style></author><author><style face="normal" font="default" size="100%">van Leeuwen, Manon</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Perceptions on F/OSS Adoption</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Perceptions on F OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">319 - 324</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper aims to reveal results of a survey run by the tOSSad1 project. The majority of survey variables devised to capture perception of public administrators around Europe regarding the importance they attach to the factors such as F/OSS product quality, availability of support, expertise and documentation, TCO, vendor lock-in, political influence, administrative attitudes, productivity, and training costs, all of which intermingle with financial, technical, legal, and personal issues. The analysis consist of depiction of respondents’ administration profile in terms of their F/OSS usage and adoption, descriptive summary and analyses of factors mentioned above, and statistical inferential analyses of survey items. Some valid statistical tests are conducted to understand, to discuss and to see the extend and significance of any F/OSS adoption generalizations for Europe based on the findings of this particular survey.
</style></abstract><section><style face="normal" font="default" size="100%">35</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Project Entity Matching across FLOSS Repositories</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Project Entity Matching.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">45 - 57</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Much of the data about free, libre, and open source (FLOSS) software development comes from studies of code repositories used for managing projects. This paper presents a method for integrating data about open source projects by way of matching projects (entities) and deleting duplicates across multiple code repositories. After a review of the relevant literature, a few of the methods are chosen and applied to the FLOSS domain, including a simple scoring system for confidence in pairwise project matches. Finally, the paper describes limitations of this approach and recommendations for future work.
</style></abstract><section><style face="normal" font="default" size="100%">4</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hausen, Hans-Ludwig</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality Specification, Testing and Certification of Bespoken, Open Source and Commercial Off-The-Shelf Systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Quality Specification Testing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">365 - 366</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The seminar will cover the principles as well as the best practices of software system quality assurance (comprising inspection, verification, validation, black and white box test, measurement and assessment, and the normative quality characteristics) for procedural, object-oriented, aspectoriented and agent-based dependable software. Attendees will exercise proven techniques for goal-directed quality specification, testing, measurement, scaling and assessment for software certification. Assessment of both the software product as well as the software process will be discussed with respect to its relevance for such acceptance assessments. A standardized process model for measurement, assessment and certification of dependable software will be used to make the attendees familiar with this comprehensive assessment procedure and to learn how to embed it into today’s standardized or non-standardized software processes.
</style></abstract><section><style face="normal" font="default" size="100%">46</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author><author><style face="normal" font="default" size="100%">Hunt, Francis</style></author><author><style face="normal" font="default" size="100%">Probert, David</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Release Management in Free Software Projects: Practices and Problems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Release Management in Free Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">295 - 300</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users. This paper explores release practices employed by volunteer free software projects and shows problems that occur. A challenge that has been identified is the difficulty of coordinating a distributed team of volunteers in order to align their work for a release.
</style></abstract><section><style face="normal" font="default" size="100%">31</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Akkanen, Jyrki</style></author><author><style face="normal" font="default" size="100%">Demeter, Hunor</style></author><author><style face="normal" font="default" size="100%">Eppel, Tamás</style></author><author><style face="normal" font="default" size="100%">Ivánfi, Zoltán</style></author><author><style face="normal" font="default" size="100%">Nurminen, Jukka</style></author><author><style face="normal" font="default" size="100%">Stenman, Petri</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reusing an open source application — practical experiences with a mobile CRM pilot</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Reusing an Open Source Application.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">217 - 222</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We discuss experiences in extending an open source CRM application to develop a new server-based mobile business application. Combining the application code reuse with incremental development process allowed successful development of a pilot application in a tight schedule. In particular, it enabled a quick start for customer-driven development, diminished risks related to the baseline application itself, and provided the flexibility needed in experimental pilot development.
</style></abstract><section><style face="normal" font="default" size="100%">18</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Antikainen, Maria</style></author><author><style face="normal" font="default" size="100%">Aaltonen, Timo</style></author><author><style face="normal" font="default" size="100%">Väisänen, Jaani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The role of trust in OSS communities — Case Linux Kernel community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Role of Trust in OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">223 - 228</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software development has been the subject of interest among businesses as well as in the academic world. OSS enables many possibilities for companies but also sets new kinds of challenges. Because of the characteristics of the OSS phenomenon we propose that trust in OSS communities plays a key role in facilitating their success. Therefore, the aim of this study is to explore the factors that affect trust in OSS communities. The data is gathered by a survey aimed to Linux Kernel developers. Among other results it may be concluded that the most important factors affecting trust seem to be other developers’ skills, reputation as well as the formal and informal practices.
</style></abstract><section><style face="normal" font="default" size="100%">19</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Juho Lindman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Shared Assumption Concerning Technical Determination in Apache Web Server Developer Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Shared Assumption Concering.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">283 - 288</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Our main finding is that OSS community seems to coordinate its activities by relying on technical determination. First, we review previous literature to understand OSS community coordination mechanisms. Then we empirically review OSS Apache Web Server community by using qualitative case study methods. Our data consist of developer list’s email-discussions. Finally, we speculate that coordination rests on community’s members’ shared assumption concerning technical determination.
</style></abstract><section><style face="normal" font="default" size="100%">29</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sigfridsson, Anders</style></author><author><style face="normal" font="default" size="100%">Avram, Gabriela</style></author><author><style face="normal" font="default" size="100%">Sheehan, Anne</style></author><author><style face="normal" font="default" size="100%">Sullivan, Daniel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Sprint-driven development: working, learning and the process of enculturation in the PyPy community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Spring-driven development.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">133 - 146</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we examine sprint-driven software development as it occurs in a specific Open Source community, PyPy. Applying a situated learning perspective, we report the findings from a study focused on the activities leading up to, taking place during, and following after sprints. The study included analyses of sprint reports, email archives and other documents available on the community website, as well as a one-week period of direct observation of a specific sprint. The objective of the study was to elaborate on how the practices of sprint-driven development in the PyPy community facilitate learning, the dissemination of knowledge among its members and the expansion of the Open Source community. This paper aims to assess how sprint-driven development can facilitate situated learning in distributed software development by describing the practices applied in PyPy.
</style></abstract><section><style face="normal" font="default" size="100%">11</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Skidmore, Darren</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Stakeholder value, usage, needs and obligations from differnet types of F/LOSS licenses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Skakteholder value usage.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">343 - 348</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper discusses different types of Stakeholders of F/LOSS, their needs, the value, usage, and obligations that stakeholders have for different types of F/LOSS licenses. Stakeholders include Developers: Individuals, Projects, Embedded Systems. Vendors: Dominant, Niche, F/LOSS. Packagers. End Users. Organisations: Disseminators, Internally, Externally Used.
</style></abstract><section><style face="normal" font="default" size="100%">39</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hauge, Øyvind</style></author><author><style face="normal" font="default" size="100%">Sørensen, Carl-Fredrik</style></author><author><style face="normal" font="default" size="100%">Røsdal, Andreas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Surveying Industrial Roles in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Surveying Industrial Roles.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">259 - 264</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Industry uses Open Source Software (OSS) to a greater and greater extent. We have defined four industrial OSS roles; OSS provider, OSS integrator, OSS participant and Inner Source Software (ISS) participant. Based on these four roles we have performed a survey in the ITEA COSI project. We provide initial answers to what motivates companies to undertake these roles, what are the advantages and challenges of undertaking them, and which development practices they use while undertaking these roles.
</style></abstract><section><style face="normal" font="default" size="100%">25</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dalle, Jean</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Toward a New Industrial Organization? OSS in Economic and Managerial Perspective</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Toward a new indusctial Org.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">377 - 379</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">At present, an more and more users are running Open Source software (OSS) on their systems. Major companies, like IBM, Oracle, or Sun Microsystems, have now started to make significant investments in developing open communities and creating a portfolio of systems incorporating OSS applications into their design. Meanwhile, an increasing number of firms are entering the market by offering OSS-based solutions to their customers, often supplying a mix of proprietary and open solutions through hybrid business models. In this context, economists and management scientists are now moving beyond the state of puzzlement that has driven much of the initial attention towards OSS. Located in the context of OSS2007 in order to foster close and fruitful interactions with scholars from various other disciplines, this workshop aims at contributing to the current evolutions of the economic and managerial research agendas about OSS, and thus to provide, first, an assessment of where we — economics and management scholars - are about OSS, and, second, an analysis of the renewed directions in which we should consider inquiring further in the near future, focusing notably on business, production, diffusion and innovation models.
</style></abstract><section><style face="normal" font="default" size="100%">50</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Krivoruchko, Jacob</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Use of Open Source Software in Enterprise Distributed Computing Environments</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Use of OSS in Enterprise.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">277 - 282</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Firms increasingly rely on open source software for solving business problems and building mission-critical IT solutions. However, there are numerous issues associated with OSS, including its influence on the total cost of ownership (TCO) and supportability and upgradeability risks. While savings from obtaining a free copy of the software can be significant, software accounts for an average of 10% of TCO, while the majority of the costs are associated with project staffing. OSS requires significant investment into staffing because it needs to be carefully selected, customized, and installed. In addition, global communities may gather and dissolve at their will, so guarantees of support, revision, and bug fixes are minimal. Yet companies can gain competitive advantage through an ability to customize software to address specific business issues and exercising control over development, revision schedules, and modifications. OSS is not a panacea from the rising software costs. Instead, it is a serious initiative that has benefits, disadvantages, and risks associated with it.
</style></abstract><section><style face="normal" font="default" size="100%">28</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman</style></author><author><style face="normal" font="default" size="100%">Lefteris Angelis</style></author><author><style face="normal" font="default" size="100%">Stamelos, I.</style></author><author><style face="normal" font="default" size="100%">Y. Manolopoulos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Repository of Repositories (RoRs) to Study the Growth of F/OSS Projects: A Meta-Analysis Research Approach</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Using Repository of Repositories.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">147 - 160</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free/Open Source Software (F/OSS) repositories contain valuable data and their usefulness in studying software development and community activities continues to attract a lot of research attention. A trend in F/OSS studies is the use of metadata stored in a repository of repositories or RoRs. This paper utilizes data obtained from such RoRs -FLOSSmole- to study the types of projects being developed by the F/OSS community. We downloaded projects by topics data in five areas (Database, Internet, Software Development, Communications, and Games/Entertainment) from Flossmole’s raw and summary data of the sourceforge repository. Time series analysis show the numbers of projects in the five topics are growing linearly. Further analysis supports our hypothesis that F/OSS development is moving “up the stack” from developer tools and infrastructure support to end-user applications such as Databases. The findings have implications for the interpretation of the F/OSS landscape, the utilization and adoption of open source databases, and problems researchers might face in obtaining and using data from RoRs.
</style></abstract><section><style face="normal" font="default" size="100%">12</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Samoladas, Ioannis</style></author><author><style face="normal" font="default" size="100%">Bibi, Stamatia</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Deligiannis, Ignatios</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Preliminary Analysis of Publicly Available FLOSS Measurements: Towards Discovering Maintainability Trends</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">decision tree</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">machine learning</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">sourcekibitzer</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Samolades2007.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">The spread of free/libre/open source software (FLOSS) and the openness of its development model oﬀer researchers a valuable source of information regarding software data. The creation of large portals, which host a vast amount of FLOSS projects make it easy to create large datasets with valuable information regarding the FLOSS development process. In addition initiatives such as FLOSSMole provide researchers with a single point and continuing access to those data. Up to now the majority of datasets from FLOSSMole oﬀered data regarding the development process and not the code itself. From February 2007 FLOSSMole oﬀers data donated 
by SourceKibitzer, which contain source code metrics for FLOSS projects written in Java. In this paper we provide 
a premilinary analysis on those data using machine learning techniques, such as classiﬁcation rules and decision trees. Using the ﬁrst available data from February 2007, we tried to build rules that can be used in order to estimate the future values of metrics oﬀered for March. Here we present some preliminary results that are encouraging and deserve to be further analyzed in future releases of SourceKibitzer datasets. </style></abstract><notes><style face="normal" font="default" size="100%">used SourceKibitzer data downloaded from FLOSSmole</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">MacLean, Alexander C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Studying Production Phase SourceForge Projects: An Exploratory Analysis Using cvs2mysql and SFRA</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Data Collection</style></keyword><keyword><style  face="normal" font="default" size="100%">forge</style></keyword><keyword><style  face="normal" font="default" size="100%">repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Delorey2007c.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">A wealth of data can be extracted from the natural by-products of software development processes and used in empirical studies of software engineering. However, the size and accuracy of such studies depend in large part on the availability of tools that facilitate the collection of data from individual projects and the combination of data from multiple projects. To demonstrate this point, we present our experience gathering and analyzing data from nearly 10,000 open source projects hosted on SourceForge. We describe the tools we developed to collect the data and the ways in which these tools and data may be used by other researchers. We also provide examples of statistics that we have calculated from these data to describe interesting author- and project-level behaviors of the SourceForge community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wasserman, Anthony</style></author><author><style face="normal" font="default" size="100%">Ashutosh Das</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using FLOSSmole Data in Determining Business Readiness Ratings</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WopDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">brr</style></keyword><keyword><style  face="normal" font="default" size="100%">business readiness rating</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Using FLOSSmole Data in Determining Business Readiness Ratings.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">This paper is a preliminary report on using FLOSSmole data retrieved from open source repositories (forges) to calculate Business Readiness Rating scores.  </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Masmoudi, Héla</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Working with Open Source Development Data: Considerations triggered by a study of bug scenarios</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bug scenarios</style></keyword><keyword><style  face="normal" font="default" size="100%">Data Collection</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2007</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/denBesten-wopdasd.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">The retrieval and preparation of public data on software development calls for more than just technical skills. In 
addition, care and judgement are needed to avoid disproportionate costs to the providers of data or unnecessary embarrassment to the participants tracked in the data. Taking the extraction of bug scenarios as a use case, we illustrate these concerns and discuss how they could be translated into social requirements that would help to make retrieval and preparation a sustainable exercise. In particular, we call for more efforts to establish institutional repositories of public data on software development and, besides, we suggest that reviewers could play a role in making sure that empirical research is performed in a way that does not bring the long-term relationship between software developers and researchers in jeopardy. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Seeking Open Infrastructure: Contrasting Open Standards, Open Source and Open Innovation</style></title><secondary-title><style face="normal" font="default" size="100%">First Monday</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2007</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">12</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><issue><style face="normal" font="default" size="100%">6</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Livieri, Simone</style></author><author><style face="normal" font="default" size="100%">Higo, Yoshiki</style></author><author><style face="normal" font="default" size="100%">Matsushita, Makoto</style></author><author><style face="normal" font="default" size="100%">Inoue, Katsuro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysis of the Linux Kernel Evolution Using Code Clone Coverage</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">ccfinder</style></keyword><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">cloning</style></keyword><keyword><style  face="normal" font="default" size="100%">kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300022.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">22 - 22</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Most studies of the evolution of software systems are based on the comparison of simple software metrics. In this paper, we present our preliminary investigation of the evolution of the Linux kernel using code-clone analysis and the code-clone coverage metrics. We examined 136 versions of the stable Linux kernel using a distributed extension of the code clone detection tool CCFinder. The result is shown as a heat map.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kagdi, Huzefa</style></author><author><style face="normal" font="default" size="100%">Collard, Michael L.</style></author><author><style face="normal" font="default" size="100%">Maletic, Jonathan I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Comparing Approaches to Mining Source Code for Call-Usage Patterns</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">function calls</style></keyword><keyword><style  face="normal" font="default" size="100%">functions</style></keyword><keyword><style  face="normal" font="default" size="100%">kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">sequence</style></keyword><keyword><style  face="normal" font="default" size="100%">sequencing</style></keyword><keyword><style  face="normal" font="default" size="100%">sequential-pattern mining</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300020.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">20 - 20</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Baysal, Olga</style></author><author><style face="normal" font="default" size="100%">Malton, Andrew J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Correlating Social Interactions to Release History during Software Evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">ant</style></keyword><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">discussion</style></keyword><keyword><style  face="normal" font="default" size="100%">effort estimation</style></keyword><keyword><style  face="normal" font="default" size="100%">lsedit</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300007.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">7 - 7</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kidane, Yared</style></author><author><style face="normal" font="default" size="100%">Gloor, Peter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Correlating temporal communication patterns of the Eclipse open source community with performance and creativity</style></title><secondary-title><style face="normal" font="default" size="100%">Computational &amp;amp; Mathematical Organization Theory</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">communication</style></keyword><keyword><style  face="normal" font="default" size="100%">creativity</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">feature requests</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">performance</style></keyword><keyword><style  face="normal" font="default" size="100%">productivity</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1007/s10588-006-9006-3</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer Netherlands</style></publisher><volume><style face="normal" font="default" size="100%">13</style></volume><pages><style face="normal" font="default" size="100%">17-27</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Social network data was collected from the Eclipse component development groups’ 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).&quot;
&quot;The study is based on data from the three main projects of the Eclipse open source development community, namely “eclipse”, “tools” and “technology”. We have chosen thirty-three different component development groups for analysis.&quot;
&quot;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’ mailing list archives to compile a list of the possible URL links. It then extracts communication data as tuples in the form of “sender, receiver, communication type, timestamp, communication contents” and stores it in the database. Further, bugs and enhancement data were collected from the Eclipse bugzilla database.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Gourley, Alex</style></author><author><style face="normal" font="default" size="100%">Devanbu, Prem</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Detecting Patch Submission and Acceptance in OSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">patches</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300026.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">26 - 26</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Anvik, John</style></author><author><style face="normal" font="default" size="100%">Murphy, Gail C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Determining Implementation Expertise from Bug Reports</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">repository</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300002.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">2 - 2</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">As developers work on a software product they accumulate expertise, including expertise about the code base of the software product. We call this type of expertise &quot;implementation expertise&quot;. Knowing the set of developers who have implementation expertise for a software product has many important uses. This paper presents an empirical evaluation of two approaches to determining implementation expertise from the data in source and bug repositories. The expertise sets created by the approaches are compared to those provided by experts and evaluated using the measures of precision and recall. We found that both approaches are good at finding all of the appropriate developers, although they vary in how many false positives are returned.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lozano, Angela</style></author><author><style face="normal" font="default" size="100%">Wermelinger, Michel</style></author><author><style face="normal" font="default" size="100%">Nuseibeh, Bashar</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating the Harmfulness of Cloning: A Change Based Experiment</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">ccfinder</style></keyword><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">clones</style></keyword><keyword><style  face="normal" font="default" size="100%">clonetracker</style></keyword><keyword><style  face="normal" font="default" size="100%">cloning</style></keyword><keyword><style  face="normal" font="default" size="100%">ctags</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">dnsjava</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">18 - 18</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Cloning is considered a harmful practice for software maintenance because it requires consistent changes of the entities that share a cloned fragment. However this claim has not been refuted or confirmed empirically. Therefore, we have developed a prototype tool, CloneTracker, in order to study the rate of change of applications containing clones. This paper describes CloneTracker and illustrates its preliminary application on a case study.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, Claudio</style></author><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">FOCSE: An OWA-based Evaluation Framework for OS Adoption in Critical Environments</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FOCSE  an  OWA.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">234/2007</style></volume><pages><style face="normal" font="default" size="100%">3-16</style></pages><abstract><style face="normal" font="default" size="100%">While the vast majority of European and US companies increasingly use open source software for non-key applications, a much smaller number of companies have deployed it in critical areas such as security and access control. This is partly due to residual difficulties in performing and documenting the selection process of open source solutions. In this paper we describe the FOCSE metrics framework, supporting a specific selection process for security-related open source code. FOCSE is based on a set of general purpose metrics suitable for evaluating open source frameworks in general; however, it includes some specific metrics expressing security solutions’ capability of responding to continuous change in threats. We show FOCSE at work in two use cases about selecting two different types of security-related open source solutions, i.e. Single Sign-On and Secure Shell applications.
 </style></abstract><section><style face="normal" font="default" size="100%">1</style></section></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Forecasting the Number of Changes in Eclipse Using Time Series Analysis</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300032.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">32 - 32</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">In order to predict the number of changes in the following months for the project Eclipse, we have applied a statistical (non-explanatory) model based on time series analysis. We have obtained the monthly number of changes in the CVS repository of Eclipse, using the CVSAnalY tool. The input to our model was the filtered series of the number of changes per month, and the output was the number of changes per month for the next three months. Then we aggregated the results of the three months to obtain the total number of changes in the given period in the challenge.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Didier Demazière</style></author><author><style face="normal" font="default" size="100%">Francois Horn</style></author><author><style face="normal" font="default" size="100%">Marc Zune</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The functioning of a free software community: entanglement of three regulation modes - control, autonomous, and distributed</style></title><secondary-title><style face="normal" font="default" size="100%">Science Studies</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Science_Studies_02-2007-Demaziere_Horn_Zune.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper consider FLOSS communities as &quot;&quot;going concerns&quot;&quot; which necessitate a minimum of order and common, shared, social rules to function. Through an in-depth and diachronic analysis of the Spip project, we present two classical modes of social regulation: a control regulation centred on the product and an autonomous regulation reflecting the differentiated commitments. Our data shows that the meaning, value and legitimacy of contributors' involvements are defined and rated more collectively, through exchanges, judgments, and evaluations. A third regulation mode, called distributed community regulation and aimed at creating and transforming shared rules that produces recognition and stratification, is then presented.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiss, Cathrin</style></author><author><style face="normal" font="default" size="100%">Premraj, Rahul</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Zeller, Andreas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Long Will It Take to Fix This Bug?</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">effort estimation</style></keyword><keyword><style  face="normal" font="default" size="100%">jboss</style></keyword><keyword><style  face="normal" font="default" size="100%">lucene</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">time</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300001.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Predicting the time and effort for a software problem has long been a difficult task. We present an approach that automatically predicts the fixing effort, i.e., the person-hours spent on fixing an issue. Our technique leverages existing issue tracking systems: given a new issue report, we use the Lucene framework to search for similar, earlier reports and use their average time as a prediction. Our approach thus allows for early effort estimation, helping in assigning issues and scheduling stable releases. We evaluated our approach using effort data from the JBoss project. Given a sufficient number of issues reports, our automatic predictions are close to the actual effort; for issues that are bugs, we are off by only one hour, beating naive predictions by a factor of four.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Canfora, Gerardo</style></author><author><style face="normal" font="default" size="100%">Cerulo, Luigi</style></author><author><style face="normal" font="default" size="100%">Di Penta, Massimiliano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying Changed Source Code Lines from Version Repositories</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">levenshtein</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300014.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">14 - 14</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Observing the evolution of software systems at different levels of granularity has been a key issue for a number of studies, aiming at predicting defects or at studying certain phenomena, such as the presence of clones or of crosscutting concerns. Versioning systems such as CVS and SVN, however, only provide information about lines added or deleted by a contributor: any change is shown as a sequence of additions and deletions. This provides an erroneous estimate of the amount of code changed.

This paper shows how the evolution of changes at source code line level can be inferred from CVS repositories, by combining information retrieval techniques and the Levenshtein edit distance. The application of the proposed approach to the ArgoUML case study indicates a high precision and recall.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Impact of the Creation of the Mozilla Foundation in the Activity of Developers</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">revision history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300028.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">28 - 28</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">During 2003, the Mozilla project transitioned from company-promoted (sponsored by AOL) to community-promoted (sponsored by the Mozilla Foundation). What happened to the group of developers during this transition? There was any significant impact on its activity or composition? To answer these questions, we have performed an analysis of the CVS repository of Mozilla, using the CVSAnalY tool, finding little on activity, but dramatic changes in the the composition of the development team.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joshi, Hemant</style></author><author><style face="normal" font="default" size="100%">Zhang, Chuanlei</style></author><author><style face="normal" font="default" size="100%">Ramaswamy, S.</style></author><author><style face="normal" font="default" size="100%">Bayrak, Coskun</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Local and Global Recency Weighting Approach to Bug Prediction</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300033.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">33 - 33</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Finding and fixing software bugs is a challenging maintenance task, and a significant amount of effort is invested by software development companies on this issue. In this paper, we use the Eclipse project's recorded software bug history to predict occurrence of future bugs. The history contains information on when bugs have been reported and subsequently fixed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu, Liguo</style></author><author><style face="normal" font="default" size="100%">Ramaswamy, Srini</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining CVS Repositories to Understand Open-Source Project Developer Roles</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developer interaction</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">mediawiki</style></keyword><keyword><style  face="normal" font="default" size="100%">orac-dr</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300008.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">8 - 8</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">This paper presents a model to represent the interactions of distributed open-source software developers and utilizes data mining techniques to derive developer roles. The model is then applied on case studies of two open-source projects, ORAC-DR and Mediawiki with encouraging results.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Linstead, Erik</style></author><author><style face="normal" font="default" size="100%">Rigor, Paul</style></author><author><style face="normal" font="default" size="100%">Bajracharya, Sushil</style></author><author><style face="normal" font="default" size="100%">Lopes, Cristina</style></author><author><style face="normal" font="default" size="100%">Baldi, Pierre</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining Eclipse Developer Contributions via Author-Topic Models</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">topics</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300030.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">30 - 30</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">We present the results of applying statistical author-topic models to a subset of the Eclipse 3.0 source code consisting of 2,119 source files and 700,000 lines of code from 59 developers. This technique provides an intuitive and automated framework with which to mine developer contributions and competencies from a given code base while simultaneously extracting software function in the form of topics. In addition to serving as a convenient summary for program function and developer activities, our study shows that topic models provide a meaningful, effective, and statistical basis for developer similarity analysis.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kiefer, Christoph</style></author><author><style face="normal" font="default" size="100%">Bernstein, Abraham</style></author><author><style face="normal" font="default" size="100%">Tappolet, Jonas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining Software Repositories with iSPAROL and a Software Evolution Ontology</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">database</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">evoont</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">owl</style></keyword><keyword><style  face="normal" font="default" size="100%">semantic</style></keyword><keyword><style  face="normal" font="default" size="100%">sparql</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300010.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">10 - 10</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">One of the most important decisions researchers face when analyzing the evolution of software systems is the choice of a proper data analysis/exchange format. Most existing formats have to be processed with special programs written specifically for that purpose and are not easily extendible. Most scientists, therefore, use their own database(s) requiring each of them to repeat the work of writing the import/export programs to their format.

We present EvoOnt, a software repository data exchange format based on the Web Ontology Language (OWL). EvoOnt includes software, release, and bug-related information. Since OWL describes the semantics of the data, EvoOnt is (1) easily extendible, (2) comes with many existing tools, and (3) allows to derive assertions through its inherent Description Logic reasoning capabilities.

The paper also shows iSPARQL -- our SPARQL-based Semantic Web query engine containing similarity joins. Together with EvoOnt, iSPARQL can accomplish a sizable number of tasks sought in software repository mining projects, such as an assessment of the amount of change between versions or the detection of bad code smells. To illustrate the usefulness of EvoOnt (and iSPARQL), we perform a series of experiments with a real-world Java project. These show that a number of software analyses can be reduced to simple iSPARQL queries on an EvoOnt dataset.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining Workspace Updates in CVS</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">gcc</style></keyword><keyword><style  face="normal" font="default" size="100%">jboss</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">workspaces</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300011.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">11 - 11</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">The version control archive CVS records not only all changes in a project but also activity data such as when developers create or update their workspaces. Furthermore, CVS records when it has to integrate changes because of parallel development. In this paper, we analyze the CVS activity data of four large open-source projects GCC, JBOSS, JEDIT, and PYTHON to investigate parallel development: What is the degree of parallel development? How frequently do conflicts occur during updates and how are they resolved? How do we identify changes that contain integrations?</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Gourley, Alex</style></author><author><style face="normal" font="default" size="100%">Devanbu, Prem</style></author><author><style face="normal" font="default" size="100%">Swaminathan, Anand</style></author><author><style face="normal" font="default" size="100%">Hsu, Greta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Borders? Immigration in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">joining</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300006.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">6 - 6</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the &quot;who, how and when&quot; of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fershtman, Chaim</style></author><author><style face="normal" font="default" size="100%">Gandal, Neil</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open source software: Motivation and restrictive licensing</style></title><secondary-title><style face="normal" font="default" size="100%">International Economics and Economic Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">incentives</style></keyword><keyword><style  face="normal" font="default" size="100%">license analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">licenses</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">restrictive</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">status</style></keyword><keyword><style  face="normal" font="default" size="100%">version history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1007/s10368-007-0086-4</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer Berlin / Heidelberg</style></publisher><volume><style face="normal" font="default" size="100%">4</style></volume><pages><style face="normal" font="default" size="100%">209-225</style></pages><abstract><style face="normal" font="default" size="100%">Open source software (OSS) is an economic paradox. Development of open source software is often done by unpaid volunteers and the source code is typically freely available. Surveys suggest that status, signaling, and intrinsic motivations play an important role in inducing developers to invest effort. Contribution to an OSS project is rewarded by adding one’s name to the list of contributors which is publicly observable. Such incentives imply that programmers may have little incentive to contribute beyond the threshold level required for being listed as a contributor. Using a unique data set we empirically examine this hypothesis. We find that the output per contributor in open source projects is much higher when licenses are less restrictive and more commercially oriented. These results indeed suggest a status, signaling, or intrinsic motivation for participation in OSS projects with restrictive licenses.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We employ a unique data set consisting of 71 open source projects hosted at the SourceForge web site. The 71 projects in the sample were chosen (in January 2000)&quot;
&quot;This sample was observed over an 18-month period from January 2002 through the middle of 2003, with data collected at 2-month intervals.&quot;
&quot;We are grateful to NERA for providing us with the data.&quot;
&quot;Although we only have data on a relatively small sample of the projects hosted SourceForge, the sample is unique because of data on lines of code as well as data on different versions of the program. The latter is a potentially important control variable, since a change in version may necessitate additional lines of code.
Our data set contains information on the size of the open source projects in the form of source lines of code (SLOC). Using SLOC as a performance measure is not always ideal; nevertheless, this performance measure is employed in the profession and the literature.15 For our purposes, SLOC is in fact an ideal measure, because we want to measure the effort that is put into the project, rather than whether a project succeeds.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mahmoud Refaat Nasr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software: The use of open source</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/OpenSourceGIS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI's ArcIMS, Intergraph's GeoMedia WebMap, and MapInfo's MapXtreme.

The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jones, M.C.</style></author><author><style face="normal" font="default" size="100%">Floyd, I.R.</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Patchworks of Open-Source Software: High-Fidelity Low-cost Prototypes. </style></title><secondary-title><style face="normal" font="default" size="100%">The Handbook of Research on Open Source Software. </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">Idea Group, Inc.</style></publisher><pages><style face="normal" font="default" size="100%">126-140.</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schroter, Adrian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Predicting Defects and Changes with Import Relations</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">defects</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">effort estimation</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300031.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">31 - 31</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Lowering the number of defects and estimating the development time of a software project are two important goals of software engineering. To predict the number of defects and changes we train models with import relations. This enables us to decrease the number of defects by more efficient testing and to assess the effort needed in respect to the number of changes.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Panjer, Lucas D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Predicting Eclipse Bug Lifetimes</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">effort estimation</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">weka</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300029.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">29 - 29</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">In non-trivial software development projects planning and allocation of resources is an important and difficult task. Estimation of work time to fix a bug is commonly used to support this process. This research explores the viability of using data mining tools to predict the time to fix a bug given only the basic information known at the beginning of a bug's lifetime. To address this question, a historical portion of the Eclipse Bugzilla database is used for modeling and predicting bug lifetimes. A bug history transformation process is described and several data mining models are built and tested. Interesting behaviours derived from the models are documented. The models can correctly predict up to 34.9% of the bugs into a discretized log scaled lifetime class.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Ernst, Michael D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Prioritizing Warning Categories by Analyzing Software History</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">columba</style></keyword><keyword><style  face="normal" font="default" size="100%">findbugs</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword><keyword><style  face="normal" font="default" size="100%">jlint</style></keyword><keyword><style  face="normal" font="default" size="100%">kenyon</style></keyword><keyword><style  face="normal" font="default" size="100%">pmd</style></keyword><keyword><style  face="normal" font="default" size="100%">warning</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300027.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">27 - 27</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Automatic bug finding tools tend to have high false positive rates: most warnings do not indicate real bugs. Usually bug finding tools prioritize each warning category. For example, the priority of &quot;overflow&quot; is 1 and the priority of &quot;jumbled incremental&quot; is 3, but the tools' prioritization is not very effective.

In this paper, we prioritize warning categories by analyzing the software change history. The underlying intuition is that if warnings from a category are resolved quickly by developers, the warnings in the category are important. Experiments with three bug finding tools (FindBugs, JLint, and PMD) and two open source projects (Columba and jEdit) indicate that different warning categories have very different lifetimes. Based on that observation, we propose a preliminary algorithm for warning category prioritizing.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Delorey, Daniel P.</style></author><author><style face="normal" font="default" size="100%">Knutson, Charles D.</style></author><author><style face="normal" font="default" size="100%">Giraud-Carrier, C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Programming Language Trends in Open Source Development: An Evaluation Using Data from All Production Phase SourceForge Projects</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs2mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">programming languages</style></keyword><keyword><style  face="normal" font="default" size="100%">sfra</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Delorey2007b.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">In this work, we analyze data collected from the CVS repos- itories of 9,997 Open Source projects hosted on SourceForge in an effort to understand trends in programming language usage in the Open Source community between 2000 and 2005. The trends we consider include: 1) the relative popularity of the ten most popular programming languages over time, 2) the use of multiple programming languages by individual programmers and by individual projects, and 3) the programming languages most often used in combination.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Our data were gathered from the SourceForge Research Ar- chive (SFRA) [4] and the CVS repositories Open Source projects hosted on SourceForge. We used cvs2mysql and SFRA+ to collect the data. cvs2mysql gathers data from CVS repositories and writes them to SQL scripts for im- port into a MySQL 5.0 database. The data collected by cvs2mysql are the name of the file, the location of the file in the repository, the type and state of the file, as well as the author, date, number of lines added and removed, and the author’s message for each revision to the file.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Minto, Shawn</style></author><author><style face="normal" font="default" size="100%">Murphy, Gail C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Recommending Emergent Teams</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300005.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">5 - 5</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration, specialized tools, such as chat and screen sharing, are being integrated into development environments. Currently, these tools require a developer to maintain a list of other developers with whom they may wish to communicate and to determine who within this list has expertise for a specific situation. For large, dynamic projects, like several successful open-source projects, these requirements place an unreasonable burden on the developer. In this paper, we show how the structure of a team emerges from how developers change software artifacts. We introduce the Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We found that EEL produces, on average, results with higher precision and higher recall than an existing heuristic for expertise recommendation.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hindle, Abram</style></author><author><style face="normal" font="default" size="100%">Godfrey, Michael W.</style></author><author><style face="normal" font="default" size="100%">Holt, Richard C.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Release Pattern Discovery via Partitioning: Methodology and Case Study</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bitkeeper</style></keyword><keyword><style  face="normal" font="default" size="100%">bt2csv</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mysql</style></keyword><keyword><style  face="normal" font="default" size="100%">releases</style></keyword><keyword><style  face="normal" font="default" size="100%">revision history</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">softchange</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300019.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">19 - 19</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">The development of Open Source systems produces a variety of software artifacts such as source code, version control records, bug reports, and email discussions. Since the development is distributed across different tool environments and developer practices, any analysis of project behavior must be inferred from whatever common artifacts happen to be available. In this paper, we propose an approach to characterizing a project's behavior around the time of major and minor releases; we do this by partitioning the observed activities, such as artifact check-ins, around the dates of major and minor releases, and then look for recognizable patterns. We validate this approach by means of a case study on the MySQL database system; in this case study, we found patterns which suggested MySQL was behaving consistently within itself. These patterns included testing and documenting that took place more before a release than after and that the rate of source code changes dipped around release time.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Kangning Wei</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Self-organization of teams for free/libre open source software development</style></title><secondary-title><style face="normal" font="default" size="100%">Information and Software Technology Journal</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">compiere</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">DESIGN</style></keyword><keyword><style  face="normal" font="default" size="100%">distributed teams</style></keyword><keyword><style  face="normal" font="default" size="100%">egroupware</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">forum</style></keyword><keyword><style  face="normal" font="default" size="100%">free/libre open source software development</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">INTERNET</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">qualitative research methods</style></keyword><keyword><style  face="normal" font="default" size="100%">self-organizing teams</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">SYSTEMS</style></keyword><keyword><style  face="normal" font="default" size="100%">task assignment</style></keyword><keyword><style  face="normal" font="default" size="100%">WORK</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">564-575</style></number><volume><style face="normal" font="default" size="100%">49</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that &quot;self-assignment&quot; was the most common mechanism across three FLOSS projects. This 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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members&quot;...&quot;projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback&quot;
&quot;3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP.&quot;

all had sourceforge hosting

Data: &quot;The primary data used for our study were interactions on the main developer communication forum, either a developer mailing list or web-based discussion forum.&quot;

Analysis: &quot;For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Antoniades, Ionannis </style></author><author><style face="normal" font="default" size="100%">Kontoyiannis</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Deligiannis, Ignatios</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Simulation of the temporal evolution of OSS projects: application to XMMS and MPLAYER</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mizuno, Osamu</style></author><author><style face="normal" font="default" size="100%">Ikami, Shiro</style></author><author><style face="normal" font="default" size="100%">Nakaichi, Shuya</style></author><author><style face="normal" font="default" size="100%">Kikuno, Tohru</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Spam Filter Based Approach for Finding Fault-Prone Software Modules</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">classification</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">modules</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">spam</style></keyword><keyword><style  face="normal" font="default" size="100%">text mining</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300004.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">4 - 4</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Because of the increase of needs for spam e-mail detection, the spam filtering technique has been improved as a convenient and effective technique for text mining. We propose a novel approach to detect fault-prone modules in a way that the source code modules are considered as text files and are applied to the spam filter directly. In order to show the applicability of our approach, we conducted experimental applications using source code repositories of Java based open source developments. The result of experiments shows that our approach can classify more than 75% of software modules correctly.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rysselberghe, Filip Van</style></author><author><style face="normal" font="default" size="100%">Demeyer, Serge</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Studying Versioning Information to Understand Inheritance Hierarchy Changes</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">inheritance</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300016.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">16 - 16</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">With the widespread adoption of object-oriented programming, changing the inheritance hierarchy became an inherent part of today's software maintenance activities. Unfortunately, little is known about the &quot;state-of-the-practice&quot; with respect to changing an application's inheritance hierarchy, and consequently we do not know how the change process can be improved. In this paper, we report on a study of the hierarchy changes stored in a versioning system to explore the answers to three research questions: (1) why are hierarchy changes made? (2) what kind of hierarchy changes are made? (3) what is the impact of these changes? Based on the results of this study, we formulate 7 hypotheses which should be investigated further to make conclusive interpretations on how hierarchy changes fit in the actual change process.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Herraiz, Israel</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a Theoretical Model for Software Growth</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">C</style></keyword><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">growth</style></keyword><keyword><style  face="normal" font="default" size="100%">halstead</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">mccabe</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword><keyword><style  face="normal" font="default" size="100%">sloccount</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300021.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">21 - 21</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Software growth (and more broadly, software evolution) is usually considered in terms of size or complexity of source code. However in different studies, usually different metrics are used, which make it difficult to compare approaches and results. In addition, not all metrics are equally easy to calculate for a given source code, which leads to the question of which one is the easiest to calculate without losing too much information. To address both issues, in this paper present a comprehensive study, based on the analysis of about 700,000 C source code files, calculating several size and complexity metrics for all of them. For this sample, we have found double Pareto statistical distributions for all metrics considered, and a high correlation between any two of them. This would imply that any model addressing software growth should produce this Pareto distributions, and that analysis based on any of the considered metrics should show a similar pattern, provided the sample of files considered is large enough.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mary Darking</style></author><author><style face="normal" font="default" size="100%">Edgar A Whitley</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards an understanding of FLOSS: Infrastructures, Materiality and the Digital Business Ecosystem</style></title><secondary-title><style face="normal" font="default" size="100%">Science Studies</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">engagement</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">infrastructures</style></keyword><keyword><style  face="normal" font="default" size="100%">INNOVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">materiality</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Darking_Whitley.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we present empirical work detailing the engagement practices of a large FLOSS project, the Digital Business Ecosystem (DBE). In common with many other FLOSS projects, the DBE project focused on the development of infrastructural software components. Infrastructures and FLOSS software exhibit multiplicity: as objects they both change and stay the same. Whilst the implications of multiplicity with respect to infrastructure have been well-documented, with respect to FLOSS, they remain under-explored. Through examining how the DBE engaged new participants we were able to explore the nature of the FLOSS software object by asking the implied question: engagement with what? We draw on recent analysis by Law and Singleton to show how the innovative yet non-existent potentiality of the DBE was as significant to engagement as its steadily growing codebase. We argue that acknowledging the materiality and immateriality of the FLOSS software object has important consequences for management of, and engagement with, FLOSS projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Studer, Matthias</style></author><author><style face="normal" font="default" size="100%">Müller, Benoît</style></author><author><style face="normal" font="default" size="100%">Ritschard, Gilbert</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding the KDE Social Structure through Mining of Email Archive</style></title><secondary-title><style face="normal" font="default" size="100%">2nd Workshop on Public Data about Software Development (WoPDaSD 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug tracking system</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">commit</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">participation</style></keyword><keyword><style  face="normal" font="default" size="100%">revision control</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/wopdasd_studer_et_all_full.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">In order to achieve a better understanding of FLOSS social structure, we need a definition of social position. From a theoretical perspective, we propose to think the participation as a trajectory. Empirically, we use optimal matching to build a typology of participation trajectories based on KDE email archives. We show how these trajectories structure the community as a whole by combining these results with a social network analysis.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Our data source is constituted by e-mails sent to KDE mailing-lists and archived by MARC&quot;

&quot;Two problems quickly arise: neither the e-mails addresses nor the names can be considered unique. Consequently, we used an in-depth search algorithm to put together “name-email” couples corresponding to a same contributor. Indeed, the algorithm suggests possible merges.&quot;

&quot;There is a specific mailing list in our data set, kde-commit, which gathers automatic notifications from the revision control system (RCS)....We measure “commit” by the number of messages sent to the “kde-commit” mailing list. However, we did not count “silent” commits, nor usual messages sent to this mailing list.&quot;

&quot;We measured activities done in BTS in two ways: “bug opener” and “non bug opener”.	First, we counted the number of modifications done by the contributor who opened the concerned bug report. &quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Software Distributions to Understand the Relationship among Free and Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">dependencies</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">fink</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300024.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">24 - 24</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Success in the open source software world has been measured in terms of metrics such as number of downloads, number of commits, number of lines of code, number of participants, etc. These metrics tend to discriminate towards applications that are small and tend to evolve slowly. A problem is, however, how to identify applications in these latter categories that are important. Software distributions specify the dependencies needed to build and to run a given software application. We use this information to create a dependency graph of the applications contained in such a distribution. We explore the characteristics of this graph, and use it to define some metrics to quantify the dependencies (and dependents) of a given software application. We demonstrate that some applications that are invisible to the final user (such as libraries) are widely used by end-user applications. This graph can be used as a proxy to measure success of small, slowly evolving free and open source software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Valetto, Giuseppe</style></author><author><style face="normal" font="default" size="100%">Helander, Mary</style></author><author><style face="normal" font="default" size="100%">Ehrlich, Kate</style></author><author><style face="normal" font="default" size="100%">Chulani, Sunita</style></author><author><style face="normal" font="default" size="100%">Wegman, Mark</style></author><author><style face="normal" font="default" size="100%">Williams, Clay</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Software Repositories to Investigate Socio-technical Congruence in Development Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">graph</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300025.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">25 - 25</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">We propose a quantitative measure of socio-technical congruence as an indicator of the performance of an organization in carrying out a software development project. We show how the information necessary to implement that measure can be mined from commonly used software repositories, and we describe how socio-technical congruence can be computed based on that information.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weissgerber, Peter</style></author><author><style face="normal" font="default" size="100%">Pohl, Mathias</style></author><author><style face="normal" font="default" size="100%">Burch, Michael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Visual Data Mining in Software Archives to Detect How Developers Work Together</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">junit</style></keyword><keyword><style  face="normal" font="default" size="100%">modules</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">svn</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword><keyword><style  face="normal" font="default" size="100%">tomcat</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300009.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">9 - 9</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Analyzing the check-in information of open source software projects which use a version control system such as CVS or SUBVERSION can yield interesting and important insights into the programming behavior of developers. As in every major project tasks are assigned to many developers, the development must be coordinated between these programmers.

This paper describes three visualization techniques that help to examine how programmers work together, e.g. if they work as a team or if they develop their part of the software separate from each other. Furthermore, phases of stagnation in the lifetime of a project can be uncovered and thus, possible problems are revealed.

To demonstrate the usefulness of these visualization techniques we performed case studies on two open source projects. In these studies interesting patterns of developers? behavior, e.g. the specialization on a certain module can be observed. Moreover, modules that have been changed by many developers can be identified as well as such ones that have been altered by only one programmer.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Floyd, I.R.</style></author><author><style face="normal" font="default" size="100%">Jones, M.C.</style></author><author><style face="normal" font="default" size="100%">Rathi, D.</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Web Mash-ups and Patchwork Prototyping: User-driven technological innovation with Web 2.0 and Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07)2007 40th Annual Hawaii International Conference on System Sciences (HICSS'07)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikoloa, HI, USA</style></pub-location><pages><style face="normal" font="default" size="100%">86 - 86</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2755-8</style></isbn><abstract><style face="normal" font="default" size="100%">The recent emergence of web mash-ups and open
source software is driving the development of new
practices in software and systems development. In this
paper we explore novel practices of user-driven
innovation through an examination of several case
studies which illustrate how users and developers are
exploiting the proliferation of open APIs and open
source systems. Developers can rapidly create proofs
of concept that are robust enough for actual use by
combining preexisting software components. The
underlying programming processes involved make use
of tried-and-true software development techniques,
and may not appear innovative at first. However, the
application of these practices and techniques to
problem solving by non-programmers shows a high
degree of creative innovation, giving rise to new ways
of thinking about technology design and production.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Peter C. Rigby</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List</style></title><secondary-title><style face="normal" font="default" size="100%">Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">joining</style></keyword><keyword><style  face="normal" font="default" size="100%">liwc</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">personality</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/28300023.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Minneapolis, MN, USA</style></pub-location><pages><style face="normal" font="default" size="100%">23 - 23</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2950-X</style></isbn><abstract><style face="normal" font="default" size="100%">Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Reid Priedhorsky</style></author><author><style face="normal" font="default" size="100%">Jilin Chen</style></author><author><style face="normal" font="default" size="100%">Shyong K. Lam</style></author><author><style face="normal" font="default" size="100%">Katherine Panciera</style></author><author><style face="normal" font="default" size="100%">Loren Terveen</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Creating, Destroying, and Restoring Value in Wikipedia</style></title><secondary-title><style face="normal" font="default" size="100%">Conference on Supporting Group Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Xiang Liu</style></author><author><style face="normal" font="default" size="100%">Bala Iyer</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Design architecture, developer networks and performance of open source software projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">NotreDameArchive</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Open Source Software Development: Recent Research Results and Emerging Opportunities</style></title><secondary-title><style face="normal" font="default" size="100%">Proc. European Software Engineering Conference and ACM SIGSOFT Symposium on the Foundations of Software Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Dubrovnik, Croatia</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Zelkowitz, M.V.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Open Source Software Development: Recent Research Results and Methods</style></title><secondary-title><style face="normal" font="default" size="100%"> Advances in Computers</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><volume><style face="normal" font="default" size="100%">69</style></volume><pages><style face="normal" font="default" size="100%">243-295</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><orig-pub><style face="normal" font="default" size="100%">May 4, 2007</style></orig-pub></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stefano Comino</style></author><author><style face="normal" font="default" size="100%">Fabio M. Manenti</style></author><author><style face="normal" font="default" size="100%">Parisi, M. L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From planning to mature: On the success of open source projects</style></title><secondary-title><style face="normal" font="default" size="100%">Research Policy</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><volume><style face="normal" font="default" size="100%">36</style></volume><pages><style face="normal" font="default" size="100%">1575-1586</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source is an example of user-centric innovation initiated by an individual or group of users to satisfy their specific needs; the more a software evolves towards a stable release able to address the requirements of its developers, the more successful the project. In this paper we use a large data-set obtained from SourceForge.net to estimate the relationship between a series of different characteristics of OS projects and the probability of evolution of the source code from a preliminary release to a mature version. We show that while projects distributed under highly restrictive licensing terms (GPL) have a significantly smaller probability of reaching a stable release, applications towards sophisticated users have a larger probability of evolving in the development status. Interestingly, we find that the size of the &quot;community of developers&quot; increases the chances of progress but this effect decreases as the community gets larger, a signal of possible coordination problems. (C) 2007 Elsevier B.V. All rights reserved.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000251834700007</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes><custom1><style face="normal" font="default" size="100%">Policy</style></custom1><custom2><style face="normal" font="default" size="100%">case study?</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christley, S.</style></author><author><style face="normal" font="default" size="100%">Madey, G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Global and Temporal Analysis of Social Positions at SourceForge. net</style></title><secondary-title><style face="normal" font="default" size="100%">Third International Conference on Open Source Systems, IFIP WG</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><volume><style face="normal" font="default" size="100%">2</style></volume><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">English, R.</style></author><author><style face="normal" font="default" size="100%">Schweik, C. M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying Success and Tragedy of FLOSS Commons: A Preliminary Classification of Sourceforge. net Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Emerging Trends in FLOSS Research and Development, 2007. FLOSS'07. First International Workshop on</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><pages><style face="normal" font="default" size="100%">11-11</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jing Wu</style></author><author><style face="normal" font="default" size="100%">Khim-Yong Goh</style></author><author><style face="normal" font="default" size="100%">Qian Tang</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Investigating success of open source software projects: A social network perspective</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">CollectedOwnData NoShare</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Param Vir Singh</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open source software development and the small world phenomenon: an empirical investigations of macro level colaboration network properties on project success</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">NotreDameArchive</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sinan Aral</style></author><author><style face="normal" font="default" size="100%">Erik Brynjolfsson</style></author><author><style face="normal" font="default" size="100%">Marshall Van Alstyne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Productivity effects of information diffusion in email networks</style></title><secondary-title><style face="normal" font="default" size="100%">Twenty Eighth International Conference on Information Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><pub-location><style face="normal" font="default" size="100%">Montréal, PQ, Canada</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Shilad Sen</style></author><author><style face="normal" font="default" size="100%">Harper, F. Maxwell</style></author><author><style face="normal" font="default" size="100%">Adam LaPitz</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Quest for Quality Tags.</style></title><secondary-title><style face="normal" font="default" size="100%">Conference on Supporting Group Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dan Frankowski</style></author><author><style face="normal" font="default" size="100%">Shyong K. Lam</style></author><author><style face="normal" font="default" size="100%">Shilad Sen</style></author><author><style face="normal" font="default" size="100%">Harper, F. Maxwell</style></author><author><style face="normal" font="default" size="100%">Scott Yilek</style></author><author><style face="normal" font="default" size="100%">Michael Cassano</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Recommenders Everywhere: The WikiLens Community-Maintained Recommender System</style></title><secondary-title><style face="normal" font="default" size="100%">Wikisym 2007</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><pub-location><style face="normal" font="default" size="100%">Montreal, Quebec, Canada</style></pub-location><isbn><style face="normal" font="default" size="100%">978-1-59593-861-9</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Chengetai Masango</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The role of face-to-face meetings in technology-supported self-organizing distributed teams</style></title><secondary-title><style face="normal" font="default" size="100%">Ieee Transactions on Professional Communication</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">50</style></volume><pages><style face="normal" font="default" size="100%">185-203</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed (or virtual teams), specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, and we point out the activities performed in these settings and the benefits obtained. Contrary to conventional wisdom about distributed teams, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit offace-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000249308800001</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes><custom1><style face="normal" font="default" size="100%">communication?</style></custom1><custom2><style face="normal" font="default" size="100%">grounded theory</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yong Tan</style></author><author><style face="normal" font="default" size="100%">Vijay Mookerjee</style></author><author><style face="normal" font="default" size="100%">Param Vir Singh</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social capital, structural holes and team composition: collaborative networks of the open source software community</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">NotreDameArchive</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>27</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Antoniades, Ionannis </style></author><author><style face="normal" font="default" size="100%">Samoladas, Ioannis</style></author><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author><author><style face="normal" font="default" size="100%">Fraczek, Ksenia</style></author><author><style face="normal" font="default" size="100%">Hadzisalihovic, Anis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Study of Available Tools </style></title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://flossmetrics.org/sections/deliverables/docs/deliverables/WP1/D1.1- Study_of_Available_Tools.pdf</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">FLOSSmetrics</style></publisher><isbn><style face="normal" font="default" size="100%">D1.1</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><work-type><style face="normal" font="default" size="100%">EU Framework deliverable</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Sowe, S.K.</style></author><author><style face="normal" font="default" size="100%">Stamelos, I.</style></author><author><style face="normal" font="default" size="100%">Samoladas, I</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding the Development of Free E-Commerce/E-Business Software: A Resource-Based View</style></title><secondary-title><style face="normal" font="default" size="100%">Emerging Free and Open Source Software Practices</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">IGI Publishing</style></publisher><pub-location><style face="normal" font="default" size="100%">Hershey, PA</style></pub-location><pages><style face="normal" font="default" size="100%">170-190</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><orig-pub><style face="normal" font="default" size="100%">May 30, 2007</style></orig-pub></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Value Capture and Value Networks in Open Source Vendor Strategies</style></title><secondary-title><style face="normal" font="default" size="100%">40th Annual Hawaii International Conference on System Sciences (HICSS'07)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Waikoloa, HI, USA</style></pub-location><pages><style face="normal" font="default" size="100%">176 - 176</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2755-8</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nicolas Schudel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Commons Identity: A Conceptual Model for Designing Brand Identity in Free and Open Source Software Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/commons_identity.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ed Sherwood-Smith</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source &amp; The Irish Software Industry?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/ReducedSizeThesis.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The open source software movement is a global phenomenon that is having a significant impact on the global software industry. It is changing the way in which software companies and people view the software development process. It is changing the way in which software companies capture value. It is commoditizing segments of the software market and is creating new business models and new ways of capturing value. It is lauded by some and vilified by others. It is often painted in a biblical light ??? David taking on Goliath. Yet, many of the Goliaths??? are also benefiting from this movement. This dissertation explores this - How can companies manage the impacts of the open source software movement to their advantage? This research examines the phenomenon in the context of the Irish Industry. Through a review of the existing literature this dissertation develops and exploratory framework for investigating different factors that might be influential in looking at how Indigenous Irish Software firms might manage the impacts of open source software movement. It weaves facets of different research areas together to produce this framework. The framework is then tested using several techniques including a qualitative survey. The dissertation includes several sections that apply the framework in order to analyze and develop profiles of several different firms. These profiles are then used to look at some of the different strategies and tactics available to firms. In many cases, examples are drawn from the global software industry to illustrate these approaches. The research concludes that there are factors that influence how a firm can manage the impact of the open source movement. It also builds on the initial framework to offer a more complete approach to understanding the factors that change the way in which firms manage the impacts of the open source software movement.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">PJ Wall</style></author><author><style face="normal" font="default" size="100%">Seamas Kelly</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Bringing Open Source Software to the Desktop : An In-Depth Study of the Implementation and use of Star Office</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Sept</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Bringing_OSS_to_the_Desktop.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source software is coming to the attention of individuals, organisations, and governments worldwide, and is increasingly being adopted by firms for specific business purposes. However, the uptake of end-user desktop OSS applications to date has been modest, and Microsoft products remain the de-facto standard on the corporate desktop. This brings into sharp focus one of the most challenging questions faced by the Open Source community today ... namely, if organisations value low acquisition costs, low total cost of ownership of software, potentially plentiful support, free access to source code, and the wish to avoid proprietary software vendor lock-in, why have more organisations not adopted OSS?  This paper contributes to the existing research by reporting on an in-depth, interpretive, processual study of an attempt by a large Irish Trade Union to replace Microsoft Office with an Open Source alternative, StarOffice.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Linus Dahlander</style></author><author><style face="normal" font="default" size="100%">Martin W. Wallin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A man on the inside: Unlocking communities as complementary assets</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dahlanderwallin.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Since Teece's seminal paper explaining who were the gainers from technological innovation, increased globalization and the information and communication technology revolution have brought newways for firms to organize and appropriate from innovation. A new more open model of innovation suggests that firms can benefit from sources of innovation that stem from outside the firm. The central theme of this paper is how firms try to unlock communities as complementary assets. These communities exist outside firm boundaries beyond ownership or hierarchical control. Because of practices developed by communities to protect their work, firms need to assign individuals to work in these communities in order to gain access to developments and, to an extent, influence the direction of the community. Using network analysis we show that some software firms sponsor individuals to act strategically within a free and open source software (FOSS) community. Firm sponsored individuals interact with more individuals than interact with them, and also they seek to interact with central individuals in the community. However, we can see differences in how individuals interact, depending on whether their affiliation is with a dedicated FOSS firm or an incumbent in the software industry. Apparently, some firm managers believe they need ???a man on the inside??? to be able to gain access to communities. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Nora Misiolek</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A structurational perspective on leadership in technology-supported self-organizing small groups</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CrowstonHeckmanMisiolek.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Syracuse University School of Information Studies</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this conceptual paper, we present a structuration-based theory of leadership behaviours in virtual teams, that is to say, in self-organizing technology-supported small groups such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on behavioural leadership theory and structuration theory, we present a two-order theory of leadership. It describes four classes of first-order leadership behaviours (task coordination, substantive task contribution, group maintenance, and boundary spanning) and defines second-order leadership as behaviour that influences changes in the structure that guides group action. Specifically, we suggest that second-order leadership behaviours are those that build structures of signification in the form of interpretive schema, structures of domination in the form of role structures and structures of legitimation in the form of rules and norms. We argue that second-order leadership is enabled by first-order leadership, is therefore action embedded, and is grounded in processes that define the social identity of the group. We propose that effective teams will exhibit a paradoxical combination of shared, distributed first-order leadership complemented by strong, concentrated, and centralized second-order leadership. We conclude by suggesting future research that might be conducted to test and further elaborate our theory.</style></abstract><work-type><style face="normal" font="default" size="100%">Working Paper</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jamil Alkhatib</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free Open Source as a Technology Transfer Tool in the Arab World</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Khatib_FOS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Arab world has so far minimum contribution to the current global innovation system. Technology transfer is a major factor behind such weakness. Within the context of the Arab world, the Free Open Source (FOS)process could be adopted as a cheap and fast alternative tool for technology transfer. This study will focus on the effectiveness of FOS process on the Technology Transfer and how it will improve the cooperation between research and industrial institutes working in the ICT sector in the Arab world.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cataldo, Marcelo</style></author><author><style face="normal" font="default" size="100%">Wagstrom, Patrick A.</style></author><author><style face="normal" font="default" size="100%">Herbsleb, J. D.</style></author><author><style face="normal" font="default" size="100%">Carley, Kathleen M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identification of coordination requirements: Implications for the design of collaboration and awareness tools</style></title><secondary-title><style face="normal" font="default" size="100%">Conference on Computer Support Collaborative Work</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">modularity</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Banff, Alberta, Canada</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">inproceedings</style></custom3><label><style face="normal" font="default" size="100%">cataldo2006identification</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sverre Helge Bolstad</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Learning and knowledge in FLOSS - Situated learning and organizational knowledge-conversion in community-based free/libre open source software development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Learning-and-knowledge-in-FLOSS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In free/libre open source software development (FLOSS), groups of developers and users working in geographically dispersed settings are supported by a dense network of interactions. The participants are highly skilled in the use of information- and communication technologies, and build the software by relying on extensive peer production and through skillful use of communication tools available on the Internet. In building the software, explicit, formal and structured knowledge in the form of documents, objects, machines and external sources are communicated and stored in ways that make it available for others in the present and future. This knowledge make up an important resource for the members and developers of the community. Another kind, or aspect, of knowledge, often called tacit or soft knowledge, is informal, unstructured, resides in people, and are difficult, or maybe impossible, to articulate. The questions guiding this research is how knowledge, both explicit and tacit, is shared, and how a new member is able take part in the practice and knowledge of the community. The theory of legitimate peripheral participation in communities of practice describes an environment for people to develop knowledge through interaction with others in an environment where knowledge is created, nurtured and sustained. By taking part in the practice as a participant observer, through virtual ethnography, the author describes the practice and communication in this decentralized and knowledge-intensive process. Taking it a step further, the knowledge of the community, and how it is shared within the ???organization???, is explored with a model for managing dynamic aspects of organizational knowledge-creation. The central theme here is that knowledge is created through a continuous dialogue between tacit and explicit knowledge. Logs from Internet Relay Chat (IRC) and interviews with core developers are analyzed, and the author argues that the Plone community is able to share both kinds of knowledge in a complex web of resources and interaction. The analysis further suggest that the FLOSS development-model facilitates access, transparency and participation on premisses that are important for learning.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Feller, Joseph</style></author><author><style face="normal" font="default" size="100%">Fitzgerald, Brian</style></author><author><style face="normal" font="default" size="100%">Hissam, Scott</style></author><author><style face="normal" font="default" size="100%">Lakhani, Karim</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding Free/Open Source Software Development Processes</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process--Improvement and Practice</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March/April</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">11</style></volume><pages><style face="normal" font="default" size="100%">95-105</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu, Liguo</style></author><author><style face="normal" font="default" size="100%">Schach, Stephen R.</style></author><author><style face="normal" font="default" size="100%">Chen, Kai</style></author><author><style face="normal" font="default" size="100%">Heller, Gillian Z.</style></author><author><style face="normal" font="default" size="100%">Offutt, Jeff</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD</style></title><secondary-title><style face="normal" font="default" size="100%">J. Syst. Softw.</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">abiword</style></keyword><keyword><style  face="normal" font="default" size="100%">Common coupling</style></keyword><keyword><style  face="normal" font="default" size="100%">coupling</style></keyword><keyword><style  face="normal" font="default" size="100%">Definition-use analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">linux kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">Maintainability</style></keyword><keyword><style  face="normal" font="default" size="100%">modules</style></keyword><keyword><style  face="normal" font="default" size="100%">netbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">Open-source software</style></keyword><keyword><style  face="normal" font="default" size="100%">openbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1016/j.jss.2005.08.014</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/YuSchachChen.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Elsevier Science Inc.</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><volume><style face="normal" font="default" size="100%">79</style></volume><pages><style face="normal" font="default" size="100%">807–815</style></pages><abstract><style face="normal" font="default" size="100%">We compared and contrasted the maintainability of four open-source operating systems: Linux, FreeBSD, NetBSD, and OpenBSD. We used our categorization of common coupling in kernel-based software to highlight future maintenance problems. An unsafe definition is a definition of a global variable that can affect a kernel module if that definition is changed. For each operating system we determined a number of measures, including the number of global variables, the number of instances of global variables in the kernel and overall, as well as the number of unsafe definitions in the kernel and overall. We also computed the value of each our measures per kernel KLOC and per KLOC overall. For every measure and every ratio, Linux compared unfavorably with FreeBSD, NetBSD, and OpenBSD. Accordingly, we are concerned about the future maintainability of Linux. </style></abstract><notes><style face="normal" font="default" size="100%">&quot;Data regarding the number and total number of lines of code of kernel and nonkernel modules in the four operating systems are provided in Table 1&quot;
loc, kloc, number of kernel modules, number of nonkernel modules
size 
c files
.h files</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Grewal, Rajdeep</style></author><author><style face="normal" font="default" size="100%">Lilien, Gary L.</style></author><author><style face="normal" font="default" size="100%">Mallapragada, Girish</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Location, Location, Location: How Network Embeddedness Affects Project Success in Open Source Systems</style></title><secondary-title><style face="normal" font="default" size="100%">Management Science</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">affiliation network</style></keyword><keyword><style  face="normal" font="default" size="100%">age</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">latent class analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">network embeddedness</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">page views</style></keyword><keyword><style  face="normal" font="default" size="100%">perl</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">registration</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://portal.acm.org/citation.cfm?id=1246148.1246155</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">7</style></number><publisher><style face="normal" font="default" size="100%">INFORMS</style></publisher><pub-location><style face="normal" font="default" size="100%">Institute for Operations Research and the Management Sciences (INFORMS), Linthicum, Maryland, USA</style></pub-location><volume><style face="normal" font="default" size="100%">52</style></volume><pages><style face="normal" font="default" size="100%">1043–1056</style></pages><abstract><style face="normal" font="default" size="100%">The community-based model for software development in open source environments is becoming a viable alternative to traditional firm-based models. To better understand the workings of open source environments, we examine the effects of network embeddedness---or the nature of the relationship among projects and developers---on the success of open source projects. We find that considerable heterogeneity exists in the network embeddedness of open source projects and project managers. We use a visual representation of the affiliation network of projects and developers as well as a formal statistical analysis to demonstrate this heterogeneity and to investigate how these structures differ across projects and project managers. Our main results surround the effect of this differential network embeddedness on project success. We find that network embeddedness has strong and significant effects on both technical and commercial success, but that those effects are quite complex. We use latent class regression analysis to show that multiple regimes exist and that some of the effects of network embeddedness are positive under some regimes and negative under others. We use project age and number of page views to provide insights into the direction of the effect of network embeddedness on project success. Our findings show that different aspects of network embeddedness have powerful but subtle effects on project success and suggest that this is a rich environment for further study.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Paola Giuri</style></author><author><style face="normal" font="default" size="100%">Matteo Ploner</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author><author><style face="normal" font="default" size="100%">Salvatore Torrisi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Skills, Division of Labor and Performance in Collective Inventions. Evidence from the Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/giuriplonerrullanitorrisi.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper investigates the role of skills and the division of labor among participants in collective inventions. Our analysis draws on a large sample of projects registered at Sourceforge.net, the world's largest incubator of open source software activity. We test the hypothesis that the level of skills of participants and their skill variety are important for project performance. Skill heterogeneity across participants is in line with two fundamental organizational features of the open source development model: team work and modular design. We also explore the hypothesis whether the level of modularization of project activities is an important predictor of performance. Our econometric estimations show that both skill level and skill heterogeneity positively affect projects' survival and performances. However, the impact of skill diversity is non linear. Design modularity is also positively associated with the performance of the project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Didier Demazière</style></author><author><style face="normal" font="default" size="100%">Francois Horn</style></author><author><style face="normal" font="default" size="100%">Nicolas Jullien</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How free software developers work. The mobilization of &quot;distant communities&quot;</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CLES_DDFHNJ_juin_2006__vm_Anglais.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The work of free software developers is an individual activity carried out in extremely heterogeneous conditions and a collective action with original production methods. We propose to analyze this work starting with the paradoxical notion of a &quot;distant community&quot;, that aims to illustrate the tension between, on the one hand, the strength of the sense of belonging to a specific world identifiable in the discourse of the participants and, on the other hand, the distances that separate the contributors in terms of relationships, status, and background. In doing this the aim is to produce a description, necessarily plural, of the different forms of &quot;distant communities&quot; that enables the production of goods in unique social and organizational conditions. More generally speaking, this notion points to methods of coordination that combine two forms of collective action that are usually contrary and antagonistic: a communitarian form based on the subjective feeling of belonging to the same community and a form of partnership based on the coordination of common interests and sharing of objectives (T??nnies, 1887, Weber, 1921). At first, we examine the ways the individual participants organize themselves in order to contribute to a project and we focus on the forms of cooperation and coordination used to deal with the constraints of efficiency and quality associated with the distribution of a product. Secondly, we look at the other side of the coin and examine the ways individual participants take action and we underline the mechanisms of commitment and participation that account for their contribution to the production of free software. These two dimensions, that in our opinion are inseparable, are explored through a survey carried out with free software developers.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Peter C. Rigby</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A preliminary examination of code review processes in open source projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Rigby2006TR.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we provide preliminary answers to the following questions regarding OSS peer review or inspection. What is the patch process and review process used by the projects? What types of review does a the project use? Why are patches rejected? What percentage of patches are rejected? Who performs the review? Are the top developers also the top reviewers? When are reviews performed? What is the frequency of review? How long do reviews take to perform? How does the patch size affect the review? How does merit-based trust among actors affect the review? Are more trusted individuals reviewed less often? How much feedback is provided in the review? What kinds of non-source code patches are reviewed? How does the kind of patch affect the review? What affect does reviewing have on other elements of the patch process? What is the relationship between reviewing and testing? The first two questions are answered in a qualitative manner for GCC, Linux, Mozilla, and Apache. The remaining questions are answered for the Apache project. The most striking similarities among projects is there use of a pre-commit review and requests for small, complete, independent patches. The Apache project also uses a post-commit review of trusted members. Reviews in the Apache project occur very frequently and usually have a review interval of hours. A small core group of reviewers conduct over 80% of reviews for Apache; however, the number of and actual individuals fluctuates over the 9 years of data we examine.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Greg R Vetter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Exit &amp; Voice in Free &amp; Open Source Software Licensing:  Moderating the Rein over Software Users</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Vetter.Exit_.and_.Voice_.in_.FOSS_.Licensing85.Oregon.L.Rev_.183.(2006).pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This article analyzes the interplay between exit and voice for user adoption of Free and Open Source Software (FOSS), as these two are conceptualized in Albert O. Hirschman's book Exit, Voice, and Loyalty:  Responses to Decline in Firms, Organizations and States.  Exit and voice cooperatively sustain FOSS through the institutional mechanism of the FOSS license.  Four situations demonstrate this.  First, even with attendant uncertainties in its novel legal landscape, users adopt FOSS to escape proprietary licensed software.  This exit is tinged with indirect voice.  Second, this indirect voice arises from collaborative projects to develop FOSS.  The very same code and license that provides the exit carries the voice.  Third, complementing exit by users are technologists who contribute, extracurricularly, to open source projects, signaling their affiliation with FOSS.  Fourth, from its beginning, the FOSS movement has expressed its voice.  Its norm entrepreneurs use rhetoric and persuasion to reinforce FOSS's disciplining effect on an entire industry.  These four situations highlight exit and voice combinations for copyright based open source licensing and patent law.  The FOSS copyright based licensing scheme helps channel FOSS into uses where exit and voice are concentrated and synergistically reinforce.  The interplay with patent law generates voice because patent law, at least theoretically, inhibits exit to FOSS and thus pressurizes the voice mechanism in Hirschman's framework.  Understanding FOSS based combinations of exit and voice in light of this framework helps participants and policy makers formulate legal, licensing and policy strategies to guide the movement and respond to its evolution.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Param Vir Singh</style></author><author><style face="normal" font="default" size="100%">Nara Youn</style></author><author><style face="normal" font="default" size="100%">Yong Tan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Developer Learning Dynamics in Open Source Software Projects: A Hidden Markov Model Analysis</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">December</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/singh-youn-tan.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This work proposes a dynamic model of developer learning in open source software (OSS) projects. A Hidden Markov Model (HMM) is proposed to explain how the code contribution behaviors of OSS de-velopers change as their levels of knowledge on their projects increase. In this model, discrete hidden states represent the unobserved knowledge levels of developers, and their observed code contribution be-haviors are modeled as state dependent. Developers??? knowledge levels evolve as they learn about the pro-jects over time. Two modes of learning are considered: learning-by-doing (code development) and learn-ing through interactions with peers. The model is calibrated using data spanning six years for 25 OSS pro-jects and 251 developers hosted at Sourceforge. The proposed model identifies three knowledge states (high, medium, and low) and estimates the impact of the two modes of learning on the transition of devel-opers between the three knowledge states. The model results suggest that in the low knowledge state de-velopers exhibit the greatest inertia, followed by those in the medium and high states. Both modes of learning are found to have varying impact across the three knowledge states. Interactions with peers ap-pear to be an important source of learning for developers in all states. A developer in the low state learns only through participation in threads started by others. Prior code contribution and starting discussion by initiating threads do not impact the knowledge level of a developer in the low state. Initiating threads, par-ticipating in threads started by others, and prior code contributions have positive impacts on the knowl-edge level of a developer in the medium or high state and, hence, influence his long term code contribu-tion behavior. Explanations for these varying impacts of learning activities on the transitions of develop-ers between the three states are provided. We also find a lack of persistence of knowledge in all states. The HMM better describes the data than a latent class model which would suggests that the learning ac-tivities have a long term, dynamic impact, rather than an immediate, static impact on the code contribu-tion behavior of a developer.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lorenzo Benussi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The evolution of free/libre open source software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">December</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Benussi(2006)_The_evolution_of_FLOSS_1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Free Libre Open Source Software represents an outstanding example of ???open development model of technological knowledge???. It has been studied in several researches that produced valuable illustrations of the way it works. Our understanding of its principal features is growing exponentially and an entire new literature on open source has been created. However there appears to be an important gap in the literature: the origin of the phenomenon. The following chapter attempts to tackle this issue by analyzing the long-term technological history of the Free Open Source Software; the main research questions at stake are: ???Is the phenomenon completely new? and if it is not totally new, where does it come from???? and, more generally, ???how did open source software developed over time????. As a consequence the present work focuses primarily on the analysis of the free/open source software history of technological change over a period of almost sixty years. I adopted a multidisciplinary approach to analyse the network of relations emerging between inventions and technological innovations, as well as economic determinants and intellectual property rights regimes throughout the period considered. Therefore, I attempted to investigate the origins of the phenomenon as a way of understanding its evolution.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tere Vadén</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">'Intellectual Property' and Knowledge Creation in Disorganisations</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">December</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/14_Vaden_ELEA_3_3_web.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Given the current forms of economic production and corporate markets, the liberating and democratic potential of digital information is counteracted by the concentration of media ownership, as well as by policy, legislation, and the development of proprietary forms of technology. The notion of 'intellectual property' produces artificial scarcity where digital technology could remove it. This tension between the proprietary and non-proprietary aspects of the information society can be analysed by looking at two types of knowledge creation: organisational and disorganisational. While organisational knowledge work can benefit from a notion of 'intellectual property', disorganisational knowledge work is disrupted, if not destroyed, by proprietary barriers on information. This is unfortunate if and when the crucial innovations and ethical potential of the information society are connected to disorganisational communities, even though the organisational type is more visible and better represented in the traditional structures of society.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jyh-An Lee</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">New Perspectives on Public Goods Production: Policy Implications of Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">December</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/LeeOSS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This article reveals some empirical data regarding the trend of evolving open source software (OSS) policies globally. Additionally, this article investigates why so many governments are considering support of OSS development, and weighs the pros and cons of such policies. The ultimate conclusion is that when two systems are equally suitable, governments may reasonably choose OSS over proprietary software because software industry market failures may justify such support of OSS development. While governments considering supporting OSS are primarily concerned with significant switching costs and incompatibility problems, OSS is actually superior to proprietary software because it increases compatibility and consequently decreases switching costs in the long term. Further, OSS will not only help developing countries build their information technology capabilities, but will also promote competition in the software market.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kristijan Spirov</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free/Open Source Software And Business: Forming A Migration Policy</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dissertation_kspirov.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper explores the non-technical issues that arise with migration to Free/Libre and Open Source Software (FLOSS) in Large Scaled Enterprises (LSEs), with special emphasis on human and social issues. The result of the study is a conceptual framework for effective addressing of non-technical issues in a migration policy. The study is of exploratory nature and uses secondary research findings from multiple disciplines: free and open source software, management of human resources, power and conflict, system migration, information systems development, motivation, change management, organizational psychology and social informatics; including anecdotal evidence from FLOSS migrations in practice. A holistic approach has been used during the analysis of the migration issues, based on the key principles of social informatics that IT technology and social contexts are interdependent. The relationship between FLOSS migrations and different organizational contexts is elaborated and it has been found out how lack of vendor support for FLOSS motivates LSEs to improve their self-support of own IT infrastructures. In-depth analysis is performed of the individual and social impact that FLOSS migrations have on enterprise IT personnel, as well as how different individual factors such as age, gender, personal motivations and beliefs may impact on individual migration efforts. The social differences between typical enterprise IT personnel and the FLOSS community are elaborated, as well as how to overcome the communication gap between them. The role of end users in FLOSS migration and relevant issues are discussed. It is proved why staged migration is the most viable option and it is shown how it is related to human and social factors. At the end, a conceptual framework for description of non-technical FLOSS migration issues is discussed, which can be used as a helpful tool in a migration policy.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author><author><style face="normal" font="default" size="100%">Dedrick, Jason</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Scope and Timing of Deployment: Moderators of Organizational Adoption of the Linux Server Platform.</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of IT Standards Research</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">7/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">4</style></volume><pages><style face="normal" font="default" size="100%">1-23</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;&amp;nbsp;Market selection of product compatibility standards has long been explained through aggregate positive-feedback theoretical models of economic utility. Explaining aggregate patterns of organizational standards adoption requires two additional steps &amp;mdash; not only differences between organizations, but also differences within organizations.&lt;/p&gt;&lt;p&gt;Here we present a qualitative study of how organizations do (or do not) adopt a new computer server platform standard, namely Linux using PC-compatible hardware. While discussions of Linux typically focus on its open source origins, our respondents were primarily interested in low price. Despite this relative advantage in price, incumbent standards enjoyed other advantages identified by prior theory, namely network effects and switching costs.&lt;/p&gt;&lt;p&gt;We show when, how and why such incumbent advantages are overcome by a new standard. We find that Linux adoption within organizations began for uses with a comparatively limited scope of deployment, thus minimizing network effect and switching costs disadvantages. We identify four attributes of information systems that potentially limit the scope of deployment: few links of the system to organizational processes, special-purpose computer systems, new uses and replacement of obsolete systems. We also identify an organizational level variable &amp;mdash; internal standardization &amp;mdash; which increases scope of deployment and thus the attractiveness of the incumbent standard.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, B.</style></author><author><style face="normal" font="default" size="100%">Scotto, M.</style></author><author><style face="normal" font="default" size="100%">Sillitti, A.</style></author><author><style face="normal" font="default" size="100%">Succi, G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study on the Migration to OpenOffice.org in a Public Administration</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Information Technology and Web Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">33/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">64 - 80</style></pages><abstract><style face="normal" font="default" size="100%">The aim of the article is to report the results of a migration to Open Source Software (OSS) in one public administration. The migration focuses on the office automation field and, in particular, on the OpenOffice.org suite. We have analysed the transition to OSS considering qualitative and quantitative data collected with the aid of different tools. All the data have been always considered from the point of view of the different stakeholders involved, IT managers, IT technicians, and users. The results of the project have been largely satisfactory. However the results cannot be generalised due to some constraints, like the environment considered and the parallel use of the old solution. Nevertheless, we think that the data collected can be of valuable aid to managers wishing to evaluate a possible transition to OSS.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, Claudio Agostino</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author><author><style face="normal" font="default" size="100%">Gabriele Gianini</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source in Web-Based Applications</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Information Technology and Web Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">33/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">81 - 94</style></pages><abstract><style face="normal" font="default" size="100%">Business and recreational activities on the global communication infrastructure are increasingly based on the use of remote resources and services, and on the interaction between different, remotely located parties. In such a context, Single Sign-On technologies simplify the log-on process allowing automatic access to secondary domains through a unique log-on operation to the primary domain. In this article, we evaluate different Single Sign-On implementations focusing on the central role of Open Source in the development of Web-based systems. We outline requirements for Single Sign-On systems and evaluate four existing Open Source implementations in terms of degree of fulfilment of those requirements. Finally we compare those Open Source systems with respect to some specific Open Source community patterns.</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ludford, P.</style></author><author><style face="normal" font="default" size="100%">D. Frankowski</style></author><author><style face="normal" font="default" size="100%">Reily, K.</style></author><author><style face="normal" font="default" size="100%">Wilms, K.</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Because I Carry My Cell Phone Anyway: Functional Location-Based Reminder Applications</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">22/04/2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Montreal, Quebec, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">889-898</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-372-7</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sara Drenner</style></author><author><style face="normal" font="default" size="100%">Max Harper</style></author><author><style face="normal" font="default" size="100%">Dan Frankowski</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author><author><style face="normal" font="default" size="100%">Loren Terveen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Insert Movie Reference Here: A System to Bridge Conversation and Item-Oriented Web Sites</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">22/04/2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pages><style face="normal" font="default" size="100%">951-954</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-372-7</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Al Mamunur Rashid</style></author><author><style face="normal" font="default" size="100%">Kimberly Ling</style></author><author><style face="normal" font="default" size="100%">Regina D Tassone</style></author><author><style face="normal" font="default" size="100%">Paul Resnick</style></author><author><style face="normal" font="default" size="100%">Robert Kraut</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Motivating Participation by Displaying the Value of Contribution</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">22/04/2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Montreal, Quebec, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">955-958</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-372-7</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cosley, D.</style></author><author><style face="normal" font="default" size="100%">D. Frankowski</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Intelligent Task Routing and Contribution Review to Help Communities Build Artifacts of Lasting Value</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">22/04/2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Montreal, Quebec, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">1037-1046</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-372-7</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Roberts, Jeffrey</style></author><author><style face="normal" font="default" size="100%">Il-Horn Hann</style></author><author><style face="normal" font="default" size="100%">Sandra Slaughter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Communication Networks in an Open Source Software Project</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">participation</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Communication Networks in an Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">297 - 306</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Savonnet, Marinette</style></author><author><style face="normal" font="default" size="100%">Leclercq, Eric</style></author><author><style face="normal" font="default" size="100%">Terrasse, Marie-Noëlle</style></author><author><style face="normal" font="default" size="100%">Grison, Thierry</style></author><author><style face="normal" font="default" size="100%">Becker, George</style></author><author><style face="normal" font="default" size="100%">Farizy, Anne</style></author><author><style face="normal" font="default" size="100%">Denoyelle, Ludovic</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Development Platforms as a Niche for Software Companies in Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Development Platforms as a Niche.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">341 - 342</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Without Abstract</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Attilio, Fiandrotti</style></author><author><style face="normal" font="default" size="100%">Di Nunzio, Pierluigi</style></author><author><style face="normal" font="default" size="100%">Di Gregorio, Federico</style></author><author><style face="normal" font="default" size="100%">Meo, Angelo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A graphical installation system for the GNU/Linux Debian distribution</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A graphical installation system.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">337 - 338</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">One of the main objectives of the Centro di Competenza sul Software Libero del Politecnico di Torino is to provide custom GNU/Linux distribution to the Public Administration, small and medium enterprise and schools. Debian GNU/Linux was choosen as the base for the custom distributions because of its strong support of free software and its long-standing technical merits: minimalist hardware requirement, the best available packaging system, support for 13 different architectures and a strict set of quality guidelines adopted by all the active Debian developers. The only foreseeable limitation, the Debian default text-based installer, was overriden by restarting the development of the then-abandoned Debian graphical installer. Now the new graphical installer is developed by tens of people and it will be included in the next official Debian release.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Bonaccorsi</style></author><author><style face="normal" font="default" size="100%">Lucia Piscitello</style></author><author><style face="normal" font="default" size="100%">Monica Merito</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How is it possible to profit from innovation in the absence of any appropriability?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/How is it possible to profit.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">333 - 334</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) represents an “open innovation” paradigm based on knowledge produced and shared by developers and users. New findings from a large survey of European software companies show that: (i) the OSS business model is currently involving almost one third of the industry, although with different intensity; (ii) compared with pure proprietary software producers, OSS firms have a broader product portfolio and are more diversified; moreover, (iii) OSS firms provide more complementary services to their customers; (iv) over time OSS firms increase the share of OS turnover out of the total turnover, becoming more and more OSS oriented; (v) both NOSS and OSS firms do not consider appropriability as a crucial requirement for innovation and do not consider the lack of appropriability as an obstacle to profitability.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hahn, Jungpil</style></author><author><style face="normal" font="default" size="100%">Moon, Jae</style></author><author><style face="normal" font="default" size="100%">Zhang, Chen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Impact of Social Ties on Open Source Project Team Formation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Impact of Social Ties on Open Source Project.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">307 - 317</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we empirically examined the role of social ties in OSSD team formation and developer joining behavior. We find that the existence and the amount of prior social relations in the network do increase the probability of an OSS project to attract more developers. Interestingly, for projects without preexisting social ties, developers tend to join the project initiated by people with less OSSD experience. This research fills a gap in the open source literature by conducting an empirical investigation of the role of social relations on project team formation behavior. Furthermore, the adoption of social network analysis, which has received little attention in the OSS literature, can yield some interesting results on the interactions among OSS developers.
</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we randomly selected 1030 new projects that were registered between X and X in 2005. A web crawler downloaded the HTML files containing project summary data and developer information on the date of registration.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">David, Paul</style></author><author><style face="normal" font="default" size="100%">Francesco Rullani</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The micro-dynamics of open source software development activity</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/The micro-dynamics of open source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">339 - 340</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study aims to isolate and identify the properties of FLOSS development insofar as these can be revealed by examining the ecology of SF.net. It characterizes the contrast between the many “lurkers” and a much smaller core of “entrepreneurial” developers who are responsible for launching new projects, and gives an interpretation of the function of platforms such as SF.net as sites that people with a propensity to start open source projects can use to recruit “laborers”. It describes the process underpinning the mobility of those who are recruited among the projects that are launched and provides insights on the evolution of developers’ level and mode of involvement in FLOSS production.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Baravalle, Andres</style></author><author><style face="normal" font="default" size="100%">Chambers, Sarah</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source in Web-based Periodicals</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source in Web-based Periodicals.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">347 - 348</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we aim to investigate the role of the media in the diffusion of Open Source, analysing three web-based periodicals from Italy, United Kingdom and USA. The influence of the media in our society is wide and we have to look to that direction if we want to seriously investigate the in-depth causes of the different trends. Nevertheless, our results show a picture that may not be familiar to many researchers of the field.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zhu, Dengya</style></author><author><style face="normal" font="default" size="100%">Potdar, Vidyasagar</style></author><author><style face="normal" font="default" size="100%">Chang, Elizabeth</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software Development (OSSD) Based On Software Engineering</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Open Source Software Development (OSSD).pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">345 - 346</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">With the advent of Open Source Software (OSS) at the end of last century, many proponents believe that OSS is a new software development process and some even advocate OSS as a revolution for software engineering. The Cathedral and the Bazaar is a typical metaphor of the software development methodologies for the Closed Source Software (CSS) and the OSS. By comparing the phased (namely, requirement analysis, document design and system design, coding, testing and maintenance) software development methodology proposed by Software Engineering (SE), and by studying the management tools provided by SourceForge.net, we believe OSS development method not only follows the phased software development process, but also in return enriches the theory of SE.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Østerlie, Thomas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Producing and Interpreting Debug Texts</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Producing and Interpreting Debug Texts.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">335 - 336</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents preliminary findings from an ethnographic study of distributed, parallel debugging in an open source software (OSS) community. Focusing on the OSS developers’ daily activities, I propose the concept of making software debuggable. In so doing, I see a somewhat different story than common narratives of debugging in current OSS research, which describes distributed, parallel debugging as a set of highly cohesive tasks within loosely couple groups. I find that parallel, distributed debugging is rather a closely coupled collective process of producing and interpreting debug texts with high cohesion between the activities of reporting, finding, and understanding bugs.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Maeda, Kazuaki</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reusable Parser Generation from Open Source Compilers</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Reusable Parser Generation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">343 - 344</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Without Abstract</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rentocchini, Francesco</style></author><author><style face="normal" font="default" size="100%">De Prato, Giuditta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Patents and Open Source Software in the European Union: Evidences of a Trade-Off?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006///</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Software Patents and Open Source Software.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">349 - 351</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The present work aims at giving an account of the patenting behaviour in the software sector, focusing on the European Union and pointing out issues regarding a trade-off which would support a policy attitude in favour of a wider diffusion of the Open Source model.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stewart, K.</style></author><author><style face="normal" font="default" size="100%">Gosain, S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Impact of Ideology on Effectiveness in Open Source Software Development Teams</style></title><secondary-title><style face="normal" font="default" size="100%">MIS Quarterly</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">communication</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">effectiveness</style></keyword><keyword><style  face="normal" font="default" size="100%">feature requests</style></keyword><keyword><style  face="normal" font="default" size="100%">ideology</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword><keyword><style  face="normal" font="default" size="100%">team effort</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword><keyword><style  face="normal" font="default" size="100%">trust</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/stewartgosain2.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">30</style></volume><pages><style face="normal" font="default" size="100%">291-314</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The emerging work on understanding open source software has argued for the importance of understanding what leads to effectiveness in OSS development teams and has pointed to the importance of ideology. This paper develops a framework of the OSS ideology (including specific norms, beliefs, and values) and a theoretical model to show how adherence to components of the ideology impact effectiveness in OSS teams. The model is based on the idea that ideology provides clan control, which is important in OSS development settings because OSS teams generally lack formal behavioral and outcome controls. The paper hypothesizes both direct effects of ideology on OSS team effectiveness and indirect effects via influences on affective trust, cognitive trust, and communication quality. Hypotheses are tested using survey and objective data on OSS projects. Four effectiveness measures are used to capture unique aspects of effectiveness in OSS including both the extent to which a team attracts input from the community and the team's success in accomplishing project outcomes. Results support the main thesis that OSS team members' adherence to the tenets of the OSS community ideology enhances OSS team effectiveness. The study uncovers several differences in the importance of OSS norms, beliefs, and values to different kinds of OSS team effectiveness and discusses implications for theory and practice.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;...we collected data related to OSS projects hosted on Sourceforge (www.sourceforge.net).&quot;
&quot;Data was collected using two surveys and from the Sourceforge website.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">von Krogh, G.</style></author><author><style face="normal" font="default" size="100%">Spaeth, S.</style></author><author><style face="normal" font="default" size="100%">Haefliger, S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Knowledge Reuse in Open Source Software: An Exploratory Study of 15 Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 38th Annual Hawaii International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge reuse</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Big Island, HI, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><abstract><style face="normal" font="default" size="100%">To date, there is no investigation of knowledge reuse in open source software projects. This paper focuses on the forms of knowledge reuse and the factors impacting on them. It develops a theory drawn from data of 15 open source software projects and finds that the effort to search, integrate and maintain external knowledge influences the form of knowledge to be reused. Implications for firms and innovation research are discussed.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;In a first step, we asked developers of different open source projects to respond to a very short web-based survey.&quot;...
&quot;In a second step, we started with gathering data from 15 projects, including interviews. In parallel, the source code, CVS comments and to a certain extent email communication was analyzed to receive a dynamic, and within the limits of the method, complete picture of knowledge reuse practices.&quot;
&quot;Projects included games (Adonthell, FlightGear, Xboard), text processing (Abiword), a GNU/Linux desktop (Xfce4), an instant messenger client (Miranda), fax software (HylaFAX), a content management system (Tiki/CMS Groupware), encryption software (OpenSSL), a collaborative music system (iRATE Radio), file sharing networks (GNUnet, Mnet, Freenet), a mailing list manager (Mailman), and an mp3 encoder (Lame).&quot;
&quot;Our data sources included interviews with key developers, source code, CVS comments, mailing lists and various Internet resources&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman K.</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Lefteris Angelis</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Identifying Knowledge Brokers that Yield Software Engineering Knowledge in OSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Information and Software Technology</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">expertise</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge sharing</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">11/2006</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/IST-Vol-48-11-2006.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">46</style></volume><pages><style face="normal" font="default" size="100%">1025-1033</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Much research on open source software development concentrates on developer lists and other software repositories to investigate what motivates professional software developers to participate in open source software projects. Little attention has been paid to individuals who spend valuable time in lists helping participants on some mundane yet vital project activities. Using three Debian lists as a case study we investigate the impact of knowledge brokers and their associated activities in open source projects. Social network analysis was used to visualize how participants are affiliated with the lists. The network topology reveals substantial community participation. The consequence of collaborating in mundane activities for the success of open source software projects is discussed. The direct beneficiaries of this research are in the identification of knowledge experts in open source software projects.</style></abstract><notes><style face="normal" font="default" size="100%">Uses the Debian mailing lists &quot;kde&quot;, &quot;mentor&quot;, and &quot;user&quot;. 
the collection period was from January 2001 to September 2004</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Reichle, M.</style></author><author><style face="normal" font="default" size="100%">Hanft, A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The FLOSSWALD information system on free and open source software</style></title><secondary-title><style face="normal" font="default" size="100%">9th International Workshop on Learning Software Organizations</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">10/2006</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/flosswald.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">We propose the implementation of an intelligent information system on free and open source software. This system will consist of a case-based reasoning (CBR) system and several machine learning modules to maintain the knowledge base and train the CBR system thus enhancing its performance. Our knowledge base will include data on free and open source software provided by the Debian project, the FLOSSmole project, and other public free and open source software directories. We plan to enrich these data by learning additional information such as concepts and different similarities. With this knowledge base, we hope to be able to create an information system that will be capable of answering queries based on precise as well as vague criteria and give intelligent recommendations on software based on the preferences of the user.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Benoit Hamet</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Integration of libre software applications to create a collaborative work platform for researchers at GET</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Information Technology and Web Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">collaborative work environment</style></keyword><keyword><style  face="normal" font="default" size="100%">contribution</style></keyword><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">groupware</style></keyword><keyword><style  face="normal" font="default" size="100%">in-house applications</style></keyword><keyword><style  face="normal" font="default" size="100%">libre software</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">OpenLDAP</style></keyword><keyword><style  face="normal" font="default" size="100%">phpGroupware</style></keyword><keyword><style  face="normal" font="default" size="100%">PicoLibre</style></keyword><keyword><style  face="normal" font="default" size="100%">ProGET</style></keyword><keyword><style  face="normal" font="default" size="100%">Sympa</style></keyword><keyword><style  face="normal" font="default" size="100%">TWiki</style></keyword><keyword><style  face="normal" font="default" size="100%">WebDAV</style></keyword><keyword><style  face="normal" font="default" size="100%">wiki</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2006</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">3</style></number><publisher><style face="normal" font="default" size="100%">IGI Global</style></publisher><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">1-16</style></pages><abstract><style face="normal" font="default" size="100%">Libre software provides powerful applications ready to be integrated for the build-up of platforms for internal use in organizations. We describe the architecture of the collaborative work platform which we have integrated, designed for researchers at GET. We present the elements we have learned during this project in particular with respect to contribution to external libre projects, in order to better ensure the maintainability of the internal applications, and to phpGroupware as a framework for specific applications development.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Shah, Sonali K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Motivation, Governance, and the Viability of Hybrid Forms in Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">Management Science</style></secondary-title><short-title><style face="normal" font="default" size="100%">Management Science</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">governance</style></keyword><keyword><style  face="normal" font="default" size="100%">INNOVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">interview</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software development</style></keyword><keyword><style  face="normal" font="default" size="100%">Volunteers</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2006</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">faculty.washington.edu/skshah/Shah%20-%20Motivation,%20Governance,%20Hybrid%20Forms.pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Shah - Motivation, Governance, Hybrid Forms.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">52</style></volume><pages><style face="normal" font="default" size="100%">1000 - 1014</style></pages><abstract><style face="normal" font="default" size="100%">Open source software projects rely on the voluntary efforts of thousands of software developers, yet we know little about why developers choose to participate in this collective development process. This paper inductively derives a framework for understanding participation from the perspective of the individual software developer based on data from two software communities with different governance structures.

In both communities, a need for software-related improvements drives initial participation. The majority of participants leave the community once their needs are met, however, a small subset remains involved. For this set of developers, motives evolve over time and participation becomes a hobby. These hobbyists are critical to the long-term viability of the software code: They take on tasks that might otherwise go undone and work to maintain the simplicity and modularity of the code. Governance structures affect this evolution of motives. Implications for firms interested in implementing hybrid strategies designed to combine the advantages of open source software development with proprietary ownership and control are discussed.</style></abstract><issue><style face="normal" font="default" size="100%">7</style></issue><notes><style face="normal" font="default" size="100%">&quot;Data from three primary sources informed this research (Table 1). All data were collected in 2001–2002.&quot;
Online project documentation: All publicly available project descriptions, charters, bylaws, meeting minutes, etc.
Mailing lists: Over 2,000 messages read over a three-month period prior to interviews
Interviews 
&quot;Ireadallpostingstoproject-specific and general mailing lists for both communities for a three-month period preceding the interviews. Over 2,000 messages were posted during this period. Read- ing these messages allowed me to gain familiarity with the technology...&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kuk, George</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Strategic Interaction and Knowledge Sharing in the KDE Developer Mailing List</style></title><secondary-title><style face="normal" font="default" size="100%">Management Science</style></secondary-title><short-title><style face="normal" font="default" size="100%">Management Science</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge collaboration</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge sharing</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">52</style></volume><pages><style face="normal" font="default" size="100%">1031 - 1042</style></pages><abstract><style face="normal" font="default" size="100%">In stark contrast with the fully participative &quot;bazaar&quot; imagery of open source software (OSS) development, some recent empirical research has pointed out that much of the OSS development is carried out by a small percentage of developers. This raises serious concerns that concentration of development effort on a few will limit knowledge sharing and underutilize the available resources. Using the notion of strategic interaction, this paper argues that individual developers often interact strategically with other highly resourceful developers by forming a smaller but better organized structure to intensify the types of epistemic interactions that matter most to the OSS development. A general framework of strategic interaction including participation inequality, conversational interactivity, and cross-thread connectivity is proposed to examine its impact on knowledge sharing, and validated using 128 discussion threads from the K Desktop Environment (KDE) developer mailing list. The findings indicate that strategic interaction has expanded knowledge sharing but with the caveat that extreme concentration of development could have an opposite effect. For researchers, this study dovetails the incentive logic by proposing and validating the strategic aspects of OSS participation to better understand the collective dynamics underpinning OSS development. Practitioners can use this approach to evaluate and better support existing knowledge-sharing initiatives.</style></abstract><issue><style face="normal" font="default" size="100%">7</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Roberts, Jeffrey A.</style></author><author><style face="normal" font="default" size="100%">Il-Horn Hann</style></author><author><style face="normal" font="default" size="100%">Slaughter, Sandra A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding the Motivations, Participation, and Performance of Open Source Software Developers: A Longitudinal Study of the Apache Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Management Science</style></secondary-title><short-title><style face="normal" font="default" size="100%">Management Science</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">change logs</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">extrinsic motivation</style></keyword><keyword><style  face="normal" font="default" size="100%">intrinsic motivation</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">participation</style></keyword><keyword><style  face="normal" font="default" size="100%">software development performance</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">status</style></keyword><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">52</style></volume><pages><style face="normal" font="default" size="100%">984 - 999</style></pages><abstract><style face="normal" font="default" size="100%">Understanding what motivates participation is a central theme in the research on open source software (OSS) development. Our study contributes by revealing how the different motivations of OSS developers are interrelated, how these motivations influence participation leading to performance, and how past performance influences subsequent motivations. Drawing on theories of intrinsic and extrinsic motivation, we develop a theoretical model relating the motivations, participation, and performance of OSS developers. We evaluate our model using survey and archival data collected from a longitudinal field study of software developers in the Apache projects. Our results reveal several important findings. First, we find that developers’ motivations are not independent but rather are related in complex ways. Being paid to contribute to Apache projects is positively related to developers’ status motivations but negatively related to their use-value motivations. Perhaps surprisingly, we find no evidence of diminished intrinsic motivation in the presence of extrinsic motivations; rather, status motivations enhance intrinsic motivations. Second, we find that different motivations have an impact on participation in different ways. Developers’ paid participation and status motivations lead to above-average contribution levels, but use-value motivations lead to below-average contribution levels, and intrinsic motivations do not significantly impact average contribution levels. Third, we find that developers’ contribution levels positively impact their performance rankings. Finally, our results suggest that past-performance rankings enhance developers’ subsequent status motivations.</style></abstract><issue><style face="normal" font="default" size="100%">7</style></issue><notes><style face="normal" font="default" size="100%">&quot;analyzing archival data collected from OSS project records over a period of four years&quot;
&quot;Apart from the source and binary codes of the actual software programs, Apache products include developer websites, change logs, documentation, and developer communications in the form of e-mail archives. From these products, we extracted two types of information: each contributor’s progression along the Apache career path, and each contributor’s source code contributions to the project.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author><author><style face="normal" font="default" size="100%">Gallagher, Scott</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Challenges of open innovation: the paradox of firm investment in open-source software</style></title><secondary-title><style face="normal" font="default" size="100%">R&amp;D Management</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">36</style></volume><pages><style face="normal" font="default" size="100%">319 - 331</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;&amp;nbsp;&lt;span class=&quot;Apple-style-span&quot; style=&quot;font-size: 13px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; &quot;&gt;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&amp;amp;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&lt;/span&gt;&lt;/p&gt;</style></abstract><issue><style face="normal" font="default" size="100%">3</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Inoue, Keisuke</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social dynamics of free and open source team communications</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing </style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracker</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">communications</style></keyword><keyword><style  face="normal" font="default" size="100%">Dynamic social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS teams</style></keyword><keyword><style  face="normal" font="default" size="100%">Human Factors</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">software development</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">06/2006</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Social dynamics of free and open source team.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><volume><style face="normal" font="default" size="100%">203/2006</style></volume><pages><style face="normal" font="default" size="100%">319 - 330</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Shilad Sen</style></author><author><style face="normal" font="default" size="100%">Shyong K. Lam</style></author><author><style face="normal" font="default" size="100%">Dan Cosley</style></author><author><style face="normal" font="default" size="100%">Al Mamunur Rashid</style></author><author><style face="normal" font="default" size="100%">Dan Frankowski</style></author><author><style face="normal" font="default" size="100%">Franklin Harper</style></author><author><style face="normal" font="default" size="100%">Jeremy Osterhouse</style></author><author><style face="normal" font="default" size="100%">John Riedl</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">tagging, community, vocabulary, evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Computer Supported Cooperative Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">04/11/2006</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Banff, Alberta, Canada</style></pub-location><pages><style face="normal" font="default" size="100%">181-190</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-249-6</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Valverde, S.</style></author><author><style face="normal" font="default" size="100%">Theraulaz, G.</style></author><author><style face="normal" font="default" size="100%">Gautrais, J.</style></author><author><style face="normal" font="default" size="100%">Fourcassie, V.</style></author><author><style face="normal" font="default" size="100%">Sole, R.V.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Self-Organization Patterns in Wasp and Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">IEEE Intelligent Systems</style></secondary-title><short-title><style face="normal" font="default" size="100%">IEEE Intell. Syst.</style></short-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">agents</style></keyword><keyword><style  face="normal" font="default" size="100%">decentralization</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">hierarchy</style></keyword><keyword><style  face="normal" font="default" size="100%">labor division</style></keyword><keyword><style  face="normal" font="default" size="100%">organization</style></keyword><keyword><style  face="normal" font="default" size="100%">self-organizing teams</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword><keyword><style  face="normal" font="default" size="100%">wasps</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">03/2006</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.95.5574&amp;rep=rep1&amp;type=pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/valverde.pdf</style></url></related-urls></urls><volume><style face="normal" font="default" size="100%">21</style></volume><pages><style face="normal" font="default" size="100%">36 - 40</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, we conducted a comparative study of how social organization takes place in a wasp colony and OSS developer communities. Both these systems display similar global organization patterns, such as hierarchies and clear labor divisions. As our analysis shows, both systems also define interacting agent networks with similar common features that reflect limited information sharing among agents. As far as we know, this is the first research study analyzing the patterns and functional significance of these systems' weighted-interaction networks. By illuminating the extent to which self-organization is responsible for patterns such as hierarchical structure, we can gain insight into the origins of organization in OSS communities.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue><notes><style face="normal" font="default" size="100%">&quot;To investigate such claims, we studied an OSS community’s social network from a dataset describing the email activity of 120 different software teams&quot;
&quot;Our test data originated from Sourceforge (http://sourceforge.net), a large open source project repository, and included communi- ties ranging from very small networks with one or two members to large networks with thousands of members.&quot;
&quot;we limited our consideration to email traffic associated with bug fixes and bug reporting. As other researchers have shown[5] this email subset allows an effective reconstruction of the software community’s social network.&quot;
&quot;We thank Kevin Crowston and James Howison for making their software data publicly available.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">David M Nichols</style></author><author><style face="normal" font="default" size="100%">Michael B Twidale</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Usability processes in open source projects</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process: Improvement and Practice</style></secondary-title><short-title><style face="normal" font="default" size="100%">Softw. Process: Improve. Pract.</style></short-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">03/2006</style></date></pub-dates></dates><volume><style face="normal" font="default" size="100%">11</style></volume><pages><style face="normal" font="default" size="100%">149 - 162</style></pages><abstract><style face="normal" font="default" size="100%">We explore how some open source projects address issues of usability. We describe the mechanisms, techniques and technology used by open source communities to design and refine the interfaces to their programs. In particular we consider how these developers cope with their distributed community, lack of domain expertise, limited resources and separation from their users. We also discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers.</style></abstract><issue><style face="normal" font="default" size="100%">2</style></issue></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">N. Good</style></author><author><style face="normal" font="default" size="100%">J. Grossklags</style></author><author><style face="normal" font="default" size="100%">Konstan, J.A.</style></author><author><style face="normal" font="default" size="100%">D. Mulligan</style></author><author><style face="normal" font="default" size="100%">A. Perzanowski</style></author><author><style face="normal" font="default" size="100%">D. Thaw</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">User Choices and Regret: Understanding Users' Decision Process bout Consensually Acquired Spyware</style></title><secondary-title><style face="normal" font="default" size="100%">I/S: A Journal of Law and Policy for the Information Society</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year><pub-dates><date><style  face="normal" font="default" size="100%">01/2006</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">2</style></volume><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, Claudio</style></author><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author><author><style face="normal" font="default" size="100%">Reale, Salvatore</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Adopting Open Source for Mission-Critical Applications: A Case Study on Single Sign-On</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Adapting OS for Mission-critical Applications.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">209 - 220</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, we describe a specific selection process for security-related open source code, based on a methodology aimed at evaluating open source security frameworks in general and Single-Sign-On (SSO) systems in particular. Our evaluation criteria for open source security-related software include the community’s timeliness of reaction against newly discovered vulnerabilities or incidents.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tsunoda, Masateru</style></author><author><style face="normal" font="default" size="100%">Monden, Akito</style></author><author><style face="normal" font="default" size="100%">Kakimoto, Takeshi</style></author><author><style face="normal" font="default" size="100%">Kamei, Yasutaka</style></author><author><style face="normal" font="default" size="100%">Matsumoto, Ken-ichi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analyzing OSS developers' working time using mailing lists archives</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">overtime work</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">workload</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138031</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/181AnalyzingOSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">181–182</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Our mining question is “when OSS developers work?” OSS developers' working time may be a good indicator to understand the development style of a project. (For example, if many developers work in office hour, these might be daily works in a company.)</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">López-Fernández, L.</style></author><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Herraiz, I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Applying Social Network Analysis Techniques to Community-Driven Libre Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Information Technology and Web Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">conway's law</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/06_Lopez_ijitwe_sna.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">1</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Source code management repositories of large, long-lived libre (free, open source) software projects can be a source of valuable data about the organizational structure, evolution, and knowledge exchange in the corresponding development communities. Unfortunately, the sheer volume of the available information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. Such methodology is proposed in this article, based on well known concepts from the social networks analysis field, which can be used to study the relationships among developers and how they collaborate in different parts of a project. It is also applied to data mined from some well known projects (Apache, GNOME, and KDE), focusing on the characterization of their collaboration network architecture. These cases help to understand the potentials of the methodology and how it is applied, but also shows some relevant results which open new paths in the understanding of the informal organization of libre software development communities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">D'Ambros, Marco</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Applying the evolution radar to PostgreSQL</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">documentation</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution radar</style></keyword><keyword><style  face="normal" font="default" size="100%">logical coupling</style></keyword><keyword><style  face="normal" font="default" size="100%">makefile</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">re-engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword><keyword><style  face="normal" font="default" size="100%">rhdb</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138029</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/177ApplyingEvolution.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">177–178</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weißgerber, Peter</style></author><author><style face="normal" font="default" size="100%">Diehl, Stephan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Are refactorings less error-prone than other changes?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword><keyword><style  face="normal" font="default" size="100%">junit</style></keyword><keyword><style  face="normal" font="default" size="100%">re-engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">reverse engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138011</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/112AreRefactorings.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">112–118</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Refactorings are program transformations which should preserve the program behavior. Consequently, we expect that during phases when there are mostly refactorings in the change history of a system, only few new bugs are introduced. For our case study we analyzed the version histories of several open source systems and reconstructed the refactorings performed. Furthermore, we obtained bug reports from various sources depending on the system. Based on this data we identify phases when the above hypothesis holds and those when it doesn't.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Beyond Low-Hanging Fruit: Seeking the Next Generation in FLOSS Data Mining</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Beyond Low-Hanging Fruit.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">47 - 56</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper will discuss the motivations and methods for collecting quantitative data about free, libre and open source (FLOSS) software projects. The paper also describes the current state of the art in collecting this data, and some of the problems with this process. Finally, the paper outlines the challenges data miners should look forward to when trying to improve the usefulness of their quantitative data streams.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">de Groot, Adriaan</style></author><author><style face="normal" font="default" size="100%">Kügler, Sebastian</style></author><author><style face="normal" font="default" size="100%">Adams, Paul</style></author><author><style face="normal" font="default" size="100%">Gousios, Giorgos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Call for Quality: Open Source Software Quality Observation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Call for Quality.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">57 - 62</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Beyer, Dirk</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Co-change visualization applied to PostgreSQL and ArgoUML: (MSR challenge report)</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">ccvisu</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">force-directed graph layout</style></keyword><keyword><style  face="normal" font="default" size="100%">graph</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">software clustering</style></keyword><keyword><style  face="normal" font="default" size="100%">software structure analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">software visualization</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138023</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/165Co-Change.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">165–166</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author><author><style face="normal" font="default" size="100%">Galia, Fabrice</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaborative Maintenance in Large Open-Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">COLLABORATION</style></keyword><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">gcc</style></keyword><keyword><style  face="normal" font="default" size="100%">ghostscript</style></keyword><keyword><style  face="normal" font="default" size="100%">halstead</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">mccabe</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">netbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">openssh</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Collaborative Maintenance.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">233 - 244</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Dodero, Gabriella</style></author><author><style face="normal" font="default" size="100%">Lupi, Katia</style></author><author><style face="normal" font="default" size="100%">Piffero, Erika</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Comparing macro development for personal productivity tools: an experience in validating accessibility of Talking Books</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Comparing macro development.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">247 - 252</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author><author><style face="normal" font="default" size="100%">Strecker, Stefan</style></author><author><style face="normal" font="default" size="100%">Frank, Ulrich</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Conceptual Modelling as a New Entry in the Bazaar: The Open Model Approach</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Conceptual Modelling as a New Entry.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">9 - 20</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 “open model” 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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Gonzalez-Barahona, Jesus</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Contributor Turnover in Libre Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">committers</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">gimp</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">mono</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Contributor Turnover in Libre Software Projects.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">273 - 286</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 “code gods”), while others are driven by several different developer groups over time (i.e. the project “regenerates” 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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Kangning Wei</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Core and periphery in Free/Libre and Open Source software team communications</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, &quot;how does one empirically distinguish the core?&quot; 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'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.</style></abstract><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">computational</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Brink, Daniel</style></author><author><style face="normal" font="default" size="100%">Roos, Llewelyn</style></author><author><style face="normal" font="default" size="100%">Weller, James</style></author><author><style face="normal" font="default" size="100%">Van Belle, Jean-Paul</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Critical Success Factors for Migrating to OSS-on-the-Desktop: Common Themes across Three South African Case Studies</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Critical Success Factors for Migrating.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">287 - 293</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sager, Tobias</style></author><author><style face="normal" font="default" size="100%">Bernstein, Abraham</style></author><author><style face="normal" font="default" size="100%">Pinzger, Martin</style></author><author><style face="normal" font="default" size="100%">Kiefer, Christoph</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Detecting similar Java classes using tree algorithms</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">clones</style></keyword><keyword><style  face="normal" font="default" size="100%">coogle</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">famix</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">similarity</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">tree similarity measures</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138000</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/65Detecting.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">65–71</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Similarity analysis of source code is helpful during development to provide, for instance, better support for code reuse. Consider a development environment that analyzes code while typing and that suggests similar code examples or existing implementations from a source code repository. Mining software repositories by means of similarity measures enables and enforces reusing existing code and reduces the developing effort needed by creating a shared knowledge base of code fragments. In information retrieval similarity measures are often used to find documents similar to a given query document. This paper extends this idea to source code repositories. It introduces our approach to detect similar Java classes in software projects using tree similarity algorithms. We show how our approach allows to find similar Java classes based on an evaluation of three tree-based similarity measures in the context of five user-defined test cases as well as a preliminary software evolution analysis of a medium-sized Java project. Initial results of our technique indicate that it (1) is indeed useful to identify similar Java classes, (2)successfully identifies the ex ante and ex post versions of refactored classes, and (3) provides some interesting insights into within-version and between-version dependencies of classes within a Java project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiss, Michael</style></author><author><style face="normal" font="default" size="100%">Moroiu, Gabriella</style></author><author><style face="normal" font="default" size="100%">Zhao, Ping</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution of Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">membership</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Evolution of Open Source Communities.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">21 - 32</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The goal of this paper is to document the evolution of a portfolio of related open source communities over time. As a case study, we explore the subprojects of the Apache project, one of the largest and most visible open source projects. We extract the community structure from the mailing list data, and study how the subcommunities evolve, and are interrelated over time. Our analysis leads us to propose the following hypotheses about the growth of open source communities: (1) communities add new developers by a process of preferential attachment; (2) links between existing communities are also subject to preferential attachment; (3) developers will migrate between communities together with other collaborators; and (4) information flow follows project dependencies. In particular, we are concerned with the underlying factors that motivate the migration between communities, such as information flow, co-worker ties, and project dependencies.
</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we took snapshots of its membership at regular intervals&quot;
&quot;we chose a one year period&quot;
&quot;we retrieve the list of core developers ordered by their number of inbound messages, as noted above.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">D'Ambros, Marco</style></author><author><style face="normal" font="default" size="100%">Lanza, Michele</style></author><author><style face="normal" font="default" size="100%">Lungu, Mircea</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The evolution radar: visualizing integrated logical coupling information</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">logical coupling</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">thunderbird</style></keyword><keyword><style  face="normal" font="default" size="100%">tinderbox</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137992</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/26TheEvolutionRadar.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">26–32</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of the file-based nature of current versioning systems. Previous research has dealt with low-level couplings between files, leading to an explosion of data to be analyzed, or has abstracted the logical couplings to module level, leading to a loss of detailed information. In this paper we propose a visualization-based approach which integrates both file-level and module-level logical coupling information. This not only facilitates an in-depth analysis of the logical couplings at all granularity levels, it also leads to a precise characterization of the system modules in terms of their logical coupling dependencies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zhen Ming Jiang</style></author><author><style face="normal" font="default" size="100%">Hassan, Ahmed E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Examining the evolution of code comments in PostgreSQL</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">code comments</style></keyword><keyword><style  face="normal" font="default" size="100%">comments</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">functions</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">software maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138030</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/179ExaminingTheEvolution.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">179–180</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">It is common, especially in large software systems, for developers to change code without updating its associated comments due to their unfamiliarity with the code or due to time constraints. This is a potential problem since outdated comments may confuse or mislead developers who perform future development. Using data recovered from CVS, we study the evolution of code comments in the PostgreSQL project. Our study reveals that over time the percentage of commented functions remains constant except for early fluctuation due to the commenting style of a particular active developer.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hardy, Jean-Luc</style></author><author><style face="normal" font="default" size="100%">Bourgois, Marc</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Exploring the potential of OSS in Air Traffic Management</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Exploring the potential of OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">173 - 179</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper introduces a project that aims at defining an Open Source Software (OSS) policy in the field of Air Traffic Management (ATM). In order to develop such a policy, we chose to investigate first a set of predictive hypotheses. Our four initial hypotheses were presented, refined and discussed in bi-lateral meetings with experts in the ATM field and in several conferences and workshops with OSS experts. At a roundtable, jointly organized by CALIBRE and EUROCONTROL, we confronted early open source experiences and insights in the ATM domain with experiences and knowledge from a panel of OSS experts and practitioners from academia and industry. The revised initial hypotheses are presented using a fixed format that should facilitate further evolution of these hypotheses.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Canfora, Gerardo</style></author><author><style face="normal" font="default" size="100%">Cerulo, Luigi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Fine grained indexing of software repositories to support impact analysis</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">gedit</style></keyword><keyword><style  face="normal" font="default" size="100%">impact analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138009</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/105FineGrained.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">105–111</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Versioned and bug-tracked software systems provide a huge amount of historical data regarding source code changes and issues management. In this paper we deal with impact analysis of a change request and show that data stored in software repositories are a good descriptor on how past change requests have been resolved. A fine grained analysis method of software repositories is used to index code at different levels of granularity, such as lines of code and source files, with free text contained in software repositories. The method exploits information retrieval algorithms to link the change request description and code entities impacted by similar past change requests. We evaluate such approach on a set of three open-source projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sowe, Sulayman</style></author><author><style face="normal" font="default" size="100%">Ioannis Stamelos</style></author><author><style face="normal" font="default" size="100%">Deligiannis, Ignatios</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Framework for Teaching Software Testing using F/OSS Methodology</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A Framework for Teaching Software Testing.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">261 - 266</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we discuss a framework for teaching software testing to undergraduate students’ volunteers. The framework uses open source software development methodology and was implemented in the “Introduction to Software Engineering” course at the department of Informatics, Aristotle University, Greece. The framework is in three phases, each describing a teaching and learning context in which students get involved in real software projects activities. We report on our teaching experiences, lessons learned and some practical problems we encountered. Results from preliminary evaluation shows that students did well as bug hunters in the bazaar and are willing to  participate in their projects long after graduation.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hala Annabi</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Robert Heckman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From Individual Contribution to Group Learning</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">case study</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/From Individual Contribution to Group Learning.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">77 - 90</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) groups experience many benefits and challenges with respect to the core group’s effectiveness. In order to capitalize on the benefits and minimize the challenges, OSS groups must learn not only on the individual level, but also on the group level. OSS groups learn by integrating individual contributions into the group’s product and processes.
This paper reports on the characteristics of the learning process in OSS groups. The study utilized an embedded single case study design that observed and analyzed group learning processes in the Apache Web server OSS project. The study used learning opportunity episodes (LOE) as the embedded unit of analysis and developed and utilized three content analytic schemes to describe the characteristics of the learning process and the factors affecting this process.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Geographic location of developers at SourceForge</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">distributed</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email address</style></keyword><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">geographical location</style></keyword><keyword><style  face="normal" font="default" size="100%">geography</style></keyword><keyword><style  face="normal" font="default" size="100%">libre software</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">timezone</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138017</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/144GeographicLocation.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">144–150</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">The development of libre (free/open source) software is usually performed by geographically distributed teams. Participation in most cases is voluntary, sometimes sporadic, and often not framed by a pre-defined management structure. This means that anybody can contribute, and in principle no national origin has advantages over others, except for the differences in availability and quality of Internet connections and language. However, differences in participation across regions do exist, although there are little studies about them. In this paper we present some data which can be the basis for some of those studies. We have taken the database of users registered at SourceForge, the largest libre software development web-based platform, and have inferred their geographical locations. For this, we have applied several techniques and heuristics on the available data (mainly e-mail addresses and time zones), which are presented and discussed in detail. The results show a snapshot of the regional distribution of SourceForge users, which may be a good proxy of the actual distribution of libre software developers. In addition, the methodology may be of interest for similar studies in other domains, when the available data is similar (as is the case of mailing lists related to software projects).</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Hierarchy and centralization in Free and Open Source Software team communications</style></title><secondary-title><style face="normal" font="default" size="100%">Knowledge, Technology &amp; Policy</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">savannah</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword><keyword><style  face="normal" font="default" size="100%">teams</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CrowstonHierarchyAndCentralization.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">4</style></number><volume><style face="normal" font="default" size="100%">18</style></volume><pages><style face="normal" font="default" size="100%">65–85</style></pages><abstract><style face="normal" font="default" size="100%">Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Whitehead,Jr., E. James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How long did it take to fix bugs?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">quality</style></keyword><keyword><style  face="normal" font="default" size="100%">time</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138027</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/173HowLong.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">173–174</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">The number of bugs (or fixes) is a common factor used to measure the quality of software and assist bug related analysis. For example, if software files have many bugs, they may be unstable. In comparison, the bug-fix time--the time to fix a bug after the bug was introduced--is neglected. We believe that the bug-fix time is an important factor for bug related analysis, such as measuring software quality. For example, if bugs in a file take a relatively long time to be fixed, the file may have some structural problems that make it difficult to make changes. In this report, we compute the bug-fix time of files in ArgoUML and PostgreSQL by identifying when bugs are introduced and when the bugs are fixed. This report includes bug-fix time statistics such as average bug-fix time, and distributions of bug-fix time. We also list the top 20 bug-fix time files of two projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Hala Annabi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Information systems success in Free and Open Source Software development: Theory and measures</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process–Improvement and Practice</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">downloads</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">flossmole</style></keyword><keyword><style  face="normal" font="default" size="100%">page views</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">success</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">11</style></volume><pages><style face="normal" font="default" size="100%">123–148</style></pages><abstract><style face="normal" font="default" size="100%">Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project’s effectiveness in team building, the speed of the project at responding to bug reports and the project’s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we continue our examination of success measures using data from Sourceforge...&quot;
&quot;e chose the number of developers (assessed from the records of the project and from bug fixing logs), bug-fixing time, and popularity (assessed from the number of downloads and viewings of project Web pages, and inclusion in distributions). These measures were chosen because they span the reconsidered FLOSS development process discussed above, including inputs (number of developers), process (speed of bug fixing) and output (popularity).&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Askari, Mina</style></author><author><style face="normal" font="default" size="100%">Holt, Ric</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Information theoretic evaluation of change prediction models for large-scale software</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evaluation approach</style></keyword><keyword><style  face="normal" font="default" size="100%">file</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">information theory</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">koffice</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">netbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">openbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction models</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138013</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/126InformationTheoretic.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">126–132</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">In this paper, we analyze the data extracted from several open source software repositories. We observe that the change data follows a Zipf distribution. Based on the extracted data, we then develop three probabilistic models to predict which files will have changes or bugs. The first model is Maximum Likelihood Estimation (MLE), which simply counts the number of events, i.e., changes or bugs, that happen to each file and normalizes the counts to compute a probability distribution. The second model is Reflexive Exponential Decay (RED) in which we postulate that the predictive rate of modification in a file is incremented by any modification to that file and decays exponentially. The third model is called RED-Co-Change. With each modification to a given file, the RED-Co-Change model not only increments its predictive rate, but also increments the rate for other files that are related to the given file through previous co-changes. We then present an information-theoretic approach to evaluate the performance of different prediction models. In this approach, the closeness of model distribution to the actual unknown probability distribution of the system is measured using cross entropy. We evaluate our prediction models empirically using the proposed information-theoretic approach for six large open source systems. Based on this evaluation, we observe that of our three prediction models, the RED-Co-Change model predicts the distribution that is closest to the actual distribution for all the studied systems.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Evangelia Berdou</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Insiders and outsiders: paid contributors and the dynamics of cooperation in community led F/OS projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">interviews</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Insiders and outsiders.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">201 - 208</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper examines the role of paid developers in mature free/open source (F/OS) communities. In particular it provides a typology for their involvement based on their employment and sponsorship arrangements and elaborates a framework for understanding the dynamics of cooperation developing between them and the volunteers based on their community ties. The evidence presented is drawn from individual interviews conducted with volunteer and paid contributors from the GNOME and KDE projects within the context of a PhD research focusing on commercialization and peripheral participation in F/OS communities. The paper highlights the various interdependencies that form between communities and companies and adds to our understanding of the dynamics of commercialization in F/OS projects.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Westenholz, Ann</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Institutional Entrepreneurs and the Bricolage of Intellectual Property Discourses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Institutional Entrepreneurs and the Bricolage.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">183 - 193</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Commercial software firms are increasingly becoming involved with open source communities. In this research-in-progress paper I briefly analysed a single firm case that demonstrates how an institutional entrepreneur mixes in an innovative way different discourses in an attempt to legitimise a new mode for developing software applying both open and closed source codes. The institutional entrepreneur does this by creating new distinctions in his daily software developing work. I am not arguing that the institutional entrepreneur is creating these new distinctions in an instrumental rational process, but that the distinctions emerge in sensemaking processes along his ‘doing’ something in the firm.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ven, Kris</style></author><author><style face="normal" font="default" size="100%">Van Nuffel, Dieter</style></author><author><style face="normal" font="default" size="100%">Verelst, Jan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Introduction of OpenOffice.org in the Brussels Public Administration</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/The Introduction of OpenOffice.org.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">123 - 134</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software is increasingly used by public administrations as an alternative to commercial software. In this paper we present a case study of the transition of the ministerial cabinets of the Brussels-Capital Region towards OpenOffice.org. 
In this case, the decision to use open source software was taken by the Government of the Brussels-Capital Region. The goal of the paper is to outline the implementation trajectory followed and to compare our findings to previous studies in this field as well as other Information Systems literature. Additionally, we discuss how OpenOffice.org was received by end users as well as the IT department that was responsible for the migration. Our findings indicate that although a migration towards OpenOffice.org is feasible, a number of difficulties still remain. For example, end user perceptions of OpenOffice.org are not always favorable and migration costs (document conversion and training) can be significant.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">D’Andrea, Vincenzo</style></author><author><style face="normal" font="default" size="100%">Gangadharan, G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Licensing Services: An “Open” Perspective</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Licensing Services  An Open Perspective.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">143 - 154</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Though service orientation is an incipient technology, the inherently infinite potentiality of services makes them to proliferate seamlessly, serving in myriad domains. Licensing of services enables to regulate the commercial use and modifications of service, retaining the copyright with owner of the service. With the growing influence of open source initiatives today, it becomes a significant topic to analyze ‘open’ing services. In this paper, we present a concept of ‘open service’ and analyze the implications of open source approach on service licenses.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koponen, Timo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Life cycle of Defects in Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">defects</style></keyword><keyword><style  face="normal" font="default" size="100%">Firefox</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Life cycle of Defects in OSS Projects.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">195 - 200</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We studied the maintenance process from the viewpoint of defect management and the defect life cycle. First, we outline a model for the defect life cycle based on ISO/IEC standards, the Framework for Open Source maintenance process, and the Bugzilla defect management system. Thereafter, we analyze defects from two Open Source software projects. The aim of the study was support the maintenance reliability. However, we found that most of the defects did not follow the life-cycle model. Defects were usually directly resolved from initial state without being assigned.
</style></abstract><notes><style face="normal" font="default" size="100%">&quot;we collected and analyzed defects of the apache http server and mozilla firefox&quot; 
&quot;all the defects reported between X and X were analyzed&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Xie, Tao</style></author><author><style face="normal" font="default" size="100%">Pei, Jian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">MAPO: mining API usages from open source repositories</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">api</style></keyword><keyword><style  face="normal" font="default" size="100%">application programming interfaces</style></keyword><keyword><style  face="normal" font="default" size="100%">documentation</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">pmd</style></keyword><keyword><style  face="normal" font="default" size="100%">program comprehension</style></keyword><keyword><style  face="normal" font="default" size="100%">search engine</style></keyword><keyword><style  face="normal" font="default" size="100%">sequences</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">source code search engine</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137997</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/54MAPO.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">54–57</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">To improve software productivity, when constructing new software systems, developers often reuse existing class libraries or frameworks by invoking their APIs. Those APIs, however, are often complex and not well documented, posing barriers for developers to use them in new client code. To get familiar with how those APIs are used, developers may search the Web using a general search engine to find relevant documents or code examples. Developers can also use a source code search engine to search open source repositories for source files that use the same APIs. Nevertheless, the number of returned source files is often large. It is difficult for developers to learn API usages from a large number of returned results. In order to help developers understand API usages and write API client code more effectively, we have developed an API usage mining framework and its supporting tool called MAPO (for Mining API usages from Open source repositories). Given a query that describes a method, class, or package for an API, MAPO leverages the existing source code search engines to gather relevant source files and conducts data mining. The mining leads to a short list of frequent API usages for developers to inspect. MAPO currently consists of five components: a code search engine, a source code analyzer, a sequence preprocessor, a frequent sequence miner, and a frequent sequence post processor. We have examined the effectiveness of MAPO using a set of various queries. The preliminary results show that the framework is practical for providing informative and succinct API usage patterns.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Pan, Kai</style></author><author><style face="normal" font="default" size="100%">Whitehead,Jr., E. James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Micro pattern evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">columba</style></keyword><keyword><style  face="normal" font="default" size="100%">design patterns</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">extraction</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137995</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/40MicroPattern.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">40–46</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">When analyzing the evolution history of a software project, we wish to develop results that generalize across projects. One approach is to analyze design patterns, permitting characteristics of the evolution to be associated with patterns, instead of source code. Traditional design patterns are generally not amenable to reliable automatic extraction from source code, yet automation is crucial for scalable evolution analysis. Instead, we analyze “micro pattern” evolution; patterns whose abstraction level is closer to source code, and designed to be automatically extractable from Java source code or bytecode. We perform micro-pattern evolution analysis on three open source projects, ArgoUML, Columba, and jEdit to identify micro pattern frequencies, common kinds of pattern evolution, and bug-prone patterns. In all analyzed projects, we found that the micro patterns of Java classes do not change often. Common bug- prone pattern evolution kinds are ‘Pool → Pool’, ‘Implementor → NONE’, and ‘Sampler → Sampler’. Among all pattern evolution	kinds,‘Box’,‘CompoundBox’,	‘Pool’, ‘CommonState’, and ‘Outline’ micro patterns have high bug rates, but they have low frequencies and a small number of changes. The pattern evolution kinds that are bug-prone are somewhat similar across projects. The bug-prone pattern evolution kinds of two different periods of the same project are almost identical.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Breu, Silvia</style></author><author><style face="normal" font="default" size="100%">Lindig, Christian</style></author><author><style face="normal" font="default" size="100%">Livshits, Benjamin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining additions of method calls in ArgoUML</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">function calls</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">pattern</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">xelopes</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138025</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/169MiningAdditions.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">169–170</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">In this paper we refine the classical co-change to the addition of method calls. We use this concept to find usage patterns and to identify cross-cutting concerns for ArgoUML.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author><author><style face="normal" font="default" size="100%">L. Daudet</style></author><author><style face="normal" font="default" size="100%">den Besten, Matthijs</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining CVS Signals</style></title><secondary-title><style face="normal" font="default" size="100%">1st Workshop on Public Data about Software Development (WoPDaSD 2006)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><pages><style face="normal" font="default" size="100%">10-19</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Breu, Silvia</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Lindig, Christian</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining eclipse for cross-cutting concerns</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">aspects</style></keyword><keyword><style  face="normal" font="default" size="100%">concept analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138006</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/94MiningEclipse.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">94–97</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Software may contain functionality that does not align with its architecture. Such cross-cutting concerns do not exist from the beginning but emerge over time. By analysing where developers add code to a program, our history-based mining identifies cross-cutting concerns in a two-step process. First, we mine CVS archives for sets of methods where a call to a specific single method was added. In a second step, such simple cross-cutting concerns are combined to complex cross-cutting concerns. To compute these efficiently, we apply formal concept analysis—an algebraic theory. History-based mining scales well: we are the first to report aspects mined from an industrial-sized project like Eclipse. For example, we identified a locking concern that crosscuts 1284 methods.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Gourley, Alex</style></author><author><style face="normal" font="default" size="100%">Devanbu, Prem</style></author><author><style face="normal" font="default" size="100%">Gertz, Michael</style></author><author><style face="normal" font="default" size="100%">Swaminathan, Anand</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining email social networks</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">communication</style></keyword><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138016</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/137MiningEmail.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">137–143</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Communication &amp; Co-ordination activities are central to large software projects, but are difficult to observe and study in traditional (closed-source, commercial) settings because of the prevalence of informal, direct communication modes. OSS projects, on the other hand, use the internet as the communication medium,and typically conduct discussions in an open, public manner. As a result, the email archives of OSS projects provide a useful trace of the communication and co-ordination activities of the participants. However, there are various challenges that must be addressed before this data can be effectively mined. Once this is done, we can construct social networks of email correspondents, and begin to address some interesting questions. These include questions relating to participation in the email; the social status of different types of OSS participants; the relationship of email activity and commit activity (in the CVS repositories) and the relationship of social status with commit activity. In this paper, we begin with a discussion of our infrastructure (including a novel use of Scientific Workflow software) and then discuss our approach to mining the email archives; and finally we present some preliminary results from our data analysis.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bird</style></author><author><style face="normal" font="default" size="100%">Gourley, Alex</style></author><author><style face="normal" font="default" size="100%">Devanbu, Prem</style></author><author><style face="normal" font="default" size="100%">Gertz, Michael</style></author><author><style face="normal" font="default" size="100%">Swaminathan, Anand</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining email social networks in Postgres</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">status</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138033</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/185MiningEmail.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">185–186</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) projects provide a unique opportunity to gather and analyze publicly available historical data. The Postgres SQL server, for example, has over seven years of recorded development and communication activity. We mined data from both the source code repository and the mailing list archives to examine the relationship between communication and development in Postgres. Along the way, we had to deal with the difficult challenge of resolving email aliases. We used a number of social network analysis measures and statistical techniques to analyze this data. We present our findings in this paper.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author><author><style face="normal" font="default" size="100%">Amor, Juan Jose</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining large software compilations over time: another perspective of software evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">distributions</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">large software collections</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">sloc</style></keyword><keyword><style  face="normal" font="default" size="100%">sloccount</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">software integrators</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137986</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/3miningLarge.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">3–9</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">With the success of libre (free, open source) software, a new type of software compilation has become increasingly common. Such compilations, often referred to as 'distributions', group hundreds, if not thousands, of software applications and libraries written by independent parties into an integrated system. Software compilations raise a number of questions that have not been targeted so far by software evolution, which usually focuses on the evolution of single applications. Undoubtedly, the challenges that software compilations face differ from those found in single software applications. Nevertheless, it can be assumed that both, the evolution of applications and that of software compilations, have similarities and dependencies.In this sense, we identify a dichotomy, common to that in economics, of software evolution in the small (micro-evolution) and in the large (macro-evolution). The goal of this paper is to study the evolution of a large software compilation, mining the publicly available repository of a well-known Linux distribution, Debian. We will therefore investigate changes related to hundreds of millions of lines of code over seven years. The aspects that will be covered in this paper are size (in terms of number of packages and of number of lines of code), use of programming languages, maintenance of packages and file sizes.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weißgerber, Peter</style></author><author><style face="normal" font="default" size="100%">Diehl, Stephan</style></author><author><style face="normal" font="default" size="100%">Görg, Carsten</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining refactorings in ARGOUML</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">re-engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138028</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/175MiningRefactorings.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">175–176</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">In this paper we combine the results of our refactoring reconstruc- tion technique with bug, mail and release information to perform process and bug analyses of the ARGOUML CVS archive.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;To see if refactorings in ARGOUML have an effect on the occurrence of new bugs and on communication between the developers, we relate the refactorings to bug reports in ISSUEZILLA respectively to mails on the developer mailing list. &quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kagdi, Huzefa</style></author><author><style face="normal" font="default" size="100%">Yusuf, Shehnaaz</style></author><author><style face="normal" font="default" size="100%">Maletic, Jonathan I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining sequences of changed-files from version histories</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">change sequences</style></keyword><keyword><style  face="normal" font="default" size="100%">heuristics</style></keyword><keyword><style  face="normal" font="default" size="100%">kde</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">sequences</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137996</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/47MiningSequences.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">47–53</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Modern source-control systems, such as Subversion, preserve change-sets of files as atomic commits. However, the specific ordering information in which files were changed is typically not found in these source-code repositories. In this paper, a set of heuristics for grouping change-sets (i.e., log-entries) found in source-code repositories is presented. Given such groups of change-sets, sequences of files that frequently change together are uncovered. This approach not only gives the (unordered) sets of files but supplements them with (partial temporal) ordering information. The technique is demonstrated on a subset of KDE source-code repository. The results show that the approach is able to find sequences of changed-files.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Voinea, Lucian</style></author><author><style face="normal" font="default" size="100%">Telea, Alexandru</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining software repositories with CVSgrab</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsgrab</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">software visualization</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138024</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/167MiningSoftware.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">167–168</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Zeller, Andreas</style></author><author><style face="normal" font="default" size="100%">Whitehead,Jr., E. James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining version archives for co-changed lines</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">change management</style></keyword><keyword><style  face="normal" font="default" size="100%">graph</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138001</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/72MiningVersionArchives.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">72–75</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Files, classes, or methods have frequently been investigated in recent research on co-change. In this paper, we present a first study at the level of lines. To identify line changes across several versions, we define the annotation graph which captures how lines evolve over time. The annotation graph provides more fine-grained software evolution information such as life cycles of each line and related changes: &quot;Whenever a developer changed line 1 of version.txt she also changed line 25 of Library.java.&quot;</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Noll, J.</style></author><author><style face="normal" font="default" size="100%">Elliott, M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Multi-Modal Modeling, Analysis and Validation of Open Source Software Development Processes</style></title><secondary-title><style face="normal" font="default" size="100%">Intern. J. Internet Technology and Web Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">empirical studies of software engineering</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software development</style></keyword><keyword><style  face="normal" font="default" size="100%">process modeling</style></keyword><keyword><style  face="normal" font="default" size="100%">requirements processes</style></keyword><keyword><style  face="normal" font="default" size="100%">software process</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Scacchi-Jensen-Noll-Elliott-OSSC05.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">49-63</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Staring, Knut</style></author><author><style face="normal" font="default" size="100%">Titlestad, Ola</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Networks of Open Source Health Care Action</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Networks of Open Source Health Care Action.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">135 - 141</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper reports on an effort to create a network of both developers and users of a public health information system. Through an analysis of capacity, recruitment, and power in the network, issues related to choice of technologies, global-local tensions, and parameters of institutional collaboration, we illustrate a number of challenges. Comparing OSS principles to a “Networks of Action” approach, conditions for learning in organizing training and development of software with participants from Africa, Asia, and Europe, as well as the involvement of advanced students in such efforts are discussed.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Iannacci, Federico</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">On the Weickian Model in the Context of Open Source Software Development: Some Preliminary Insights</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/On the Weickian Model in the Context.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">3 - 8</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Despite being regarded as a path-breaking model of organising, Weick’s Enactment-Selection-Retention (ESR) model has been labelled too abstract a model find any practical applications. This paper attempts to show that exploration-oriented open source projects represent valuable case studies where Weick’s ESR model can be applied. By taking the Linux case study as a case in point, it is argued that a qualitative analysis of micro interactions (i.e. double interacts) might reveal broad organising patterns. Preliminary implications in terms of coordination and knowledge making processes are discussed in the final section.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Voinea, Lucian</style></author><author><style face="normal" font="default" size="100%">Telea, Alexandru</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An open framework for CVS repository querying, analysis and visualization</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsgrab</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution visualization</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">software visualization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1137993</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">33–39</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">We present an open framework for visual mining of CVS software repositories. We address three aspects: data extraction, analysis and visualization. We first discuss the challenges of CVS data extraction and storage, and propose a flexible way to deal with CVS implementation inconsistencies. We next present a new technique to enrich the raw data with information about artifacts showing similar evolution. Finally, we propose a visualization backend and show its applicability on industry-size repositories.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Singh, V</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author><author><style face="normal" font="default" size="100%">Rathi, D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Technical Support: A Look at Peer Help-Giving</style></title><secondary-title><style face="normal" font="default" size="100%">39th Annual Hawaii International Conference on System Sciences (HICSS'06)Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Kauia, HI, USA</style></pub-location><volume><style face="normal" font="default" size="100%">6</style></volume><pages><style face="normal" font="default" size="100%">118c</style></pages><abstract><style face="normal" font="default" size="100%">We explore online technical support of open source software by a study of postings to discussion boards. Our results indicate that there are several types of detail that are required by the help-givers to be able to diagnose and remediate help-seekers’ difficulties. As a result help interactions may iterate somewhat inefficiently. These findings are compared with studies of telephone technical help lines for commercial software, and library reference interviews. By considering certain rather problematic interactions we can identify ways to improve the process.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stewart, Katherine J.</style></author><author><style face="normal" font="default" size="100%">Darcy, David P.</style></author><author><style face="normal" font="default" size="100%">Daniel, Sherae L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Opportunities and Challenges Applying Functional Data Analysis to the Study of Open Source Software Evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Statistical Science</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">fda</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.jstor.org/stable/27645747</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><publisher><style face="normal" font="default" size="100%">Institute of Mathematical Statistics</style></publisher><volume><style face="normal" font="default" size="100%">21</style></volume><pages><style face="normal" font="default" size="100%">167-178</style></pages><abstract><style face="normal" font="default" size="100%">This paper explores the application of functional data analysis (FDA) as a means to study the dynamics of software evolution in the open source context. Several challenges in analyzing the data from software projects are discussed, an approach to overcoming those challenges is described, and preliminary results from the analysis of a sample of open source software (OSS) projects are provided. The results demonstrate the utility of FDA for uncovering and categorizing multiple distinct patterns of evolution in the complexity of OSS projects. These results are promising in that they demonstrate some patterns in which the complexity of software decreased as the software grew in size, a particularly novel result. The paper reports preliminary explorations of factors that may be associated with decreasing complexity patterns in these projects. The paper concludes by describing several next steps for this research project as well as some questions for which more sophisticated analytical techniques may be needed.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;As part of a larger project, data were collected on 105 OSS	projects hosted online at Sourceforge (sf.net).&quot; &quot;...we limited our data collection to projects that use only the Java programming language and were listed in the Internet and System Networking domains.&quot; &quot;... only including these projects that use an OSI approved license...&quot; &quot;had to have posted at least one file on the Sourceforge site as of the time of our initial project selection Fall 2002&quot; &quot;Data were collected on the published release history of each project thatmet the screening criteria. Each release of each project was
analyzed to calculate CplXLCoh. The size of each release was measured using a calculation of the number of lines of code (LOC)&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gençer, Mehmet</style></author><author><style face="normal" font="default" size="100%">Oba, Beyza</style></author><author><style face="normal" font="default" size="100%">Özel, Bülent</style></author><author><style face="normal" font="default" size="100%">Tunalıoğlu, V.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Organization of Internet Standards</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Organization of Internet Standards.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">267 - 272</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this study we look at a body of standards documents in RFCs(Request For Comments) of IETF (Internet Engineering Task Force). The cross references between these documents form a network. Approaches from social network analysis are deployed to assess centrality of artifacts in this network and identify cohesive subgroups and levels of cohesion. Our results demonstrate major groups centered around key standard tracks, and application of network metrics reflect different levels of cohesion for these groups. As application of these techniques in such domains is unusual, possible uses in open source projects for strategizing are discussed.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ven, Kris</style></author><author><style face="normal" font="default" size="100%">Verelst, Jan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Organizational Adoption of Open Source Server Software by Belgian Organizations</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/The Organizational Adoption of OSS Server.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">111 - 122</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study reports on five case studies in Belgian organizations that currently use open source server software. Respondents were asked about their motivation to use open source server software. Our results indicate that the lower cost, high reliability and availability of external support are the prime reasons why organizations use open source software. The often claimed advantage of open source software of having access to the source code was found relevant only for those organizations who perform development based on open source software. Some factors that were found relevant in previous studies (such as the support of standards) were however deemed less important by the organizations in our sample.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Schofield, Andrew</style></author><author><style face="normal" font="default" size="100%">Cooper, Grahame</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Participation in Free and Open Source Communities: An Empirical Study of Community Members’ Perceptions</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Participation in free and open source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">221 - 231</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Although the defining factors of Free and Open Source Software (FOSS) are generally seen as the availability and accessibility of the source code, it is what these facilitate that is perhaps of more significance. Source code availability allows the sharing of code, skills, knowledge, and effort, focused on a particular piece of software under development. The result of this is the FOSS community, which although often perceived as a single group, is actually many small groups, each bound by a common interest in a particular piece of software and using the Internet as a communication medium. Although there have been studies focusing on the motivation of FOSS developers to contribute to software, there has been little investigation into the motives, attitudes, and the culture within the communities as a whole. There is much more to most of these communities than software development. Many also have extensive support networks for the use of software, portals for research, and social facilities. This paper describes the results of an investigation into how FOSS community members perceive the communities that they belong to, their reasons for being in the community, and the manner in which they participate.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Lings, Brian</style></author><author><style face="normal" font="default" size="100%">Lindqvist, Edvin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Perceptions and Uptake of Open Source in Swedish Organisations</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Perceptions and Uptake of Open Source.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">155 - 163</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">There are many different ways in which Open Source ideas can be adopted by business, and influence the way in which companies do business. A number of different surveys have been conducted in different countries with the purpose of understanding the state of practice with respect to Open Source in companies. A number of different business models have been observed, ranging from the use of Open Source infrastructure products to basing a company’s entire business model on Open Source. In this paper we report on a study of the perceptions of Open Source and the uptake of open source products and development models in Swedish companies. We investigate this from the standpoint of stakeholders in those companies which have an expressed interest in Open Source, allowing a more in-depth analysis of the extent to which Open Source has influenced business thinking. From our analysis we find that uptake is much higher than reported in earlier studies, but is still concentrated in SMEs, consistent with the findings of previous studies. There is increased evidence of interest beyond the simple use of OS components at the (LAMP) infrastructure level. In particular, a significant proportion of the companies are in a symbiotic relationship with the OS community, supporting both through participation in existing projects and the release of new software under OS licences.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Knab, Patrick</style></author><author><style face="normal" font="default" size="100%">Pinzger, Martin</style></author><author><style face="normal" font="default" size="100%">Bernstein, Abraham</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Predicting defect densities in source code files with decision tree learners</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">data mining</style></keyword><keyword><style  face="normal" font="default" size="100%">decision tree learner</style></keyword><keyword><style  face="normal" font="default" size="100%">defect density</style></keyword><keyword><style  face="normal" font="default" size="100%">defect prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">prediction</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138012</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/119Predicting.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">119–125</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">With the advent of open source software repositories the data available for defect prediction in source files increased tremendously. Although traditional statistics turned out to derive reasonable results the sheer amount of data and the problem context of defect prediction demand sophisticated analysis such as provided by current data mining and machine learning techniques.In this work we focus on defect density prediction and present an approach that applies a decision tree learner on evolution data extracted from the Mozilla open source web browser project. The evolution data includes different source code, modification, and defect measures computed from seven recent Mozilla releases. Among the modification measures we also take into account the change coupling, a measure for the number of change-dependencies between source files. The main reason for choosing decision tree learners, instead of for example neural nets, was the goal of finding underlying rules which can be easily interpreted by humans. To find these rules, we set up a number of experiments to test common hypotheses regarding defects in software entities. Our experiments showed, that a simple tree learner can produce good results with various sets of input data.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bart Massey</style></author><author><style face="normal" font="default" size="100%">Keith Packard</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Regurgitate: Using GIT For F/LOSS Data Collection</style></title><secondary-title><style face="normal" font="default" size="100%">1st Workshop on Public Data about Software Development (WoPDaSD 2006)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">cvsanaly</style></keyword><keyword><style  face="normal" font="default" size="100%">git</style></keyword><keyword><style  face="normal" font="default" size="100%">history</style></keyword><keyword><style  face="normal" font="default" size="100%">promise</style></keyword><keyword><style  face="normal" font="default" size="100%">regurgitate</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/massey.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">We have created a new tool, regurgitate, for importing CVS repositories into the GIT source code management system. Important features of GIT include great expressiveness in capturing relationships between revisions and across files as well as extremely high-speed processing. These features make GIT an ideal platform for gathering detailed longitudinal metrics for open source projects. The availability of regurgitate facilitates using GIT as an analysis tool for that majority of open source projects that keep their repositories in CVS. In particular, GIT is fast enough that it is practical to replay the entire development history of a project commit-at-a-time, collecting metrics at each step. We demonstrate this process for a simple metric and a collection of benchmark F/LOSS repositories.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tuunanen, Timo</style></author><author><style face="normal" font="default" size="100%">Koskinen, Jussi</style></author><author><style face="normal" font="default" size="100%">Kärkkäinen, Tommi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Retrieving Open Source Software Licenses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">license</style></keyword><keyword><style  face="normal" font="default" size="100%">license analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">reuse</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Retrieving Open Source Software Licenses.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">35 - 46</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open Source Software maintenance and reuse require identifying and comprehending the applied software licenses. This paper first characterizes software maintenance, and open source software (OSS) reuse which are particularly relevant in this context. The information needs of maintainers and reusers can be supported by reverse engineering tools at different information retrieval levels. The paper presents an automated license retrieval approach called ASLA. User needs, system architecture, tool features, and tool evaluation are presented. The implemented tool features support identifying source file dependencies and licenses in source files, and adding new license templates for identifying licenses. The tool is evaluated against another tool for license information extraction. ASLA requires the source code as available input but is otherwise not limited to OSS. It supports the same programming languages as GCC. License identification coverage is good and the tool is extendable.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Basu, Amit</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Robust Open Source Exchange for Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A Robust Open Source Exchange.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">99 - 108</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper addresses the development of mechanisms for the creation of OSSD exchanges that could be used by developers across any geographical range, as long as all the developers can interact via some open network infrastructure such as the Internet. The structure of these exchanges can range from public repositories such as Sourceforge.net to intra-organizational forums for software development within an enterprise. We examine in particular the structure of an exchange model based on protocols for a robust online marketplace.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Barbara Scozzi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The role of mental models in FLOSS development work practices</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/The role of mental medels.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">91 - 97</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Shared understandings are important for software development as they guide to effective individual contributions to, and coordination of, the software development process. In this paper, we present the theoretical background and research design for a proposed study on shared mental models within Free/Libre Open Source Software (FLOSS) development teams. In particular, we plan to perform case studies on several projects and to use cognitive maps analysis to represent and compare the mental models of the involved members so as to gauge the degree of common knowledge and the development of a collective mind as well as to better understand the reasons that underlie team members actions and the way common mental models, if any, arise.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A study of the contributors of PostgreSQL</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">patches</style></keyword><keyword><style  face="normal" font="default" size="100%">postgresql</style></keyword><keyword><style  face="normal" font="default" size="100%">revision history</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138022</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/163AStudyOf.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">163–164</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the project's CVS repository.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A study on the introduction of Open Source Software in the Public Administration</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A study on the introduction of OSS.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">165 - 171</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper reports about a study on the introduction of Open Source Software (OSS) in a Public Administration located in Europe. The Public Administration examined has introduced OSS as a means to save on the license costs and to have a larger space for customisation purposes. The adoption of new software may have an impact on the employees’ productivity that need to be addressed.
In this article, we compare the usage of OpenOffice.org and Microsoft Office. Data about the usual office activities performed by the users participating to the experimentation have been collected by means of an automated non-invasive data collection tool. The result of this study reports a similar usage pattern of both suites in terms of workload, but a different approach in using functionalities provided by each software. A further analysis on the life cycles of documents elaborated with the office suites seems to validate the similarities among the software solutions examined.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors></contributors><titles><title><style face="normal" font="default" size="100%">A tool for the measurement, storage, and pre-elaboration of data supporting the release of public datasets</style></title><secondary-title><style face="normal" font="default" size="100%">1st Workshop on Public Data about Software Development (WoPDaSD 2006)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><abstract><style face="normal" font="default" size="100%">The big number of projects producing open source software provides researches with the possibility to measure software artefacts, thus producing a huge amount of data that are available for analysis. In order to be efficient and reliable, the process of data retrieval and analysis needs to be adequately supported by tools. In particular, measurement tools should guarantee that a large amount of artefacts are measured in a coherent and efficient way. They should also guarantee that the delivered measures have a well specified structure and meaning, which should be agreed upon by the community of researchers interested in analysing the data. A problem that such tools have to face is that all the elements involved are highly variable: the data source can be available in different versions; the measures to be carried out can be defined in (often only slightly) different ways; it is usually different the output required by different types of analysis. Another non trivial problem is that measured data have to be stored persistently in a way that lets the user not only retrieve the data, but also the meta-data describing the measurement themselves. In this paper we describe a tool that addresses the requirements described above, and present a first implementation that satisfies several of such requirements. </style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Di Cerbo, Francesco</style></author><author><style face="normal" font="default" size="100%">Favara, Daniele</style></author><author><style face="normal" font="default" size="100%">Scotto, Marco</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author><author><style face="normal" font="default" size="100%">Vernazza, Tullio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A tool to support the introduction of GNU/Linux desktop system in a professional environment</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/A tool to support the introduction.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">253 - 260</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The introduction of a GNU/Linux-based desktop system in a large company is often problematic, in terms of technical issues but especially for employees’ training costs. Mainly, these obstacles are represented by different hardware configurations that might require several ad-hoc activities to adapt a standard release to the specific environment, including company’s application profile. On the other hand, GNU/Linux live distributions provide to the users’ community new and interesting capabilities, as self-configuration and better usability, but loosing compatibility with original distributions, that is unaffordable in professionals scenarios. DSS (Debased Scripts Set) is an answer to both questions. It is a live distribution that includes an unmodified Debian-based Linux release and a modular-designed file system.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jin Xu</style></author><author><style face="normal" font="default" size="100%">Gao, Yongqin</style></author><author><style face="normal" font="default" size="100%">Christley, S.</style></author><author><style face="normal" font="default" size="100%">Madey, G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Topological Analysis of the Open Souce Software Development Community</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 38th Annual Hawaii International Conference on System Sciences</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">roles</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">srda</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.132.6830&amp;rep=rep1&amp;type=pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/xuGao.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE</style></publisher><pub-location><style face="normal" font="default" size="100%">Big Island, HI, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><abstract><style face="normal" font="default" size="100%">The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysis of Open Source Software developers by studying the entire development community at SourceForge [26]. Statistics and social network properties are explored to find collaborations and the effects of different members in the OSS development community. Small world phenomenon and scale free behaviors are found in the SourceForge development network. These topological properties may potentially explain the success and efficiency of OSS development practices. We also infer from our analysis that weakly associated but contributing co-developers and active users may be an important factor in OSS development.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We extracted data from a 2003 data dump obtained from SourceForge. &quot;
roles</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Simmons, Gregory</style></author><author><style face="normal" font="default" size="100%">Dillon, Tharam</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards an Ontology for Open Source Software Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2006: Open Source Systems (IFIP 2.13)</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">IFIP International Federation for Information Processing</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Towards an Ontology for OSS Development.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pages><style face="normal" font="default" size="100%">65 - 75</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Software development is a knowledge intensive process and the information generated in open source software development projects is typically housed in a central Internet repository. Open source repositories typically contains vast amounts of information, much of it unstructured, meaning that even if a question has previously been discussed and dealt with it is not a trivial task to locate it. This can lead to rework and confusion amongst developers and possibly deter new developers from getting involved in the project in the first place. This paper will present the case for an open source software development ontology. Such an ontology would enable better categorization of information and the development of sophisticated knowledge portals in order to better organize community knowledge and increase efficiency in the open source development process.
</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Peter C. Rigby</style></author><author><style face="normal" font="default" size="100%">Storey, Margaret-Anne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using evolutionary annotations from change logs to enhance program comprehension</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">annotations</style></keyword><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracking</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">evolutionary</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing lists</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138020</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/159UsingEvolutionary.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">159–162</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">Evolutionary annotations are descriptions of how source code evolves over time. Typical source comments, given their static nature, are usually inadequate for describing how a program has evolved over time; instead, source code comments are typically a description of what a program currently does. We propose the use of evolutionary annotations as a way of describing the rationale behind changes applied to a given program (for example &quot;These lines were added to ...&quot;). Evolutionary annotations can assist a software developer in the understanding of how a given portion of source code works by showing him how the source has evolved into its current form.In this paper we describe a method to automatically create evolutionary annotations from change logs, defect tracking systems and mailing lists. We describe the design of a prototype for Eclipse that can filter and present these annotations alongside their corresponding source code and in workbench views. We use Apache as a test case to demonstrate the feasibility of this approach.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kakimoto, Takeshi</style></author><author><style face="normal" font="default" size="100%">Monden, Akito</style></author><author><style face="normal" font="default" size="100%">Kamei, Yasutaka</style></author><author><style face="normal" font="default" size="100%">Tamada, Haruaki</style></author><author><style face="normal" font="default" size="100%">Tsunoda, Masateru</style></author><author><style face="normal" font="default" size="100%">Matsumoto, Ken-ichi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using software birthmarks to identify similar classes and major functionalities</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">class</style></keyword><keyword><style  face="normal" font="default" size="100%">file</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">multi-dimensional scaling</style></keyword><keyword><style  face="normal" font="default" size="100%">similarity</style></keyword><keyword><style  face="normal" font="default" size="100%">software birthmark</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138026</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/171UsingSoftware.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">171–172</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Canfora, Gerardo</style></author><author><style face="normal" font="default" size="100%">Cerulo, Luigi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Where is bug resolution knowledge stored?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2006 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '06</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">argouml</style></keyword><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">impact analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">mining challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">mining software repositories</style></keyword><keyword><style  face="normal" font="default" size="100%">msr challenge</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1137983.1138032</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/183WhereIsBug.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">183–184</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-397-2</style></isbn><abstract><style face="normal" font="default" size="100%">ArgoUML uses both CVS and Bugzilla to keep track of bug-fixing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by inserting the id number of the bug in the CVS commit notes. This relationship reveals useful to predict code entities impacted by a new bug report.In this paper we analyze ArgoUML software repositories with a tool, we have implemented, showing what are Bugzilla fields that better predict such impact relationship, that is where knowledge about bug resolution is stored.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jones, M.C.</style></author><author><style face="normal" font="default" size="100%">Rathi, D.</style></author><author><style face="normal" font="default" size="100%">Twidale, M.B</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Wikifying your interface:  Facilitating Community-Based Interface Translation</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 6th ACM conference on Designing Interactive systems  - DIS '06</style></secondary-title><short-title><style face="normal" font="default" size="100%">DIS '06</style></short-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM Press</style></publisher><pages><style face="normal" font="default" size="100%">321-330</style></pages><isbn><style face="normal" font="default" size="100%">1595933670</style></isbn><abstract><style face="normal" font="default" size="100%">We explore the application of a wiki-based technology and
style of interaction to enabling the incremental translation
of a collaborative application into a number of different
languages, including variant English language interfaces
better suited to the needs of particular user communities.
The development work allows us to explore in more detail
the design space of functionality and interfaces relating to
tailoring, customization, personalization and localization,
and the challenges of designing to support ongoing
incremental contributions by members of different use
communities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sherae Daniel</style></author><author><style face="normal" font="default" size="100%">Ritu Agarwal</style></author><author><style face="normal" font="default" size="100%">Katherine Stewart</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An absorptive capacity perspective of open source software development group performance</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">NotreDameArchive</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assessing the health of open source communities</style></title><secondary-title><style face="normal" font="default" size="100%">Computer</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><number><style face="normal" font="default" size="100%">5</style></number><volume><style face="normal" font="default" size="100%">39</style></volume><pages><style face="normal" font="default" size="100%">89-91</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><accession-num><style face="normal" font="default" size="100%">WOS:000237454500016</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><tertiary-authors><author><style face="normal" font="default" size="100%">Acuna, S.T.</style></author><author><style face="normal" font="default" size="100%">Sanchez-Segura, M.I.</style></author></tertiary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Discovering, Modeling, and Reenacting Open Source Software Development Processes</style></title><secondary-title><style face="normal" font="default" size="100%">New Trends in Software Process Modeling</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">Series in Software Engineering and Knowledge Engineering</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><volume><style face="normal" font="default" size="100%">18</style></volume><pages><style face="normal" font="default" size="100%">1-20</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Eileen Allen</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Wei, Kangning</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Emergent decision-making practices in technology-supported self-organizing distributed teams</style></title><secondary-title><style face="normal" font="default" size="100%">the International Conference on Information Systems (ICIS 2006)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><pub-location><style face="normal" font="default" size="100%">Milwaukee, WI, 10–13 Dec</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Eileen Allen</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Emergent Decision-making Practices in Technology-Supported Self-Organizing Distributed Teams</style></title><secondary-title><style face="normal" font="default" size="100%">Twenty Seventh International Conference on Information Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/decision_making_practices.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">1–12</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We seek to identify work practices that make technology-supported self-organizing distributed (or virtual) teams (TSSODT for short) effective in producing outputs satisfactory to their sponsors, meeting the needs of their members and continuing to function. A particularly important practice for team effectiveness is decision making: are the right decisions made at the right time to get the work done in a way that satisfies team sponsors, keeps contributors happy and engaged, and enables continued team success? In this research-in-progress paper, we report on an inductive qualitative analysis of 120 decision episodes taken by 2 Free/libre Open Source Software development teams (the completed paper will include 360 episodes from 6 teams). Our analysis revealed differences in the performance of the two teams that seems to be related to differences in overall project effectiveness.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author><author><style face="normal" font="default" size="100%">Enrico Zini</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Empirical Study on Implementing FLOSS in Schools</style></title><secondary-title><style face="normal" font="default" size="100%">Social Informatics: An Information Society for All? In Remembrance of Rob Kling, the proceedings of the 7th 'Human Choice and Computers' conference</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/LinZini_HCC7.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Springer Science and Business Media</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software and supports the needs of local users better. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization - including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">FLOSSmole: A Collaborative Repository for FLOSS Research Data and Analyses</style></title><secondary-title><style face="normal" font="default" size="100%">International Journal of Information Technology and Web Engineering</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">1</style></volume><pages><style face="normal" font="default" size="100%">17-26</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">computational</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ibrahim Izlem Gozukeles</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free and open source software hackers in Turkey</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/WP.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">n/a</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In recent years, there has been growing interest of governments and firms for Free and Open Source Software (FOSS). However, FOSS is still a puzzlement for a wide spectrum of academic disciplines. Social scientists ask why FOSS hackers participate in FOSS if they do not get any monetary rewards. On the other hand firms ask, how a firm can earn money from FOSS. In this study, motivations of FOSS hackers and firms are taken as an interrelated phenomenon. This study discusses FOSS from the view of hackers in Turkey. In that respect, social conditions that make hackers voluntarily contribute to the FOSS projects and their relationship with the commercial world are explored. 1</style></abstract><work-type><style face="normal" font="default" size="100%">Working Paper</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Katherine Stewart</style></author><author><style face="normal" font="default" size="100%">Ammeter, A. P.</style></author><author><style face="normal" font="default" size="100%">Maruping, L. M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Impacts of license choice and organizational sponsorship on user interest and development activity in open source software projects</style></title><secondary-title><style face="normal" font="default" size="100%">Information Systems Research</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">17</style></volume><pages><style face="normal" font="default" size="100%">126-144</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">What differentiates successful from unsuccessful open source software projects? This paper develops and tests a model of the impacts of license restrictiveness and organizational sponsorship on two indicators of success: user interest in, and development activity on, open source software development projects. Using data gathered from Freshmeat.net and project home pages, the main conclusions derived from the analysis are that (1) license restrictiveness and organizational sponsorship interact to influence user perceptions of the likely utility of open source software in such a way that users are most attracted to projects that are sponsored by nonmarket organizations and that employ nonrestrictive licenses, and (2) licensing and sponsorship address complementary developer motivations such that the influence of licensing on development activity depends on what kind of organizational sponsor a project has. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000238492700003</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 1</style></notes><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">model</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Klemens, B.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Math You Can't Use: Patents, Copyright, and Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><publisher><style face="normal" font="default" size="100%">Brookings Institution Press</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">book</style></custom3><label><style face="normal" font="default" size="100%">klemens2006</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Inoue, K.</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Social dynamics of free and open source team communications</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the IFIP 2nd International Conference on Open Source Software, Lake Como, Italy</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">computational</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Madhavji, N.H.</style></author><author><style face="normal" font="default" size="100%">Lehman, M.M.</style></author><author><style face="normal" font="default" size="100%">Ramil, J.F.</style></author><author><style face="normal" font="default" size="100%">Perry, D.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding Free/Open Source Software Evolution</style></title><secondary-title><style face="normal" font="default" size="100%">Software Evolution and Feedback: Theory and Practice</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2006</style></year></dates><publisher><style face="normal" font="default" size="100%">John Wiley and Sons Inc.</style></publisher><pub-location><style face="normal" font="default" size="100%">New York</style></pub-location><pages><style face="normal" font="default" size="100%">181-206</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lorenzo Benussi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysing the technological history of the Open Source Phenomenon: Stories from the Free Software Evolution</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/benussi.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The Free Libre Open Source Software represents an outstanding example of open development model of technological knowledge. It has been studied in several researches that produced valuable illustrations of the way it works. Our understanding of its principal features is growing exponentially and an entire new literature on open source has been created. However there appears to be an important gap in the literature: the origin of the phenomenon. The paper attempts to tackle this issue by analyzing the long-term technological history of Free Open Source Software; the main research questions at stake are: is the phenomenon completely new? and if it is not totally new, where it comes form? and, more generally, how open source software developed over time? As a consequence the present work focuses primarily on the analysis of the fee/open source software history of technological change over a period of almost sixty years. I adopted a multidisciplinary approach to analyse the network of relations emerging between inventions and technological innovations, as well as economic determinants and intellectual property rights regimes throughout the period considered. Thus, I attempt to investigate the origins of the phenomenon as a way of understanding its evolution.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Juho Lindman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Effects of Open Source Software on the Business Patterns of Software Industry</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lindman.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software is a phenomenon that has potential to change the traditional patterns of business behavior. Research committed so far has not evaluated the entire scale of potential changes, which is the purpose of this explorative thesis. Previous literature on the subject can be divided into history of the phenomenon, explaining the nature of the phenomenon, and a more general discussion about strategies and business models in the software business. By using these theories this thesis provides a framework for analysing the entire phenomenon. The framework is put to use in the empirical part. Data consist of interviews of experts in the field. An analysis of the data is done using narrative methods. The analysis yield eleven narratives that describe the phenomenon. Four of the narratives reveal effects. On the basis of the responses gathered, open source software can change competition environment, customer expectations, the importance of competence, and platform thinking.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Marleen Wynants</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How open is the future (Book - Under creative Commons</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">There are two reasons why the free and open-source software issue has become such an inspirational and powerful force today: the rise of the Internet and the growing tendency to protect all intellectual property. Internet technology made it possible to handle massive decentralized projects and irreversibly changed our personal communication and information research. Intellectual property, on the other hand, is a legal instrument which - due to recent excesses - became the symbol of exactly the opposite of what it had been developed for: the protection of the creative process. As a result, free-thinking programmers, scientists, artists, designers, engineers and scholars are daily trying to come up with new ways of creating and sharing knowledge.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robert Cooksey</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">I Walk the Open Road: Toward an Open Source Philosophy</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/cooksey.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper addresses the concept of &quot;Open Source&quot; in a philosophical way. It argues that open source is a virtual entity with ontological significance beyond the realm of the software movement that granted its naming. The paper includes an examination of the technical language surrounding open source software, progresses through a philosophical exploration of this language removed from the specificity of computer languages and technologies, and then returns to an analysis of The Open Source Definition in the light of the philosophical investigation.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrew Watson</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Reputation in Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/watson.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The 1990s and early 2000s have seen the dramatic rise of open source software, with the Linux operating system as the most salient example. This article focuses on the role of reputation in open source. It describes the importance of the reputations of hackers, software vendors, open source projects, and the open source movement. Although reputation has long been used as an explanation of hacker motivation, this article applies the concept of reputation at multiple levels, and identifies the inter-level relations.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nicholas Economides</style></author><author><style face="normal" font="default" size="100%">Evangelos Katsamakas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Linux vs. Windows: A comparison of application and platform innovation incentives for open source and proprietary software platforms</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/economideskatsamakas.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper analyzes and compares the investment incentives of platform and application developers for Linux and Windows. We find that the level of investment in applications is larger when the operating system is open source rather than proprietary. The comparison of the levels of investment in the operating systems depends, among others, on reputation effects and the number of developers. The paper also develops a short case study comparing Windows and Linux and identifies new directions for open source software research.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nicolas Jullien</style></author><author><style face="normal" font="default" size="100%">Jean-Beno\^ıt Zimmermann</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">New approaches to intellectual property : from open software to knowledge based industrial activities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/jullienzimmermann.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We analyze the question of intellectual property in computer software, showing that both copyright and patents do not fit to the specificities and needs of this industry. The alternative model of Open Source Software, based on a very new juridical concept called GPL &quot;General Public License&quot;, tends to take a growing importance. We explain its main characteristics, which consist to impose to the producers to disclose the source-code of the concerned programs and of any further improvement if they re-distribute/resell it. We show that by doing that it introduces a totally different approach of intellectual property within industrial strategies, based on a weaker intellectual protection. We discuss the consequences of such a movement in intistitutional and public policy terms and we enlarge the approach to understand its exemplariness, in the context of a knowledge based economy, for a growing number of industrial activities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Process Maturity and the Success of Free Software Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/michlmayr1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The success of free software and open source projects has increased interest in utilizing the open source model for mature software development. However, the ad hoc nature of open source development may result in poor quality software or failures for a number of volunteer projects. In this paper, projects from SourceForge are assessed to test the hypothesis that there is a relationship between process maturity and the success of free software and open source projects. This study addresses the question of whether the maturity of particular software processes differs in unsuccessful and unsuccessful projects. Processes are identified which are key factors in successful free software projects. The insights gained from this study can be used improve the software process used by free software projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nicholas Economides</style></author><author><style face="normal" font="default" size="100%">Evangelos Katsamakas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Two-sided competition of proprietary vs. open source technology platforms and the implications for the software industry</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/economideskatsamakas2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Technology platforms, such as Microsoft Windows, are the hubs of technology industries. We develop a framework to characterize the optimal two-sided pricing strategy of a platform firm, that is, the pricing strategy towards the direct users of the platform as well as towards firms offering applications that are complementary to the platform. We compare industry structures based on a proprietary platform (such as Windows) with those based on an open-source platform (such as Linux) and analyze the structure of competition and industry implications in terms of pricing, sales, profitability, and social welfare. We find that, when the platform is proprietary, the equilibrium prices for the platform, the applications, and the platform access fee for applications may be below marginal cost, and we characterize demand conditions that lead to this. The proprietary applications sector of an industry based on an open source platform may be more profitable than the total profits of a proprietary platform industry. When users have a strong preference for application variety, the total profits of the proprietary industry are larger than the total profits of an industry based on an open source platform. The variety of applications is larger when the platform is open source. When a system based on an open source platform with an independent proprietary application competes with a proprietary system, the proprietary system is likely to dominate the open source platform industry both in terms of marketshare and profitability. This may explain the dominance of Microsoft in the market for PC operating systems.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Francesca Antonacci</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free software development communities as a pedagogic model</style></title><secondary-title><style face="normal" font="default" size="100%">Condividere la conoscenza. L'esempio del software libero</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/antonacci.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Unicopli</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The pedagogic interest arising from the emergence of free software development communities is twofold. Firstly, in their production practices these communities set out formative processes as well as educational ones. These practices characterise these communities and are not accessory, to the point that without them the communities could not survive. Secondly, these communities are interesting as they make up a particularly rich epistemological model for the understanding of formative, educational and didactical themes. Having embraced the hacker culture, these communities promote and create an incentive to the free circulation of knowledge without protectionist barriers. However, freedom of knowledge alone is not enough, both in the educational and productive fields, unless it is introduced in an organisational model promoting the participation and engagement of the individuals. The communities of free software development are a particularly interesting organisational model because their structure, based on co-operation and solidarity and opposing centralisation, promote the participation of programmers and users all over the world. Thanks to this kind of organisation, which owes much to a model of delegating leadership, authoritative but not authoritarian, charismatic but not idealised these communities are putting together a very large number of work groups. These are geographically, methodologically and culturally non-homogeneous groups, which despite all predictions create highly competitive products of high quality.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">De Souza, Cleidson</style></author><author><style face="normal" font="default" size="100%">Jon Froehlich</style></author><author><style face="normal" font="default" size="100%">Paul Dourish</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Seeking the Source: Software Source Code as a Social and Technical Artifact</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/desouza.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In distributed software development, two sorts of dependencies can arise. The structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover the structures of software projects, and the ways in which development processes are inscribed into software artifacts. We show how a range of organizational processes and arrangements can be uncovered in software repositories, with implications for collaborative work in large distributed groups such as open source communities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">F. Barcellini</style></author><author><style face="normal" font="default" size="100%">F. Detienne</style></author><author><style face="normal" font="default" size="100%">J. M. Burkhardt</style></author><author><style face="normal" font="default" size="100%">W. Sack</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Thematic Coherence and Quotation Practices in Open Source Software design-oriented online discussions</style></title><secondary-title><style face="normal" font="default" size="100%">Group '05 Conference Proceedings</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Barcellinietal.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper presents an analysis of online discussions in Open Source Software (OSS) design. The objective of our work is to understand and model the dynamics of OSS design that take place in mailing list exchanges. We show how quotation practices can be used to locate design relevant data in discussion archives. OSS developers use quotation as a mechanism to maintain the discursive context. To retrace thematic coherence in the online discussions of a major OSS project, Python, we follow how messages are linked through quotation practices. We compare our quotation-based analysis with a more conventional analysis: a thread-based of the reply-to links between messages. The advantages of a quotation-based analysis over a thread-based analysis are outlined. Our analysis reveals also the links between the social structure and elements in the discussion space and how it shapes influence in the design process.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Li, Mingshu</style></author><author><style face="normal" font="default" size="100%">Boehm, Barry</style></author><author><style face="normal" font="default" size="100%">Osterweil, Leon J.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Experiences in Discovering, Modeling, and Reenacting Open Source Software Development Processes</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process Workshop (SPW05): Unifying the Software Process Spectrum</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Springer-Verlag</style></publisher><pub-location><style face="normal" font="default" size="100%">Beijing, China</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jonathon Frost</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Some Economic &amp; Legal Aspects of Open Source Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/frost.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The emergence of open source software as a viable economic model has risen to the forefront in the debate on the future of the information technology industry. However, at first glance, the open source software development model is strikingly enigmatic and counterintuitive. To help better understand this phenomenon, this paper, through market data and economic theory, proceeds to ask and answer three related questions. First, what is the economic relationship between open source software development communities and proprietary software firms? Second, what are the resulting effects on market innovation and innovation incentives? And third, what legal mechanisms allow for the sustainability of open source software and should they be expanded or reduced? This paper concludes that open source activity appears to be generating four economic effects, whose net effect on innovation in the software market is ambiguous.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Imhorst</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Anarchy and Source Code - What does the Free Software Movement have to do with Anarchism?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/imhorst.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">What does the hacker ethic have to do with anarchism? Why does Richard Stallman, an outstanding personality of the free software movement, described himself as an anarchist? We should not imagine the anarchists of the Free Software Movement to be like the cartoon image: A scruffy looking lunatic, with a crazy glint in his eyes and bristling with weapons. Instead of chaos, Stallman postulates a new form of order for the intellectual property in the terms of the hacker ethic - the access to knowledge should be free, decentralized, anti-bureaucratic and anti-authoritarian.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mathias Klang</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free software and open source: The freedom debate and its consequences (Published in First Monday)</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">To most outsiders the ethics of software is not something usually considered. To most proficient computer users with a passing interest in this question the ethics of software is recognised as one of the fundamental questions in the digital rights area. To most of the latter, terms such as free software, open source, and their derivatives (FLOSS, FOSS, Software Freedom) are interchangeable. Choosing one over the other is a matter of taste rather than politics. However, to most insiders the question is not one of taste. There is a fundamental difference between the two areas even if they share a similar root. Free software is not the same as open source. The two groups differ in their fundamental philosophical approach to software and its importance to society as a whole. This paper examines the two groups? differing philosophies and explores how their actions have affected software development, access to fundamental software infrastructure, and the development of the concept of freedom.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Gender issues in the FLOSS development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lin3_gender.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The FLOSS development is responding to the ICT development in various ways. This essay describes and analyses challenges (societal and organisational) and advantages (e.g. new models for mobile and collaborative work online), particularly regarding gender issues, encountered in the recent FLOSS development. The focus of the essay is not only on the claims made women in the existed FLOSS community about the tensions between male and female developers' interests and ways of doings, but also on the current obstacles against bringing more women, who are not technically competent, to participate in the FLOSS development. This paper concludes with suggestions on how to create rules and resources and the creation of a common FLOSS space for both genders.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matthias Stürmer</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Community Building</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/sturmer.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Building an active and helpful community around an open source project is a complex task for its leaders. Therefore investigations in this work are intended to define the optimum starting position of an open source project and to identify recommendable promoting actions by project leaders to enlarge community size in a healthy way. For this paper eight interviews with committed representatives of successful open source projects have led to over 12 hours of conversation about community building. Analysing the statements of these experienced community members exposed helpful activities that led to the presently prospering communities of their projects. Summarizing the conclusions of this qualitative research a table with conditions for successful open source project initialisation and a subject-level promotion matrix of community building could be created. They include suggestions o?n how to start a new open source project and how to improve and increase the community of an already advanced open source project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Norbert Bollow</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Webservice Protocol Design for Economic Liberty and Observability</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/bollow.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">One big potential benefit of the webservices paradigm is in reducing the costs of inter-firm business transactions. That should allow small and medium-sized enterprises to compete successfully with big firms. This paper considers specifically the economic needs of peer-to-peer business alliances, defined as multiparty business alliances which are not under the control of any single firm or any small group of alliance members, so that each participating firm has full economic liberty. This organisational form is appropriate for example for Free Software businesses. The main conclusions are that achieving economic observability of business transactions is of great importance, and that this is difficult to achieve with the Remote Procedure Calls paradigm of JINI or XML / HTTP / SOAP based webservices. The problem can be overcome by using the SXDF / QQP / QRPC suite of webservice protocols,</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alan MacCormack</style></author><author><style face="normal" font="default" size="100%">John Rusnak</style></author><author><style face="normal" font="default" size="100%">Carliss Baldwin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code (updated)</style></title></titles><keywords><keyword><style  face="normal" font="default" size="100%">complexity</style></keyword><keyword><style  face="normal" font="default" size="100%">cost</style></keyword><keyword><style  face="normal" font="default" size="100%">dependencies</style></keyword><keyword><style  face="normal" font="default" size="100%">functions</style></keyword><keyword><style  face="normal" font="default" size="100%">lines of code</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/maccormackrusnakbaldwin2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper reports data from a study that seeks to characterize the differences in design structure between complex software products. In particular, we use Design Structure Matrices (DSMs) to map the dependencies between the elements of a design and define metrics that allow us to compare the structures of different designs. We first use these metrics to compare the architectures of two software products - the Linux operating system and the Mozilla web browser - that were developed via contrasting modes of organization: specifically, open source versus proprietary development. We then track the evolution of Mozilla, paying particular attention to a purposeful &quot;re-design&quot; effort that was undertaken with the intention of making the product more &quot;modular.&quot; We find significant differences in structure between Linux and the first version of Mozilla, suggesting that Linux had a more modular architecture. We also find that the redesign of Mozilla resulted in an architecture that was significantly more modular than that of its predecessor, and indeed, than that of Linux. Our results, while exploratory, are consistent with a view that different modes of organization are associated with designs that possess different structures. However, we also illustrate that purposeful managerial actions can have a large impact on structure. This latter result is important given recent moves to release proprietary software into the public domain. These moves are likely to fail unless the product possesses an architecture that facilitates participation. Our paper provides evidence that a tightly-coupled design can be adapted to meet this objective.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;For each design, we report data on the number of source files, the number of dependencies, the density of the DSM (i.e., the number of dependencies per source file pair) the propagation cost and the clustered cost. We also provide data on the average complexity of source files, in terms of the number of functions and lines of code.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Janet Hope</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Biotechnology</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/hope.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Building on discussions with public and private sector industry participants, funding agencies, leaders of the free and open source software movement and scholars in a range of disciplines, this PhD thesis assesses the desirability and feasibility of extending open source principles to biotechnology research and development. It argues that &quot;open source biotechnology&quot; is both desirable and broadly feasible, and demonstrates that many of the essential elements of an embryonic open source movement are already present in this field.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christian Bac</style></author><author><style face="normal" font="default" size="100%">Olivier Berger</style></author><author><style face="normal" font="default" size="100%">Véronique Deborde</style></author><author><style face="normal" font="default" size="100%">Benoit Hamet</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Why and how-to contribute to libre software when you integrate them into an in-house application ?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 1st International Conference on Open Source Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><pages><style face="normal" font="default" size="100%">113–118</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free or open source software are common tools that everybody can use and customise at its convenience to create in-house applications. Using and customising free software is not sufficient to ensure that this in-house application will be maintainable at mid or long term. This paper draws lessons from our in-house project, the development of a groupware Web platform for researchers, to help defining a policy through which efficient contributions can be made to open source software so that the in-house projects may remain viable.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Process Modeling Across the Web Information Infrastructure</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process--Improvement and Practice</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July-September</style></date></pub-dates></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">10</style></volume><pages><style face="normal" font="default" size="100%">255-272</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><orig-pub><style face="normal" font="default" size="100%">Proc. 5th. Intern. Workshop on Software Process Simulation and Modeling, Edinburgh, Scotland, May 2004.</style></orig-pub></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stefano Comino</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From Planning to Mature: on the Determinants of Open Source Take Off</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Comino_Manenti_Parisi.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper we use data from SourceForge.net, the largest open source projects repository, to estimate the main determinants of the progress in the development of a stable and mature code of a software. We find that the less restrictive the licensing terms the larger the likelihood of reaching an advanced development status and that this effect is even stronger for newer projects. We also find that projects geared towards system administrators appear to be the more successful ones. The determinants of projects' development stage change with the age of the project in many dimensions, i.e. licensing terms, software audience and contents, thus supporting the common perception of opens source as a very dynamic phenomenon. The data seem to suggest that open source is evolving towards more commercial applications.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Benno Luthiger Stoll</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Fun and Software Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/BLuthiger_Fun_SoftwareDevel_OSS2005.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study gathered 1330 answers about fun and software development from open source developers as well as 114 answers from programmers working in commercial software projects. The analysis of these data proves that fun plays an important role when software developers decide to get engaged in an open source project. Moreover, the comparison of the answers gives evidence for the hypothesis that programming in an open source project is significantly more fun compared to the same activity under commercial conditions. The reasons for this fact are that open source projects are able to attract software developers with a credible project vision and that they can offer them an optimal challenge.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality Practices and Problems in Free Software Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">July</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/michlmayr_hunt_probert-quality_practices_problems.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free software and open source projects are often perceived to be of high quality. It has been suggested that the high level of quality found in some free software projects is related to the open development model which promotes peer review. While the quality of some free software projects is comparable to if not better than that of closed source software, not all free software projects are successful and of high quality. Even mature and successful projects face quality problems, some of which are related to the unique characteristics of free software and open source as a distributed development model based primarily on volunteers. In exploratory interviews performed with free software and open source developers, common quality practices as well as actual quality problems have been identified. The results of these interviews are presented in this paper to take stock of the current status of quality in free software projects and to act as a starting point for the implementation of quality process improvement strategies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sandeep Krishnamurthy</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Launching of Mozilla Firefox - A Case Study in Community-Led Marketing</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/sandeep2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Mozilla Firefox is a Free/Libre/Open Source (FLOSS) browser supported by the Mozilla Foundation. This browser was recently released and has met with considerable success- it has been downloaded more than 20 million times and has already taken considerable market share from its prime competitor- Microsoft?s Internet Explorer. In this paper, I chronicle how the efforts of 63000 volunteers led to a community successfully competing with a powerful corporation. I identify four factors as the key facilitators to Firefox? success- complacent competition, product superiority, presence of marketing leader and volunteer support.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Arti Rai</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open and Collaborative Biomedical Research: Theory and Evidence</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/rai.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Although a few commentators have discussed briefly the application of open source-type principles to biomedical research, they have not analyzed carefully how the model is actually being used. In this paper, I draw upon an ongoing, multi-year empirical inquiry into the role of intellectual property in computational biology and associated efforts to evaluate the extent to which the open and collaborative research model may promote socially desirable biomedical innovation ? that is, innovation that produces marginal health benefits in excess of its marginal costs.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sonali Shah</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Beyond Software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/shah4.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The &quot;community-based&quot; model has generated many of the innovations we use on a daily basis. The social structure created by this model has cultivated many entrepreneurial ventures and even seeded new industries and product categories. In this paper, I discuss three elements of this model and present four exemplars of the model that span fields and centuries. I conclude by reframing our view of the innovation process as driven by the activities of firms and research institutions and discussing implications for firms and policy.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stefan Behringer</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Provision of a Public Good with a direct Provision Technology and Large Number of Agents</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">January</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/behringer.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper provides a limit result for the provision of a public good in a mechanism design framework as the number of agents gets large. A canonical example for a public good that is produced with a direct provision technology is Open Source Software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christoph Lattemann</style></author><author><style face="normal" font="default" size="100%">Stefan Stieglitz</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Framework for Governance in Open Source Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">Jan</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Governance-in-OpenSourceProjects.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In recent years, the development of software in open source communities has attracted immense attention from research and practice. The idea of commercial quality, free software, and open source code accelerated the development of well-designed open source software such as Linux, Apache tools, or Perl.Intrinsic motivation, group identification processes, learning, and career concerns are the key drivers for a successful cooperation among the participants. These factors and most mechanisms of control, coordination, and monitoring forms of open source communities can hardly be explained by traditional organizational theories. In particular, the micro and macro structures of open source communities and their mode of operation are hardly compatible with the central assumption of the New Institutional Theory, like opportunistic behavior.The aim of this contribution is to identify factors that sustain the motivation of the community members over the entire life cycle of an open source project. Adequate coordination and controlling mechanisms for the governance in open source communities may be extracted.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Intrinsic motivations and profit-oriented firms in Open Source software. Do firms practise what they preach?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">February</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/rossi_motivations.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">A growing body of economic literature is exploring the incentives of the agents involved in the Open Source movement. However, most empirical analyses focus on individual developers and neglect firms that do business with Open Source software (Open Source firms). This paper contributes to the literature by providing empirical evidence on the incentives of firms that engage in Open Source activities. Data on firms? motivations were collected by a large-scale survey conducted on 146 Italian companies supplying Open Source (OS) solutions and show that intrinsic, community-based incentives do play a role. Nevertheless, these positive attitudes towards the values of the OS community, which are quite surprising by profit-oriented firms, are not in general put into practise. Discrepancy between attitudes and behaviours is a widely investigated phenomenon in social psychology literature. We explore its pattern in our sample, find that it does not concern all the respondents, and single out a group of firms adopting a more consistent behaviour. Our results are in line with the literature on individual motivations in organisations and Open Source business models .</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tom Chance</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Hacker Ethic and Meaningful Work</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/chance.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper begins with the following proposition: given that we spend a large proportion of our time working, a just society will provide or encourage meaningful work. Hackers have created and broadened spaces where working life can unfold freely, so a proper analysis of the Hacker Ethic ought to be of concern both to philosophers interested in meaningful work, and to academics researching hackers and the free software community. I proceed by first developing an understanding of the Hacker Ethic that highlights a central concern of my essay, that of orientations that I characterise as self-indulgent and social placing conflicting obligations upon individuals. Using Marx's conception of alienated as a basis, I go on to show how the Hacker Ethic can to an extent overcome these conflicts by developing a more rounded understanding of the ethic. Finally I raise some concerns for the underdeveloped field of the philosophy of hacking and free software that are particularly pertinent to the paper.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Krzysztof Klincewicz</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Innovativeness of open source software projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/klincewicz.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The paper addresses an ongoing debate about the innovativeness of open source projects and critically evaluates the innovative potential of 500 most active projects registered by SourceForge.net. The analysis is based on a proposed framework, distinguishing between radical inventions, technology / platform modifications, and marketing innovations. Research findings include relatively low levels of technical newness in the studies sample, alongside high interest of developers and users in the innovative projects. The article discusses the underlying mechanisms, restricting innovativeness of community-driven open source efforts, and postulates the establishment of an institution of idea brokers playing roles corresponding to venture capitalists in the commercial software domain.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Techno-Feminist Perspective on the Free/Libre Open Source Software Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">August</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lin5.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper tries to analyse the FLOSS development from a &quot;techno-feminist&quot; perspective (Wajcman 2004). Staying away from a reductionism that simplifies the gender issue in the FLOSS community to the level of a fight between men and women, the issues I attempt to address include not only the inequality that women face in computing, but also other inequalities that other users face mainly emerging from the power relationships between expert and lay (namely, developer and user) in software design. Instead of splitting women and men in the FLOSS development, this analysis helps motivate both men and women to work together, reduce the gender gap, and improve the disadvantaged statuses of women and a wider users community in the FLOSS development.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Federico Iannaci</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Coordination Processes in Open Source Software Development: The Linux Case Study</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/iannacci3.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">von Hippel, Eric</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Democratizing Innovation</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">MIT Press</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Innovation is rapidly becoming democratized. Users, aided by improvements in computer and communications technology, increasingly can develop their own new products and services. These innovating users–both individuals and firms–often freely share their innovations with others, creating user-innovation communities and a rich intellectual commons. In Democratizing Innovation, Eric von Hippel looks closely at this emerging user-centered innovation system. He explains why and when users find it profitable to develop new products and services for themselves, and why it often pays users to reveal their innovations freely for the use of all. The trend toward democratized innovation can be seen in software and information products–most notably in the free and open-source software movement–but also in physical products. He shows that product and service development is concentrated among &quot;lead users,&quot; who are ahead on marketplace trends and whose innovations are often commercially attractive. Von Hippel argues that manufacturers should redesign their innovation processes and systematically seek out innovations developed by users. User innovation has a positive impact on social welfare, and von Hippel proposes that government policies, including R&amp;D subsidies and tax credits, should be realigned to eliminate biases against it. An electronic version of this book is available under a Creative Commons license.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ilkka Tuomi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Future of Open Source. In: Wynants, M. &amp; J. Cornelis (eds.) How Open is the Future? VUB Brussels University Press, pp. 429-59.</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/tuomi3_bookchapter.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source has seen phenomenal growth in recent years. In many ways, it has been a great success story. Yet it is interesting to study the conditions that would enable the open-source movement to remain viable and thrive also in the future. This chapter explores the driving forces behind the open source model and its constraints, discussing both the factors likely to promote the continuous growth of the open-source movement and those that could lead to its downfall.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Hybrid Innovation - How Does the Collaboration Between the FLOSS Community and Corporations Happen?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lin4_hybrid.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Unlike innovation based on a strong professional culture involving close collaboration between professionals in academia and/or corporations, the current Free/Libre Open Source Software (FLOSS) development entails a global knowledge network, which consists of 1) a heterogeneous community of individuals and organisations who do not necessarily have professional backgrounds in computer science but competent skills to understand programming and working in a public domain; 2) corporations. This paper highlights the importance of the hybrid form of developing and implementing software, and also identifies several key factors shaping the collaboration between OSS firms and the community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Greg R Vetter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">&quot;Infectious&quot; Open Source Software: Spreading Incentives or Promoting Resistance?</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/vetter2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Some free or open source software infects other software with its licensing terms. Free or open source software is a copyright based licensing system. It typically allows modification and distribution on conditions such as source code availability, royalty-free use and other requirements. Some licenses require distribution of modifications under the same terms. A license is infectious when it has a strong scope for the modifications provision. The scope arises from a broad conception of software derivative works. A strong infectious ambit would apply itself to modified software, and to software intermixed or coupled with non-open-source software. Popular open source software, including the GNU/Linux operating system, uses a license with this feature. This Article assesses the efficacy of broad infectious license terms to determine their incentive effects for open source and proprietary software. The analysis doubts beneficial effects. Rather, on balance, such terms may produce incentives detrimental to interoperability and coexistence between open and proprietary code. As a result, open source licensing should precisely define infectious terms in order to support open source development without countervailing effects and misaligned incentives.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sara Boettiger</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Patenting</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The open source and free software movements have used self-perpetuating copyright licenses to maintain open access to publicly distributed software. This model of licensing has now migrated to the field of biotechnology, where patents rather than copyrights dominate proprietary rights. Consequently, a model for open source patenting or free biotechnology presents a constellation of legal issues not typically found in previous open source licensing. This paper discusses several of these issues, including the nature of the rights transferred, the activities that may trigger the terms of the license, and the legal prohibitions on certain forms of licensing.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lee Fleming</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Penguins, Camels, and Other Birds of a Feather: Brokerage, Boundary Spanning, and Leadership in Open Innovation Communities</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/flemingwaguespack.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">What types of human and social capital identify the emergence of leaders of open innovation communities? Consistent with the norms of an engineering culture, we find that future leaders must first make strong technical contributions. Beyond technical contributions, they must then integrate their voluntary communities in order to avoid the ever present danger of forking and balkanization. This is enabled by two correlated but distinct social positions: brokerage, and boundary spanning between technological modules. An inherent lack of trust associated with brokerage positions can be overcome through physical interaction or contributions within technological boundaries. Successful leaders are thus the product of strong technical contribution and a structural position that can bind the community together.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Stewart, Katherine J.</style></author><author><style face="normal" font="default" size="100%">Ammeter, Anthony P.</style></author><author><style face="normal" font="default" size="100%">Maruping, Likoebe M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Preliminary Analysis of the Influences of Licensing and Organizational Sponsorship on Success in Open Source Projects</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 07</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">HICSS '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">freshmeat</style></keyword><keyword><style  face="normal" font="default" size="100%">license analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">licensing</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword><keyword><style  face="normal" font="default" size="100%">restrictive</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2005</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1109/HICSS.2005.38</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">IEEE Computer Society</style></publisher><pub-location><style face="normal" font="default" size="100%">Washington, DC, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1-10</style></pages><isbn><style face="normal" font="default" size="100%">0-7695-2268-8-7</style></isbn><abstract><style face="normal" font="default" size="100%">This paper develops and tests a model of the impact of	licensing restrictiveness	and	organizational sponsorship on the popularity and vitality of open source software (OSS) development projects. Using data gathered from Freshmeat.net and OSS project home pages the main conclusions derived from the analysis are that organizational sponsorship has a positive effect on project popularity by easing user concerns about cost and quality and that license restrictiveness may have a negative effect on popularity by reducing the perceived utility of open source software. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;Publicly available data on open source projects registered on the Freshmeat website (www.freshmeat.net) was used to test the hypotheses. Data was collected from each project’s Freshmeat website at the start and end of an eight month period (March - December 2002).&quot;
&quot;We first selected three project categories from which to draw our sample. These were utilities, software development, and games.&quot;
&quot;Within these categories we further differentiated between new projects, which had been registered on the site within the two weeks prior to our first data collection point and older projects that had been registered more than two weeks prior to our initial data collection.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>12</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kingstone, Steve</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Brazil adopts open-source software</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">2 June, 2005</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://news.bbc.co.uk/2/hi/business/4602325.stm</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">5 December</style></number><publisher><style face="normal" font="default" size="100%">BBC News</style></publisher><pub-location><style face="normal" font="default" size="100%">Sao Paulo</style></pub-location><volume><style face="normal" font="default" size="100%">2008</style></volume><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaboration Using OSSmole: A repository of FLOSS data and analyses</style></title><secondary-title><style face="normal" font="default" size="100%">Symposium on Mining Software Repositories</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">17 May</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">St. Louis</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">N. Good</style></author><author><style face="normal" font="default" size="100%">Dhamija, R.</style></author><author><style face="normal" font="default" size="100%">J. Grossklags</style></author><author><style face="normal" font="default" size="100%">D. Thaw</style></author><author><style face="normal" font="default" size="100%">Aronowitz, S.</style></author><author><style face="normal" font="default" size="100%">D. Mulligan</style></author><author><style face="normal" font="default" size="100%">J. Konstan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Stopping spyware at the gate: a user study of privacy, notice and spyware</style></title><secondary-title><style face="normal" font="default" size="100%">2005 Symposium on Usable Privacy and Security</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">agreement,</style></keyword><keyword><style  face="normal" font="default" size="100%">and</style></keyword><keyword><style  face="normal" font="default" size="100%">Aspects,</style></keyword><keyword><style  face="normal" font="default" size="100%">Design,</style></keyword><keyword><style  face="normal" font="default" size="100%">end</style></keyword><keyword><style  face="normal" font="default" size="100%">EULA,</style></keyword><keyword><style  face="normal" font="default" size="100%">Experimentation,</style></keyword><keyword><style  face="normal" font="default" size="100%">Factors,</style></keyword><keyword><style  face="normal" font="default" size="100%">Human</style></keyword><keyword><style  face="normal" font="default" size="100%">Legal</style></keyword><keyword><style  face="normal" font="default" size="100%">license</style></keyword><keyword><style  face="normal" font="default" size="100%">notice,</style></keyword><keyword><style  face="normal" font="default" size="100%">of</style></keyword><keyword><style  face="normal" font="default" size="100%">privacy,</style></keyword><keyword><style  face="normal" font="default" size="100%">security</style></keyword><keyword><style  face="normal" font="default" size="100%">service,</style></keyword><keyword><style  face="normal" font="default" size="100%">spyware,</style></keyword><keyword><style  face="normal" font="default" size="100%">terms</style></keyword><keyword><style  face="normal" font="default" size="100%">ToS,</style></keyword><keyword><style  face="normal" font="default" size="100%">usability,</style></keyword><keyword><style  face="normal" font="default" size="100%">user</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year><pub-dates><date><style  face="normal" font="default" size="100%">07/2005</style></date></pub-dates></dates><publisher><style face="normal" font="default" size="100%">Association for Computing Machinery</style></publisher><pub-location><style face="normal" font="default" size="100%">Pittsburgh, PA</style></pub-location><pages><style face="normal" font="default" size="100%">43-52</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-178-3 </style></isbn><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chengetai Masango</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">	Socialization practices in FLOSS development teams</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">development team</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">member</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">socialization</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1438</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">322-323</style></pages><abstract><style face="normal" font="default" size="100%">Socialization of new members into Free/Libre Open Source Software (FLOSS) development teams is an important but little studied process in producing effective teams of this type. This is a dissertation proposal for a virtual ethnographic study that looks at the mechanisms and processes used to socialize new members into the team in order to help maintain a common group identity and focus.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ohira, Masao</style></author><author><style face="normal" font="default" size="100%">Ohsugi, Naoki</style></author><author><style face="normal" font="default" size="100%">Ohoka, Tetsuya</style></author><author><style face="normal" font="default" size="100%">Matsumoto, Ken-ichi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Accelerating cross-project knowledge collaboration using collaborative filtering and social networks</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">collaborative filtering</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">knowledge collaboration</style></keyword><keyword><style  face="normal" font="default" size="100%">projects</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">visualization tool</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083163</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/111Accelerating.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">111-115</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Vast numbers of free/open source software (F/OSS) development projects use hosting sites such as Java.net and SourceForge.net. These sites provide each project with a variety of software repositories (e.g. repositories for source code sharing, bug tracking, discussions, etc.) as a media for communication and collaboration. They tend to focus on supporting rich collaboration among members in each project. However, a majority of hosted projects are relatively small projects consisting of few developers and often need more resources for solving problems. In order to support cross-project knowledge collaboration in F/OSS development, we have been developing tools to collect data of projects and developers at SourceForge, and to visualize the relationship among them using the techniques of collaborative filtering and social networks. The tools help a developer identify “who should I ask?” and “what can I ask?” and so on. In this paper, we report a case study of applying the tools to F/OSS projects data collected from SourceForge and how effective the tools can be used for helping cross-project knowledge collaboration.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Morgan, Lorraine</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Analysis of COSPA - A Consortium for Open Source in the Public Administration</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/624</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">125-129</style></pages><abstract><style face="normal" font="default" size="100%">This paper reflects on a two-year EU funded specific research targeted project that officially began in January 2004 entitled COSPA, a Consortium for studying, evaluating and supporting the introduction of Open Source Software and Open Data Standards in the Public Administration. COSPA focuses on office automation and desktop system software and aims at rigorously measuring the effort, costs and benefits of a transition to Open Source. The project involves 15 European Universities and Public Administrations from Italy, Hungary, Ireland, Denmark, UK, Belgium and about sixty observers, including the University of Alberto (Canada), Victoria University of Wellington (New Zealand) and the United Nations Educational Scientific and Cultural Organisation (UNESCO).</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kim, Sunghun</style></author><author><style face="normal" font="default" size="100%">Whitehead,Jr., E. James</style></author><author><style face="normal" font="default" size="100%">Bevan, Jennifer</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Analysis of signature change patterns</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">gcc</style></keyword><keyword><style  face="normal" font="default" size="100%">kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">signature change</style></keyword><keyword><style  face="normal" font="default" size="100%">signature change patterns</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution path</style></keyword><keyword><style  face="normal" font="default" size="100%">soure code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083154</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/64AnalysisOfSignature.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">1–5</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Software continually changes due to performance improvements, new requirements, bug fixes, and adaptation to a changing operational environment. Common changes include modifications to data definitions, control flow, method/function signatures, and class/file relationships. Signature changes are notable because they require changes at all sites calling the modified function, and hence as a class they have more impact than other change kinds.We performed signature change analysis over software project histories to reveal multiple properties of signature changes, including their kind, frequency, and evolution patterns. These signature properties can be used to alleviate the impact of signature changes. In this paper we introduce a taxonomy of signature change kinds to categorize observed changes. We report multiple properties of signature changes based on an analysis of eight prominent open source projects including the Apache HTTP server, GCC, and Linux 2.5 kernel.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Long, J.</style></author><author><style face="normal" font="default" size="100%">Yuan, M.J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Are All Open Source Projects Created Equal? Understanding the Sustainability of Open Source Software Development Model</style></title><secondary-title><style face="normal" font="default" size="100%">AMCIS 2005 Proceedings</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">downloads</style></keyword><keyword><style  face="normal" font="default" size="100%">metadata</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/LongYuan.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">435</style></number><abstract><style face="normal" font="default" size="100%">A very intriguing question in Open Source software (OSS) development is: why there are only a few open source projects succeed, while the majority of projects never do. In this research, we examine the factors that may influence the performance of OSS projects. We particularly focus on the OSS’s core developers’ role in the project’s success. Extant research has yet to distinguish core developers and non-core developers from the community at large. The different roles of the core developers and non-core developers in OSS projects’ success still remain unclear. Our research contributes to the literature by separating the core developers from the development forces in general and empirically examining the core developers’ importance. Drawing the evidences from our extensive dataset of 300 open source projects, we demonstrated that core developers’ leadership and project advocation are crucial in determining the fate of the OSS projects. Our research could provide better understanding of OSS sustainability. It could also give practical advice to the OSS community on how to make the project successful.</style></abstract><notes><style face="normal" font="default" size="100%">uses first 300 most active projects on Sourceforge: 'Our data sample consists of 300 open source software development projects hosted in the Sourceforge.Net. They are the first 300 active projects ranked by Sourceforge.Net....Our dependent variable in the model to measure the success of the projects is the number of downloads. It is an essential variable to show how successful the project is. Generally, more number of downloads means a more successful project. Independent variables include: development status, project lifespan, number of developers, number of messages in the forums, number of mailing list, number of bug report, number of patch report, number of CVS report, number of file releases and also number of news release.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ågerfalk, Pär J</style></author><author><style face="normal" font="default" size="100%">Deverell, Andrea</style></author><author><style face="normal" font="default" size="100%">Fitzgerald, Brian</style></author><author><style face="normal" font="default" size="100%">Morgan, Lorraine</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Assessing the Role of Open Source Software in the European Secondary Software Sector: A Voice from Industry</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/752</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">82-87</style></pages><abstract><style face="normal" font="default" size="100%">This paper addresses the open source software (OSS) phenomenon from an industry perspective and reveals a number of complexities surrounding the role of OSS in the secondary software sector. It presents the research results of an international workshop which was hosted with the explicit intention of extracting the voice of key industrial stakeholders. The data was gathered and analysed using a qualitative approach which revealed the key strengths and weaknesses of OSS from an industrial perspective. This formed the foundations for developing a framework describing the emerging commercial incarnation of OSS (we refer to this as Open Source Software, Inc.) The paper concludes that the European secondary software sector recognise the benefits of leveraging OSS but are aware of key issues pertinent to such an end.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gonzalez,  Andres Guadamuz</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The calm before the storm? Legal challenges to open source licences</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">215-219</style></pages><abstract><style face="normal" font="default" size="100%">This paper will concentrate on presenting a legal
analysis of two of the main challenges to open source
software: SCO’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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiss, Dawid</style></author><author><style face="normal" font="default" size="100%">Osi´nski, Stanisław</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Carrot2 Clustering Framework</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">BSD license</style></keyword><keyword><style  face="normal" font="default" size="100%">cluster</style></keyword><keyword><style  face="normal" font="default" size="100%">clustering framework</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">research</style></keyword><keyword><style  face="normal" font="default" size="100%">result</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/788</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">298-299</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author><author><style face="normal" font="default" size="100%">Rigby, Peter</style></author><author><style face="normal" font="default" size="100%">Cubranic, Davor</style></author><author><style face="normal" font="default" size="100%">Storey, Margaret-Anne</style></author><author><style face="normal" font="default" size="100%">Thomson, Suzanne</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The challenges of creating open source education software: the Gild experience</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">learning environment</style></keyword><keyword><style  face="normal" font="default" size="100%">novice programmers</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">programming environment</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1539</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">338-340</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors></contributors><titles><title><style face="normal" font="default" size="100%">A Cluster Analysis of Open Source Licenses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/618</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">50-53</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Crombie, David</style></author><author><style face="normal" font="default" size="100%">Lenoir, Roger</style></author><author><style face="normal" font="default" size="100%">McKenzie, Neil</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Communication from scratch: towards accessible open source information systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/759</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">179-186</style></pages><abstract><style face="normal" font="default" size="100%">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, ...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Persson, Anna</style></author><author><style face="normal" font="default" size="100%">Lings, Brian</style></author><author><style face="normal" font="default" size="100%">Lundell, Björn</style></author><author><style face="normal" font="default" size="100%">Mattsson, Anders</style></author><author><style face="normal" font="default" size="100%">Ärlig, Ulf</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Communication, coordination and control in distributed development: an OSS case study</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/769</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">88-92</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gutsche, Joerg</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Competition between Open Source and Proprietary Software, and the Scope for Public Policy</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/758</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">196-199</style></pages><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Kangning Wei</style></author><author><style face="normal" font="default" size="100%">Li, Qing</style></author><author><style face="normal" font="default" size="100%">Eseryel, U. Yeliz</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Coordination of Free/Libre Open Source Software development</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems (ICIS 2005)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">case study</style></keyword><keyword><style  face="normal" font="default" size="100%">compiere</style></keyword><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">egroupware</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">gaim</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/CrowstonWeiLiEseryelHowison.pdf</style></url></related-urls></urls><pub-location><style face="normal" font="default" size="100%">Las Vegas, NV, USA</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 “self-assignment” 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.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;The data used for the study were interactions on the main developer communication venue, either a developer mailing list or online forum&quot;
sourceforge
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rossi, Bruno</style></author><author><style face="normal" font="default" size="100%">Scotto, Marco</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Criteria for the non invasive transition to OpenOffice</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/789</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">250-253</style></pages><abstract><style face="normal" font="default" size="100%">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' attitude towards OSS and the emerging criteria for a possible transition are exposed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Angioni, Manuela</style></author><author><style face="normal" font="default" size="100%">Sanna, Raffaella</style></author><author><style face="normal" font="default" size="100%">Soro, Alessandro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Defining a Distributed Agile Methodology for an Open Source Scenario</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/766</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">209-214</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we propose and describe an agile methodology for distributed development (MADD - Methodology for Agile Distributed Development). In particular, it’s illustrated a set of best practices to apply in a distributed and agile context, chosen on the base of their impact software quality and team interoperation. Beyond the proposed methodology, we show the results of a survey that we submitted to various contributors of Open Source projects. The survey has been of support to the definition of the MADD, helping to more understand and estimate if, how and how much agile practices and values are already present in the OS world, that today represents one of the most emblematic examples of distributed development. The MADD methodology will be adopted on a software development project at the University of Cagliari (Italy), by a group of students that will work like an Open Source community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author><author><style face="normal" font="default" size="100%">Braghin, Chiara</style></author><author><style face="normal" font="default" size="100%">Gasperi, Paolo</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Defining the Total Cost of Ownership for the Transition to Open Source Systems</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/774</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">108-112</style></pages><abstract><style face="normal" font="default" size="100%">This paper provides a a framework to evaluate the transition to a OSS software solution in terms of returns and losses in the context of Public Administrations. The ultimate goal of the framework is to identify costs that are not easy to trace or that are not usually collected like user acceptance. The framework has been conducted using a Total Cost of Ownership approach, which is the most frequently used model to conduct cost comparisons between two or more IT systems. The study further implements the Goal Question Metric paradigm to identify the cost metrics. The framework relies various methods to collect the data, including questionnaires with end-users, qualitative interviews with IT-managers and company balance sheets. An example of framework's use is provided.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Developer identification methods for integrated data from various sources</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">anonymization</style></keyword><keyword><style  face="normal" font="default" size="100%">bug tracker</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email address</style></keyword><keyword><style  face="normal" font="default" size="100%">gnome</style></keyword><keyword><style  face="normal" font="default" size="100%">identity</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">privacy</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">version control</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083162</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/106DeveloperIdentification.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">106-110</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Studying a software project by mining data from a single repository has been a very active research field in software engineering during the last years. However, few efforts have been devoted to perform studies by integrating data from various repositories, with different kinds of information, which would, for instance, track the different activities of developers. One of the main problems of these multi-repository studies is the different identities that developers use when they interact with different tools in different contexts. This makes them appear as different entities when data is mined from different repositories (and in some cases, even from a single one). In this paper we propose an approach, based on the application of heuristics, to identify the many identities of developers in such cases, and a data structure for allowing both the anonymized distribution of information, and the tracking of identities for verification purposes. The methodology will be presented in general, and applied to the GNOME project as a case example. Privacy issues and partial merging with new data sources will also be considered and discussed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Colazo, Jorge A.</style></author><author><style face="normal" font="default" size="100%">Fang, Yulin</style></author><author><style face="normal" font="default" size="100%">Neufeld, Derrick J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Development Success in Open Source Software Projects: Exploring the Impact of Copylefted Licenses</style></title><secondary-title><style face="normal" font="default" size="100%">Americas Conference on Information Systems (AMCIS 2005)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributions</style></keyword><keyword><style  face="normal" font="default" size="100%">copyleft</style></keyword><keyword><style  face="normal" font="default" size="100%">developer</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">membership</style></keyword><keyword><style  face="normal" font="default" size="100%">productivity</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">success</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://aisel.isworld.org/password.asp?Vpath=AMCIS/2005&amp;\#38;PDFpath=OSSDAU01-1167.pdf</style></url></web-urls></urls><abstract><style face="normal" font="default" size="100%">Copyleft prevents the source code of open source software (OSS) from being privately appropriated. The ethos of the OSS movement suggests that volunteer developers may particularly value and contribute to copylefted projects. Based on social movement theory, we hypothesized that copylefted OSS projects are more likely than non-copylefted OSS projects to succeed in the development process, in terms of two key indicators: developer membership and developer productivity. We performed an exploratory study using data from 62 relevant OSS projects spanning an average of three years of development time. We found that copylefted projects were associated with higher developer membership and productivity. This is the first study to empirically test the relationship between copylefted licenses and OSS project success. Implications for OSS project initiators as well as future research directions are discussed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Botturi, Luca</style></author><author><style face="normal" font="default" size="100%">Chris Tebb</style></author><author><style face="normal" font="default" size="100%">Vania Dimitrova</style></author><author><style face="normal" font="default" size="100%">Drew Withworth</style></author><author><style face="normal" font="default" size="100%">Julika Matravers</style></author><author><style face="normal" font="default" size="100%">Jutta Geldermann</style></author><author><style face="normal" font="default" size="100%">Isabelle Hubert</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Development-oriented Open Source eLearning Tool Evaluation: the Edukalibre Approach</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">341-344</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Russo, Ruggero</style></author><author><style face="normal" font="default" size="100%">Lamanna, Davide</style></author><author><style face="normal" font="default" size="100%">Baldoni, Roberto</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Distributed Software Platforms for Rehabilitating Obsolete Hardware</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/782</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">220-223</style></pages><abstract><style face="normal" font="default" size="100%">The diffusion of ICTs created the issue of a huge quantity of old computers to be discarded (E-waste). Sustainable dismantle is becoming a global enviromental emergency. Trashware movement is spreading worldwide, aiming to profitably reuse discarded computers as an alternative to dismantling them. Trashware is deeply related to the Open Source and Free Software movements. The aim of this piece of research is to combine Trashware to clustering, in order to verify if further optimisations are possible. Experiments were conducted on clusters of old machines and results are hereby presented.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Russo, Barbara</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Doctoral Symposium at OSS 2005</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">300</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">De Prato, Giuditta</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Economics approaching OSS: reviewing 15 years of debate</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/765</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">268</style></pages><abstract><style face="normal" font="default" size="100%">The work aims at reviewing the theoretical literature on the development and diffusion of Open Source Software (OSS) relevant to an economic approach. It provides a synthetic picture of the areas of economic analysis for OSS, by attempting to frame relevant research efforts into a taxonomy based on attributes of innovation and process of diffusion. The main contributions investigating in the past decade the economic theoretical models beyond the “open” way of producing and distributing software goods analyse: i) its supposed nature of complex public good, ii) the production process and distributed work organisation, iii) the evaluation of its impact on the software market, both at market level and at firm level. The relationship of the open source model with knowledge appropriation and reuse, and with innovation diffusion to support economic growth and social wealth would help drawing related economics and policy issues.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Abiteboul, Serge</style></author><author><style face="normal" font="default" size="100%">Leroy, Xavier</style></author><author><style face="normal" font="default" size="100%">Vrdoljak, Boris</style></author><author><style face="normal" font="default" size="100%">Di Cosmo, Roberto</style></author><author><style face="normal" font="default" size="100%">Fermigier, Stéfane</style></author><author><style face="normal" font="default" size="100%">Laurière, Stéphane</style></author><author><style face="normal" font="default" size="100%">Lepied, Frédéric</style></author><author><style face="normal" font="default" size="100%">Pop, Radu</style></author><author><style face="normal" font="default" size="100%">Villard, Florent</style></author><author><style face="normal" font="default" size="100%">Smets, Jean-Paul</style></author><author><style face="normal" font="default" size="100%">Bryce, Ciarán</style></author><author><style face="normal" font="default" size="100%">Dittrich, Klaus R.</style></author><author><style face="normal" font="default" size="100%">Milo, Tova</style></author><author><style face="normal" font="default" size="100%">Sagi, Assaf</style></author><author><style face="normal" font="default" size="100%">Shtossel, Yotam</style></author><author><style face="normal" font="default" size="100%">Panto, Eleonora</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">EDOS: Environment for the Development and Distribution of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/737</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">66-70</style></pages><abstract><style face="normal" font="default" size="100%">The open-source software community is now comprised of a very large and growing number of contributors and users. The GNU/Linux operating system for instance has an estimated 18 million users worldwide and its contributing developers can be counted by thousands. The critical mass of contributors taking part in various opensource projects has helped to ensure high quality for open source software. However, despite the achievements of the open-source software industry, there are issues in the production of large scale open-source software (OSS) such as the GNU/Linux operating system that have to be addressed as the numbers of users, of contributors, and of available applications grow. EDOS is a European project supported by IST started October 2004 and ending in 2007, whose objective is to provide a new generation of methodologies, theoretical models, technical tools and quality models specifically tailored to OSS engineering and to software distribution over the Interne...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gyimothy, T.</style></author><author><style face="normal" font="default" size="100%">Ferenc, R.</style></author><author><style face="normal" font="default" size="100%">Siket, I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Empirical validation of object-oriented metrics on open source software for fault prediction</style></title><secondary-title><style face="normal" font="default" size="100%">IEEE Transactions on Software Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">cbo</style></keyword><keyword><style  face="normal" font="default" size="100%">defects</style></keyword><keyword><style  face="normal" font="default" size="100%">dit</style></keyword><keyword><style  face="normal" font="default" size="100%">fault-prone modules</style></keyword><keyword><style  face="normal" font="default" size="100%">faults</style></keyword><keyword><style  face="normal" font="default" size="100%">lcom</style></keyword><keyword><style  face="normal" font="default" size="100%">lcomn</style></keyword><keyword><style  face="normal" font="default" size="100%">loc</style></keyword><keyword><style  face="normal" font="default" size="100%">metrics</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">noc</style></keyword><keyword><style  face="normal" font="default" size="100%">object-oriented</style></keyword><keyword><style  face="normal" font="default" size="100%">rfc</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">wmc</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.115.8372&amp;rep=rep1&amp;type=pdf</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/Gyimothy.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">10</style></number><volume><style face="normal" font="default" size="100%">31</style></volume><pages><style face="normal" font="default" size="100%">897-910</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software systems are becoming increasingly important these days. Many companies are investing in open source projects and lots of them are also using such software in their own work. But, because open source software is often developed with a different management style than the industrial ones, the quality and reliability of the code needs to be studied. Hence, the characteristics of the source code of these projects need to be measured to obtain more information about it. This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000233015300008</style></accession-num><notes><style face="normal" font="default" size="100%">&quot;This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle.&quot;
metrics, 
wmc weighted methods per class, 
dit depth of inheritance, 
rfc response for a class,
noc number of children,
cbo coupling between object classes,
cohesion,
lines of code, loc, sloc
chidamber and kemerer metrics</style></notes><custom1><style face="normal" font="default" size="100%">software engineering</style></custom1><custom2><style face="normal" font="default" size="100%">case study</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Görg, Carsten</style></author><author><style face="normal" font="default" size="100%">Weißgerber, Peter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Error detection by refactoring reconstruction</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugs</style></keyword><keyword><style  face="normal" font="default" size="100%">class</style></keyword><keyword><style  face="normal" font="default" size="100%">inheritance</style></keyword><keyword><style  face="normal" font="default" size="100%">jedit</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">tomcat</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083148</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/29ErrorDetection.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">29-33</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">In many cases it is not sufficient to perform a refactoring only at one location of a software project. For example, refactorings may have to be performed consistently to several classes in the inheritance hierarchy, e.g. subclasses or implementing classes, to preserve equal behavior.In this paper we show how to detect incomplete refactorings - which can cause long standing bugs because some of them do not cause compiler errors - by analyzing software archives. To this end we reconstruct the class inheritance hierarchies, as well as refactorings on the level of methods. Then, we relate these refactorings to the corresponding hierarchy in order to find missing refactorings and thus, errors and inconsistencies that have been introduced in a software project at some point of the history.Finally. we demonstrate our approach by case studies on two open source projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rainer, Austen</style></author><author><style face="normal" font="default" size="100%">Gale, Stephen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evaluating the Quality and Quantity of Data on Open Source Software Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/733</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">29-36</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, we provide a preliminary evaluation of the quality and quantity of data on open source (OS) projects, provided at the SourceForge.net portal. We have derived a dataset of approximately 50000 projects from SourceForge. Using several indicators of project activity, we identify two samples from the entire dataset: the ‘most active’ OS projects (a total of 456 projects, ~0.9% of the entire dataset), and those projects with active code development (5826 projects, ~11.6%). The number of projects that are active across all of our main indicators of activity account for less than 1% of the projects on the portal. This suggests that many OS projects being registered on SourceForge are ‘impulse’ projects, which do not gather sufficient interest from developers or users to ‘activate’ those projects and make them ‘successful’. It also suggests that researchers, developers and users should be careful about how they use OS portals.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution of Open Source Software Systems – A Large-Scale Investigation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/863</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">148-153</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, the evolution of a large sample of open source software projects will be analysed. The evolution of commercial systems has been an issue that has long been a center of research, thus a coherent theoretical framework of software evolution has been developed and empirically tested. Therefore these results can be used to compare the situation in open source projects to the evolution of commercial projects. This allows to assess whether the underlying software process indeed significantly differs. The data collection methodology relying on a large software repository and the respective source code control systems is described, and an overview on the collected data on several thousand projects is given. The evolutionary behaviour is explored using both a linear and a quadratic model, with the quadratic model significantly outperforming the linear one. The most interesting fact is that while in the mean the growth rate is decreasing over time according to the l...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mattia Monga</style></author><author><style face="normal" font="default" size="100%">Andrea Trentini</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution of Open-Source Code Bases EVOSC 2005</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">359</style></pages><abstract><style face="normal" font="default" size="100%">The very essence of open- source software is that
it enables custom evolutions. These evolutions should be
designed and managed carefully, since merging the main
trunk with custom branches is often critical for inheriting
evolutions that are not at the core interest of the independent
developer.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution of Volunteer Participation in Libre Software Projects: Evidence from Debian</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">debian</style></keyword><keyword><style  face="normal" font="default" size="100%">maintainers</style></keyword><keyword><style  face="normal" font="default" size="100%">PopCon</style></keyword><keyword><style  face="normal" font="default" size="100%">popularity</style></keyword><keyword><style  face="normal" font="default" size="100%">Volunteers</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/857</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/robles_barahona_michlmayr-evolution_participation.pdf</style></url></related-urls></urls><pages><style face="normal" font="default" size="100%">100-107</style></pages><abstract><style face="normal" font="default" size="100%">Most libre software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: volunteer contributions are inherently difficult to predict, plan and manage, especially in the case of large projects. In this paper we analyze the evolution in time of the human resources of one of the largest and most complex libre software projects composed primarily of volunteers, the Debian project. Debian currently has around 1300 volunteers working on several tasks: much activity is focused on packaging software applications and libraries, but there is also major work related to the maintenance of the infrastructure needed to sustain the development. We have performed a quantitative investigation of data from almost seven years, studying how volunteer involvement has affected the software...</style></abstract><notes><style face="normal" font="default" size="100%">&quot;For each release we have retrieved the corresponding sources.gz file (see below) from the Debian archive. From it we have extracted information about the packages and their maintainers....&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Experiences teaching a graduate course in Open Source Software Engineering</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">course</style></keyword><keyword><style  face="normal" font="default" size="100%">FOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software engineering</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/971</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">326-328</style></pages><abstract><style face="normal" font="default" size="100%">This paper describes the early experiences of a graduate course in open source software engineering at the Department of Computer Science at the University Victoria. It includes a description of the motivation for the course, its structure and evaluation methods. It concludes with a discussion of the lessons learned and its future.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Colognesi, Cristina</style></author><author><style face="normal" font="default" size="100%">Guandalini, Stefano</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">eZPA portale e-government per enti locali</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">e-government</style></keyword><keyword><style  face="normal" font="default" size="100%">enti locali</style></keyword><keyword><style  face="normal" font="default" size="100%">INTERNET</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">pubblica amministrazione</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/874</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">289-290</style></pages><abstract><style face="normal" font="default" size="100%">Tra i numerosi settori in cui Internet sta intervenendo con una forte carica di “modernizzazione”, quello dell’e- Government, inteso come possibilità per tutti gli utenti, per tutti i cittadini, di gestire il rapporto con la Pubblica Amministrazione, anche on line, sta producendo gli effetti maggiormente innovativi. L'occasione fornitaci dall'amministrazione del Comune di Ozzano dell'Emilia ha permesso di sviluppare l'applicazione eZPA, scritta con software a codice sorgente aperto e rilasciata con licenza GNU-GPL (General Publish Licence), liberamente utilizzabile e modificabile. Il portale consente la fruibilità telematica dei servizi comunali sia ai clienti esterni (cittadini e imprese), sia agli utenti interni (dipendenti e collaboratori comunali), attraverso una struttura di sportelli fisici/virtuali. In particolare, l'utilizzo della metafora di comunicazione “Evento della vita”,[1] raccomandata dalle linee guida del Ministro per l'Innovazione e le Tecnologie, ha ...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Altarocca, Francesco</style></author><author><style face="normal" font="default" size="100%">Vaccari, Carlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Fare Open Source all'Istat: il generatore di data-entry per indagini statistiche</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">data-entry</style></keyword><keyword><style  face="normal" font="default" size="100%">indagini statistiche</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">PHP</style></keyword><keyword><style  face="normal" font="default" size="100%">web</style></keyword><keyword><style  face="normal" font="default" size="100%">XML</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/903</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">283-286</style></pages><abstract><style face="normal" font="default" size="100%">Viene presentata una prima esperienza di sviluppo di software Open Source all'Istat, che riguarda un sistema generalizzato di data-entry per indagini statistiche. L'applicazione, in via di rilascio, copre la fase di acquisizione dati propria delle indagini statistiche e consentirà di generare maschere che potranno essere utilizzate sia in Intranet che sul Web. L'applicazione descritta, che utilizza PHP e XML come tecnologie fondanti, rappresenta un'esperienza concreta di sviluppo Open Source nella quale l'Istat vuole riversare le proprie esperienze specifiche, mettendole poi a disposizione delle altre strutture interessate.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Potortì, Francesco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Free software and research</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/864</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">270-271</style></pages><abstract><style face="normal" font="default" size="100%">Free software licenses are a natural choice in a research environment. In the following, we will try to back this simple statement with some considerations and examples, in an effort to analyse the significant interactions between free software and research.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Trung T. Dinh-Trong</style></author><author><style face="normal" font="default" size="100%">James M. Bieman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The FreeBSD Project: A Replication Case Study of Open Source Development</style></title><secondary-title><style face="normal" font="default" size="100%">IEEE Trans. Software Eng.</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">contributors</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">defect density</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">users</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/DinhTrungBieman.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">6</style></number><volume><style face="normal" font="default" size="100%">31</style></volume><pages><style face="normal" font="default" size="100%">481-494</style></pages><abstract><style face="normal" font="default" size="100%">Case studies can help to validate claims that open source software development produces higher quality software at lower cost than traditional commercial development. One problem inherent in case studies is external validity—we do not know whether or not results from one case study apply to another development project. We gain or lose confidence in case study results when similar case studies are conducted on other projects. This case study of the FreeBSD project, a long-lived open source project, provides further understanding of open source development. The paper details a method for mining repositories and querying project participants to retrieve key process information. The FreeBSD development process is fairly well-defined with proscribed methods for determining developer responsibilities, dealing with enhancements and defects, and managing releases. Compared to the Apache project, FreeBSD uses 1) a smaller set of core developers—developers who control the code base—that implement a smaller percentage of the system, 2) a larger set of top developers to implement 80 percent of the system, and 3) a more well-defined testing process. FreeBSD and Apache have a similar ratio of core developers to people involved in adapting and debugging the system and people who report problems. Both systems have similar defect densities and the developers are also users in both systems.</style></abstract><notes><style face="normal" font="default" size="100%">&quot; we obtained the necessary data from the [FreeBsd] CVS repository, the bug report database, and the e-mail archive. The CVS repository contains all of the code and related documentation that is committed to the project from 1993 until the present. The bug report database contains information describing all reported problems, as well as the status (such as fixed, under test, or open) of each problem. Each bug report is called a PR and assigned a reference number. The e-mail archive contains every e-mail message exchanged between the developers since 1994.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Rentocchini, Francesco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Future Development in the European Software Industry: Patentability of Computer Programs or Open Source Software?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">european</style></keyword><keyword><style  face="normal" font="default" size="100%">market segment</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">os</style></keyword><keyword><style  face="normal" font="default" size="100%">patent</style></keyword><keyword><style  face="normal" font="default" size="100%">patent literature</style></keyword><keyword><style  face="normal" font="default" size="100%">patentability</style></keyword><keyword><style  face="normal" font="default" size="100%">software industry</style></keyword><keyword><style  face="normal" font="default" size="100%">software sector</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://hdl.handle.net/2038/966</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">311-313</style></pages><abstract><style face="normal" font="default" size="100%">Economic literature has treated the patent system as an indispensable tool to incentive inventive activity and to foster diffusion of technological improvements, but recent developments have brought at the center of the stage the Open Source phenomenon which is based on completely different mechanisms among which the free disclosure of the inventive steps. This work analyzes changes that are taking place into patent literature in order to give account of the desirability of patents in software sector. In addition some ideas on empirical analysis are put forward: the possibility of measuring the relationship between patents and input of innovation process in the software sector and the influence that private firms will have on Open Source developers motivations.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Skidmore, Darren</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The future of software as a business artefact</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1540</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">231-236</style></pages><abstract><style face="normal" font="default" size="100%">Rather than look to migration guides for business, or to barriers to adoption of Open Source Software, perhaps we should look to understand what it is that organisations need from their software, it is not just the feature set of the application, but a combination and compromise of the business benefits and business risks, some of which are not inherent in the software feature set, but are interrelated to the needs and pre-existing conditions of the organisation. This paper looks to investigate these aspects of Software to an organisation and to then investigate if Open Source Software can fulfil these factors.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ruben van Wendel de Joode</style></author><author><style face="normal" font="default" size="100%">Tineke M. Egyedi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Handling variety: the tension between adaptability and interoperability of open source software</style></title><secondary-title><style face="normal" font="default" size="100%">Computer Standards &amp; Interfaces</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">divergence</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.sciencedirect.com/science/article/B6TYV-4F6K72H-1/2/c74c64ce51e6f46abf9f39ae945c9e15</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">28</style></volume><pages><style face="normal" font="default" size="100%">109 - 121</style></pages><abstract><style face="normal" font="default" size="100%">Open source software (OSS) offers unprecedented opportunities to create variety. This could lead to incompatibility and fragmentation. To prevent this some form of coordination is needed. This paper explores which mechanisms of coordination are responsible for limiting divergence in OSS. Two cases are examined: Java and Linux. A systematic difference seems to exist between the mechanisms identified in the two communities. With respect to Java, divergence is where possible avoided ex ante, whereas for Linux divergence is foremost reduced ex post. The conclusion discusses this difference and the implications of both types of coordination in respect to interoperability.</style></abstract><notes><style face="normal" font="default" size="100%">unable to find concise description of the data used [ms]</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Özel, Bülent</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Hypergraph Based Approach for Unlocking Power Relations in Rhizomatic Open Source Software Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/626</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">272</style></pages><abstract><style face="normal" font="default" size="100%">This study, first, points the rhizomatic nature of open source software (OSS) communities. Then, it proposes an hypergraph based research methodology both to capture and to analyze dynamics of OSS communities. An exemplary hypergraph theoretical analysis of power antecedence within rhizomatic network of an OSS community is illustrated.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lundestad, Christian V.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Idealism and Commercialism – Developing Free/Libre and Open Source Software in Private Businesses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">dominance</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS community</style></keyword><keyword><style  face="normal" font="default" size="100%">free/libre</style></keyword><keyword><style  face="normal" font="default" size="100%">legitimacy</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">Private Businesses</style></keyword><keyword><style  face="normal" font="default" size="100%">social organisation</style></keyword><keyword><style  face="normal" font="default" size="100%">theories of power</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/970</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">301-302</style></pages><abstract><style face="normal" font="default" size="100%">This paper presents a PhD research project undertaken as part of a larger project aimed at paying sociological attention to different forms of distribution of knowledge, including program code. We want to investigate empirically how the commons knows as free/open source software is actually made. In my PhD project I study the use and development of FLOSS in private businesses, focusing on professional developers working in private businesses and at the same time participating in the FLOSS community. The theoretical starting point is theories of power, dominance and legitimacy by Max Weber and Pierre Bourdieu.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Megías, David</style></author><author><style face="normal" font="default" size="100%">Serra, Jordi</style></author><author><style face="normal" font="default" size="100%">Macau, Rafael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An International Master Programme in Free Software in the European Higher Education Space</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">FS community</style></keyword><keyword><style  face="normal" font="default" size="100%">GNU/Linux</style></keyword><keyword><style  face="normal" font="default" size="100%">learning</style></keyword><keyword><style  face="normal" font="default" size="100%">master programme</style></keyword><keyword><style  face="normal" font="default" size="100%">software development</style></keyword><keyword><style  face="normal" font="default" size="100%">university</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/713</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">349-352</style></pages><abstract><style face="normal" font="default" size="100%">The Universitat Oberta de Catalunya (Open University of Catalonia, UOC) offers an International Master programme in Free Software. The first edition of this master programme began on November 2003 and there are about 240 students currently enrolled at the different specialities offered by the program. In this paper, the design, the methodology and the first few conclusions drawn from this higher education experience are discussed and summarized. After this master programme was changed to accomplish with European Higher Education Space (EHES).</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gale, Stephen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Investigation of Developer and User Activity In FLOSS Projects</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">developer</style></keyword><keyword><style  face="normal" font="default" size="100%">development</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">FLOSS project</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">pattern</style></keyword><keyword><style  face="normal" font="default" size="100%">portal</style></keyword><keyword><style  face="normal" font="default" size="100%">project</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/712</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">307-308</style></pages><abstract><style face="normal" font="default" size="100%">This document outlines research plans to investigate the evolution of a set of FLOSS (Free, Libre, and Open Source Software) projects and their communities by looking at patterns of developer and user activity through a combination of analysis of archived material and interaction with the project communities. The goal of the proposed research is to better understand the dynamics within FLOSS projects and how some projects become successful.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Lorenzo Benussi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Knowledge, Communication and Innovation: the case of Open Source Software as Open Media</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">attributive</style></keyword><keyword><style  face="normal" font="default" size="100%">Creative Commons</style></keyword><keyword><style  face="normal" font="default" size="100%">non-commercial</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/972</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">314-316</style></pages><abstract><style face="normal" font="default" size="100%">The understanding of the major characteristics of Linux Operative System and, more in general, the analysis of the so-called Open Source Phenomenon, is nowadays a central issue in order to appreciate the ongoing evolution of software industry. Free/Open Source Software model may appears a “revolution” in the way of thinking about software development, distribution and use. But, at a closer glance, it reveals itself more as an “evolution” along the path of “tinkering with software” typical of the Hacker Tech-Culture since the beginning of sixties. In fact the “open source way” of developing software results from the hackers habit of sharing technological knowledge and it represents a perfection of this, due to the availably of new communication technologies. The aim of this research is to explain this evolution, to point out its historical, economics and technological determinants and to link it with the evolution of the “communicational medium” used by the open source ...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Siewicz, Krzysztof</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Legal issues of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cooperation</style></keyword><keyword><style  face="normal" font="default" size="100%">copyright law</style></keyword><keyword><style  face="normal" font="default" size="100%">freedom</style></keyword><keyword><style  face="normal" font="default" size="100%">intellectual property</style></keyword><keyword><style  face="normal" font="default" size="100%">legal issue</style></keyword><keyword><style  face="normal" font="default" size="100%">license</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/974</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">320-321</style></pages><abstract><style face="normal" font="default" size="100%">From the legal standpoint, Open Source amounts to distributing rights and obligations in software license agreements in such a way, that they would (1) both grant users control over the program and (2) facilitate the sharing of improvements. The Open Source idea aims at reversing the process usually referred to as proprietary licensing and equaling the rights of the users with these of the authors. To some extent, it attempts to destroy monopolies created by copyright laws and to prevent them to arise again. There is much in the discussion on the legal issues of Open Source. The first voices came from the programmers who started the movement.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Antoniol, Giuliano</style></author><author><style face="normal" font="default" size="100%">Rollo, Vincenzo Fabio</style></author><author><style face="normal" font="default" size="100%">Venturi, Gabriele</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Linear predictive coding and cepstrum coefficients for mining time variant information from software repositories</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">data mining</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">files</style></keyword><keyword><style  face="normal" font="default" size="100%">kernel</style></keyword><keyword><style  face="normal" font="default" size="100%">linear predictive coding</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">lpc</style></keyword><keyword><style  face="normal" font="default" size="100%">size</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083156</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/74LinearPredictive.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">74-78</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">This paper presents an approach to recover time variant information from software repositories. It is widely accepted that software evolves due to factors such as defect removal, market opportunity or adding new features. Software evolution details are stored in software repositories which often contain the changes history. On the other hand there is a lack of approaches, technologies and methods to efficiently extract and represent time dependent information. Disciplines such as signal and image processing or speech recognition adopt frequency domain representations to mitigate differences of signals evolving in time. Inspired by time-frequency duality, this paper proposes the use of Linear Predictive Coding (LPC) and Cepstrum coefficients to model time varying software artifact histories. LPC or Cepstrum allow obtaining very compact representations with linear complexity. These representations can be used to highlight components and artifacts evolved in the same way or with very similar evolution patterns. To assess the proposed approach we applied LPC and Cepstral analysis to 211 Linux kernel releases (i.e., from 1.0 to 1.3.100), to identify files with very similar size histories. The approach, the preliminary results and the lesson learned are presented in this paper.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Susana Nunes,</style></author><author><style face="normal" font="default" size="100%">Flávio Moringa</style></author><author><style face="normal" font="default" size="100%">Miguel Lourenço</style></author><author><style face="normal" font="default" size="100%">Paulo Trezentos</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Linux on the portuguese schools: the Caixa Mágica experience</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">279-280</style></pages><abstract><style face="normal" font="default" size="100%">This article depicts the experience of Caixa Mágica
in the deployment of 14.000 computers with dual boot in the
portuguese schools. Caixa Mágica role was preparing its
Linux distribution to become friendly to students and
teachers.
This project was very successful and is now beginning with a
second phase with 5.000 more computers.
In this experience report with present some of the obstacles
and achievements accomplished in “Salas TIC”.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Baldoni, Matteo</style></author><author><style face="normal" font="default" size="100%">Baroglio, Cristina</style></author><author><style face="normal" font="default" size="100%">Roversi, Luca</style></author><author><style face="normal" font="default" size="100%">Grandi, Claudio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Live! I-Learn @ Home</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">e-learning</style></keyword><keyword><style  face="normal" font="default" size="100%">environment</style></keyword><keyword><style  face="normal" font="default" size="100%">GNU/Linux</style></keyword><keyword><style  face="normal" font="default" size="100%">java</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">technology</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/977</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">294-295</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we present a live CD based on GNU/Linux (Knoppix), customized in order to supply a complete working and studying environment for the students of the Corso di Studi in Informatica. In particular, it supplies the Moodle course management system for e-learning complete of the courses of the first year. The aim is to enable the use of such resources off-line and without requiring special skills that will be achieved by studying but that newbies do not have.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Teli, Maurizio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Looking at Free and Open Source Software: A Study about F/OSS Developers' Culture</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cultural analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cultural study</style></keyword><keyword><style  face="normal" font="default" size="100%">cyber</style></keyword><keyword><style  face="normal" font="default" size="100%">F/OSS developers</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">software development</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/968</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">324-325</style></pages><abstract><style face="normal" font="default" size="100%">My work will be a cultural study of a F/OSS development project, mixing a symmetric approach with the interaction analysis by Erving Goffman. Methodologically I will approach cyber – ethnography.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiss, Dawid</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Measuring Success of Open Source Projects Using Web Search Engines</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://hdl.handle.net/2038/973</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">93-99</style></pages><abstract><style face="normal" font="default" size="100%">What makes an open source project successful? In this paper we show that the traditional factors of success of open source projects, such as the number of downloads, deployments or community activity are inconvenient to collect or insufficient. We then correlate success of an open source project with its popularity on the Web. We show several ideas of how such popularity could be measured using Web search engines and provide experimental results from quantitative analysis of the measures we introduce on representative large samples of open source projects from SourceForge.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Colasanti, Cecilia</style></author><author><style face="normal" font="default" size="100%">Patruno, Vincenzo</style></author><author><style face="normal" font="default" size="100%">Vaccari, Carlo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Migrazione di un Sistema Informativo da UNIX-AIX a UNIX-Linux</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">architettura hardware</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">migrazione</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">server</style></keyword><keyword><style  face="normal" font="default" size="100%">sistema informativo</style></keyword><keyword><style  face="normal" font="default" size="100%">sistema proprietario</style></keyword><keyword><style  face="normal" font="default" size="100%">unix aix</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/978</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">287-288</style></pages><abstract><style face="normal" font="default" size="100%">Il presente documento ha come obiettivo quello di descrivere la politica adottata dall'Istituto Nazionale di Statistica rispetto all'uso del software Open Source. In particolare vengono descritti i sistemi che attualmente operano su piattaforma Linux, quelli che sono in fase di migrazione e le scelte che si sono fatte nel caso di convivenza tra sistemi “open” e sistemi “proprietari”. Viene inoltre illustrata l'architettura hardware scelta nel caso della migrazione di un sistema complesso da piattaforma interamente proprietaria (UNIX AIX) a piattaforma con sistema operativo open Linux Red Hat.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Fischer, Michael</style></author><author><style face="normal" font="default" size="100%">Oberleitner, Johann</style></author><author><style face="normal" font="default" size="100%">Ratzinger, Jacek</style></author><author><style face="normal" font="default" size="100%">Gall, Harald</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining evolution data of a product family</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bsd</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">freebsd</style></keyword><keyword><style  face="normal" font="default" size="100%">netbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">openbsd</style></keyword><keyword><style  face="normal" font="default" size="100%">release history</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">text mining</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083145</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/12MiningEvolution.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">12-16</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Diversification of software assets through changing requirements impose a constant challenge on the developers and maintainers of large software systems. Recent research has addressed the mining for data in software repositories of single products ranging from fine- to coarse grained analyses. But so far, little attention has been payed to mining data about the evolution of product families. In this work, we study the evolution and commonalities of three variants of the BSD (Berkeley Software Distribution), a large open source operating system. The research questions we tackle are concerned with how to generate high level views of the system discovering and indicating evolutionary highlights. To process the large amount of data, we extended our previously developed approach for storing release history information to support the analysis of product families. In a case study we apply our approach on data from three different code repositories representing about 8.5GB of data and 10 years of active development.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Huang, Shih-Kun</style></author><author><style face="normal" font="default" size="100%">Liu, Kang-min</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mining version histories to verify the learning process of Legitimate Peripheral Participants</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">awstats</style></keyword><keyword><style  face="normal" font="default" size="100%">bzflag</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">filezilla</style></keyword><keyword><style  face="normal" font="default" size="100%">gallery</style></keyword><keyword><style  face="normal" font="default" size="100%">Legitimate Peripheral Participants (LPP)</style></keyword><keyword><style  face="normal" font="default" size="100%">moodle</style></keyword><keyword><style  face="normal" font="default" size="100%">open boundary</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software development process</style></keyword><keyword><style  face="normal" font="default" size="100%">phpmyadmin</style></keyword><keyword><style  face="normal" font="default" size="100%">social networks</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083158</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/84MiningVersion.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">84-88</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Since code revisions reflect the extent of human involvement in the software development process, revision histories reveal the interactions and interfaces between developers and modules.We therefore divide developers and modules into groups according to the revision histories of the open source software repository, for example, sourceforge.net. To describe the interactions in the open source development process, we use a representative model, Legitimate Peripheral Participation (LPP) [6], to divide developers into groups such as core and peripheral teams, based on the evolutionary process of learning behavior.With the conventional module relationship, we divide modules into kernel and non-kernel types (such as UI). In the past, groups of developers and modules have been partitioned naturally with informal criteria. In this work, however, we propose a developer-module relationship model to analyze the grouping structures between developers and modules. Our results show some process cases of relative importance on the constructed graph of project development. The graph reveals certain subtle relationships in the interactions between core and non-core team developers, and the interfaces between kernel and non-kernel modules.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alessandro Narduzzo</style></author><author><style face="normal" font="default" size="100%">Rossi, Alessandro</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Modular Design and the Development of Complex Artifacts: Lessons from Free/Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/979</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">162-171</style></pages><abstract><style face="normal" font="default" size="100%">Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of development methodologies and practices in Free/Open Source software projects. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of various Free/Open Source Software projects (among them: the GNU operating system, the Linux kernel, the HURD kernel). It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Specific case studies here depicted, as well as indirect observation of common programming practices employed by Free/Open Source developers and users, suggest a possible revision towards an improved theory of modularity that may be extended also to settings different from software production.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Noll, John</style></author><author><style face="normal" font="default" size="100%">Elliott, Margaret</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Multi-Modal Modeling of Open Source Software Requirements Processes</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/975</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">1-8</style></pages><abstract><style face="normal" font="default" size="100%">Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies however have revealed that the requirements processes in OSSD projects are different in a number of ways, including the general lack of explicit software requirements specifications. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software requirements processes found in OSSD projects, with examples drawn from studies of the NetBeans.org project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Onetti, Alberto</style></author><author><style face="normal" font="default" size="100%">Capobianco, Fabrizio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source and Business Model Innovation. The Funambol case</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/967</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">224-227</style></pages><abstract><style face="normal" font="default" size="100%">A comprehensive theoretical framework about open source business models is still missing, notwithstanding a growing number of contributions. This lack of literature is mainly due to the relative newness of the phenomena. This paper aims at giving a contribution to the ongoing discussion about open source business implications. The research hypothesis is that open source represents a disruptive innovation for the software industry. The purpose is to understand, through case study research, how open source companies can develop successful business models. Funambol provides an interesting example of an optimized business model, able to leverage the open source advantage in an emerging market. The paper is structured in three main parts: the first one aims at outlining the research hypothesis and methodology. The second part identifies the unique competitive factors distinguishing open source business and the main business implications. The final part focuses on the analys...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Griffiths, David</style></author><author><style face="normal" font="default" size="100%">Blat, Josep</style></author><author><style face="normal" font="default" size="100%">Elferink, Ray</style></author><author><style face="normal" font="default" size="100%">Zondergeld, Sara</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source and IMS Learning Design: Building the Infrastructure for eLearning</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">eLearning</style></keyword><keyword><style  face="normal" font="default" size="100%">eLearning specification</style></keyword><keyword><style  face="normal" font="default" size="100%">FOSS</style></keyword><keyword><style  face="normal" font="default" size="100%">infrastructure</style></keyword><keyword><style  face="normal" font="default" size="100%">Learning Design</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1264</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">329-333</style></pages><abstract><style face="normal" font="default" size="100%">The development of open, flexible eLearning specifications has significant implications for and interactions with the FOSS movement. A short overview of eLearning specifications is provided, focusing on the difference between SCORM and Learning Design (LD). The significance of LD for FOSS is examined, and common values identified. The particular contribution made by FOSS to LD infrastructure is discussed, and the importance of reference applications described. An overview is given of the FOSS applications available, divided into design time and run time, with particular reference to LD editors and the CopperCore Learning Design engine.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Bonaccorsi</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source firms: from community to business</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">business</style></keyword><keyword><style  face="normal" font="default" size="100%">COMMUNITY</style></keyword><keyword><style  face="normal" font="default" size="100%">firms</style></keyword><keyword><style  face="normal" font="default" size="100%">Open Source firms</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1265</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">362-363</style></pages><abstract><style face="normal" font="default" size="100%">A large body of literature is now addressing the Open Source (OS) phenomenon. Economic scholars have deeply investigated the incentives of people working within OS community projects; the software production models in absence of explicit hierarchical structures; the successful dissemination of OS programs in environments dominated by proprietary standards; the peculiarities in the management of intellectual property within the OS framework. Theoretical contributions have coupled with the collection of extensive empirical evidence mainly through surveys taken on individual developers. Nowadays a new trend is shaping the OS movement: more and more firms are entering the market by offering software solutions based on the new paradigm (Open Source firms).</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gammeri, Simone</style></author><author><style face="normal" font="default" size="100%">Di Cerbo, Francesco</style></author><author><style face="normal" font="default" size="100%">Scotto, Marco</style></author><author><style face="normal" font="default" size="100%">Succi, Giancarlo</style></author><author><style face="normal" font="default" size="100%">Vernazza, Tullio</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source for e-Government Application Integration: a PHP-based solution</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/index.jsp</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">204-208</style></pages><abstract><style face="normal" font="default" size="100%">This paper introduces UniGeINT - University of Genoa Integration Tool -, a framework designed to provide integration between several existing tools, databases and data repositories we used in internal administrative processes, by exploiting OSS benefits in terms of costs reduction and bug reporting. Moreover, it adopts state-of-art solutions in Enterprise Application Integration, by using specific design patterns able to match existing IT marrow. So we required in final product common features unmissable for a large scale corporative environment: reliability and fault tolerance, besides to a complete integration with anything previously developed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Davini, Emanuela</style></author><author><style face="normal" font="default" size="100%">Faggioni, Elisabetta</style></author><author><style face="normal" font="default" size="100%">Granatella, Giampiero</style></author><author><style face="normal" font="default" size="100%">Tartari, Dimitri</style></author><author><style face="normal" font="default" size="100%">Scotto, Marco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Software in Public Administration. A real example OSS for egovernment Observatories</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1208</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">119-124</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) has risen to great prominence. Briefly, OSS programs are programs whose licenses give users the freedom to run the program for any purpose, to study and modify the program, and to redistribute copies of either the original or modified program (without having to pay royalties to previous developers). In the last years the Italian Public Administrations (PA) points out the benefits of using OSS as a valid alternative to closed source software. The goal of this paper is to illustrate the state of the art of OSS in Italian PA and describe two pratical examples of the use of OSS in the e-government area. Those examples are represented by the local e-government observatories developed respectively by Emilia Romagna and Liguria Regions. A real and settled knowledge about current and past egovernment initiatives in Italy can improve the future planning. For these reasons several Italian Regions developed Observatories for e-Government and Informatio...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Andrea Bonaccorsi</style></author><author><style face="normal" font="default" size="100%">Cristina Rossi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source software, intrinsic motivations and profit-oriented firms. Do not firms practise what they preach?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">241-245</style></pages><abstract><style face="normal" font="default" size="100%">This paper contributes to the literature by
providing empirical evidence on the incentives of firms that
engage in Open Source activities. Data collected by a survey
on 146 Italian companies supplying OS solutions (Open
Source firms) show that (surprisingly) intrinsic, communitybased
incentives do play a role but are not, in general, put into
practise. The discrepancy between attitudes and behaviours is
investigated and firms adopting more consistent behaviours
are singled out. Our results are in line with the literature on
business models of firms entering the Open Source field.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martinez, Arturo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source, a development option</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1261</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">228-230</style></pages><abstract><style face="normal" font="default" size="100%">The Open Source (OS) movement is one of the most amazing revolutions in last decades. It is probably the most successful collaborative project in history. Its philosophy: learn, innovate and share, has created an immense knowledge base which has been opened to everyone. It brings technology to everybody and empowers people, communities, governments and companies. The purpose of this paper is to show how OS solutions, methods and communities can support a number of key areas for a nation's development, at the same time that generates its own infrastructure which not only supports development but also has the potential to become a main business activity for that nation.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hu, Bao-Gang</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source: Toward Innovations through Educational Development in China</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1259</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">254-258</style></pages><abstract><style face="normal" font="default" size="100%">This paper describes the author's personal viewpoints toward open source software, particularly for the educational development in China. The current status of China is presented to explain why open source is critical within the Chinese educational domain. We believe that open source is suitable not only for financial reasons, but also because it will provide an efficient solution for China to establish an innovative environment whilst promoting intellectual capacities. The benefits of using open source are ideal for the current situations in the Chinese educational system. In this paper, one example is given about the promotion activities of the open source software Scilab (SCILAB(c)INRIA-ENPC) in the Chinese educational domain since 2001. Activities demonstrate that open source ideas and practices will have a great impact in China. Lessons and progress are demonstrated from these activities. The final goal of the Chinese educational development is to increase innovati...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tiangco, Francis</style></author><author><style face="normal" font="default" size="100%">Stockwell, Alison</style></author><author><style face="normal" font="default" size="100%">Sapsford, John</style></author><author><style face="normal" font="default" size="100%">Rainer, Austen</style></author><author><style face="normal" font="default" size="100%">Swanton, Eamonn</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open-source software in an occupational health application: the case of Heales Medical Ltd.</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1257</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">130-134</style></pages><abstract><style face="normal" font="default" size="100%">In this paper, we provide a case study of a small company, Heales Medical Ltd., that has chosen to use opensource software to develop an online integrated patient management system. We use this case study to examine some preconceptions of open-source technology in the light our experiences of open source in the Heales project. We identify costs and cost savings as being the primary business considerations, and identify software purchase and licensing as key advantages for open-source. We then look at development issues including software evaluation, implementation and programming, and identify these as more costly for open-source, in terms of time and effort expended. We also look at issues to do with open source licensing, which our initial investigations suggest is confusing and requires further analysis. Overall, the ability to modify the source code is regarded as a key benefit of open-source software, but in a business environment like Heales, this is of little imp...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Giacalone, Paolo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OSS implementation solutions for Public Administration applications</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1420</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">259-262</style></pages><abstract><style face="normal" font="default" size="100%">The paper will address the approach used by our company to develop an electronic certified mail solution, called eCertMail, which allows the transmission of documents in electronic form guaranteeing their sending and their reception from a legal point of view, using OS technologies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sissa, Giovanna</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Osservatorio Tecnologico: services for open source software at school</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1421</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">269</style></pages><abstract><style face="normal" font="default" size="100%">Technology Transfer is a keyword in ICT field. OsservatorioTecnologico, the Italian web based national service for technology transfer from ICT to schools, ever since the beginning indicated the Open Source Software (OSS) as one of the main topics. Several services are provided to schools, for example: dissemination of OSS Best Practices in education, guideline about OSS for public sector, monitoring OSS spreading in schools.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Conklin, Megan</style></author><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OSSmole: A collaborative repository for FLOSS research data and analyses</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1422</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">54-60</style></pages><abstract><style face="normal" font="default" size="100%">This paper introduces a collaborative project, “OSSmole”, designed to gather, share and store comparable data and analyses of free and open source software development for academic research. The project draws on the ongoing collection and analysis efforts of many research groups, reducing duplication, and promoting compatibility both across sources of FLOSS data and across research groups and analyses. The paper outlines current difficulties with the current typical quantitative FLOSS research process and uses these to develop requirements and presents the design of the system.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bencetti, Stefano</style></author><author><style face="normal" font="default" size="100%">Verduci, Gianni</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">OTRS: un sistema a ticket per la gestione dell’help desk</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">help desk</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">ticketing system</style></keyword><keyword><style  face="normal" font="default" size="100%">trouble ticket</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1423</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">281</style></pages><abstract><style face="normal" font="default" size="100%">Descriviamo l’esperienza di utilizzo di un software a codice sorgente aperto per la gestione a ticket dell’help desk informatico del D.I.S.I. (Dipartimento di Informatica e Scienze delll’Informazione) dell’Università degli Studi di Genova.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Müller, Benoît</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Principles for a Dynamic Software Ecosystem</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1424</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">267</style></pages><abstract><style face="normal" font="default" size="100%">The open source software movement reflects one of the most dramatic developments in today’s dynamic information technology industry. Interestingly, some commentators have sought to posit open source against proprietary software. This paper argues that while open source and proprietary models may be based on different development and distribution philosophies, neither model is inherently superior.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">De Prato, Giuditta</style></author><author><style face="normal" font="default" size="100%">Gagliardi, Dimitri</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Proprietary Software and Open Source Philosophy: a shift in software’s production methods</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">ttp://pascal.case.unibz.it/handle/2038/1425</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">237-240</style></pages><abstract><style face="normal" font="default" size="100%">The aim of this paper is to point out that, since the massive growth of Open Source Software (OSS), the production methods of software have changed. The change is not only recognisable within the OSS communities but most evident effects can be also observed in the “proprietary” segment of the market. The data analysis has been performed by allocating a variation towards or away from cooperation/ competition according to the direction of about 12,000 communications, articles and technical notes dated from 1998 up to February 2005. A co-evolution path is identifiable: both the OSS and the proprietary models interchange their original market and production strategies. In the case of the OSS segment, market strategies becomes more business oriented; as a result, systems previously based solely on remote users/producers relations exchange some of the redundancy in its process in favour of a more businessdriven and coordinated production process. On the other hand, proprieta...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Martin Michlmayr</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quality Improvement in Volunteer Free Software Projects: Exploring the Impact of Release Management</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">free software</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">process improvement</style></keyword><keyword><style  face="normal" font="default" size="100%">quality assurance</style></keyword><keyword><style  face="normal" font="default" size="100%">release management</style></keyword><keyword><style  face="normal" font="default" size="100%">volunteer projects</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1429</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">309-310</style></pages><abstract><style face="normal" font="default" size="100%">Even though free software has achieved great popularity and success in recent years, there are a number of product quality challenges facing the open source development model. There is significant room for further quality improvement and one area that deserves special attention is release management. This research will identify problems with current release practices, verify possible advantages of an increasingly popular release model, and develop interventions to improve release management in free software projects. The research also aims to answer the fundamental question as to how volunteer projects can deliver predictable and high quality software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Nikula, Uolevi</style></author><author><style face="normal" font="default" size="100%">Jantunen, Sami</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quantifying the Interest in Open Source Systems: Case South-East Finland</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1434</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">192-195</style></pages><abstract><style face="normal" font="default" size="100%">Open source systems (OSS) has emerged as one of the most interesting phenomena in software engineering today. Unfortunately, only little hard data is available to quantify the interest in OSS in commercially operating software houses. As a part of a local initiative to increase the alignment between the software industry and software engineering research and education, a state of the practice survey was conducted in the local software houses. Due to the globally recognized interest in OSS some explorative questions on the topic were included in the survey. The results of the survey indicate widespread interest in OSS in the industry, and even though the study had a strictly regional focus, the results provide quantitative support for future research on OSS.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Weiss, Dawid</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Quantitative Analysis of Open Source Projects on SourceForge</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1430</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">140-147</style></pages><abstract><style face="normal" font="default" size="100%">Relatively easy accessibility of high volumes of information about open source software makes it an interesting target for quantitative analysis meant to discover some hidden properties and trends of this software development model. In this work we demonstrate how such information can be acquired from the largest open source hosting facility — SourceForge — with nearly minimal effort. We compare our data with an identical data set collected a few months earlier by the OssMole [2] project, of which we were not aware at the time of performing the experiment, but which allowed us to make some interesting cross-comparisons and derive conclusions about temporal changes going on at SourceForge.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Williams, Chadd C.</style></author><author><style face="normal" font="default" size="100%">Hollingsworth, Jeffrey K.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Recovering system specific rules from software repositories</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">function usage patterns</style></keyword><keyword><style  face="normal" font="default" size="100%">functions</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">wine</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083144</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/7Recovering.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">7-11</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">One of the most successful applications of static analysis based bug finding tools is to search the source code for violations of system-specific rules. These rules may describe how functions interact in the code, how data is to be validated or how an API is to be used. To apply these tools, the developer must encode a rule that must be followed in the source code. The difficulty is that many of these system-specific rules are undocumented and &quot;grow&quot; over time as the source code changes. Most research in this area relies on expert programmers to document these little-known rules. In this paper we discuss a method to automatically recover a subset of these rules, function usage patterns, by mining the software repository. We present a preliminary study that applies our work to a large open source software project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Drozdik, Sylvester</style></author><author><style face="normal" font="default" size="100%">Kovács, George L.</style></author><author><style face="normal" font="default" size="100%">Kochis, Pál Zoltán</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Risk Assessment of an Open Source Migration Project</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1432</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">246-249</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we investigate the risks of an Open Source migration in the small Public Administration (PA) area. We consider not just technical risks (like security or reliability), but strategic issues (like e-government priorities, mid-term ownership cost items) and some social relations are also taken into consideration.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Conlon, Pat</style></author><author><style face="normal" font="default" size="100%">Carew, Peter</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Risk Driven Framework for Open Source Information Systems Development</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/617</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">200-203</style></pages><abstract><style face="normal" font="default" size="100%">This paper attempts to justify the need for a framework to address concerns with the use of open source software for information systems development (ISD). The premise of this argument is that the open source paradigm primarily addresses technical concerns while IS failures tend to be multifaceted in nature. OSS may improve but will not ultimately solve the problems of ISD due to its inherent sociotechnical complexities. Issues of concern for open source ISD are identified in this paper and a theoretical framework is outlined allowing organisations to take a more balanced approach to open source ISD. The framework is predicated upon risk management and a lifecycle that addresses social and organisational concerns throughout the ISD process. The objective of this framework is to aid in avoidance of the social and organisational pitfalls of ISD while leveraging the ability of the OSS paradigm to address software crisis issues. Finally, the implications of this framework a...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hoffman, Tom</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SchoolTool: Defining Our Niche in the Open Source Architecture of Schools</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">information system</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">school</style></keyword><keyword><style  face="normal" font="default" size="100%">student</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1436</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">334-337</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hindle, Abram</style></author><author><style face="normal" font="default" size="100%">Daniel M. German</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SCQL: a formal model and a query language for source control repositories</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">file</style></keyword><keyword><style  face="normal" font="default" size="100%">gnumeric</style></keyword><keyword><style  face="normal" font="default" size="100%">modperl</style></keyword><keyword><style  face="normal" font="default" size="100%">openssl</style></keyword><keyword><style  face="normal" font="default" size="100%">revision</style></keyword><keyword><style  face="normal" font="default" size="100%">samba</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083161</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/100scql.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">100-104</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Source Control Repositories are used in most software projects to store revisions to source code files. These repositories operate at the file level and support multiple users. A generalized formal model of source control repositories is described herein. The model is a graph in which the different entities stored in the repository become vertices and their relationships become edges. We then define SCQL, a first order, and temporal logic based query language for source control repositories. We demonstrate how SCQL can be used to specify some questions and then evaluate them using the source control repositories of five different large software projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matusow, Jason</style></author><author><style face="normal" font="default" size="100%">McGibbon, Stephen</style></author><author><style face="normal" font="default" size="100%">Rowe, David</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Shared Source and Open Solutions: an e-Government Perspective</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/736</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">263-266</style></pages><abstract><style face="normal" font="default" size="100%">Over the past four years, increasing commercialisation has been a significant influence on free and open source software. At the same time, the community based collaborative development model, which generally connotes open source, has also been studied and adopted by traditional software companies. These trends have led to an understanding that what separates open source from other software development approaches is the licensing model rather than the development model. Despite this, the two paradigms are rapidly starting to look very similar as open source is increasingly commercialised and established software companies integrate community based development into their value chain. This paper presents Microsoft’s experience with its Intellectual Property Sharing programs and Shared Source Initiative. We also present the Solution Sharing Network, an environment that facilitates the sharing of solutions and best practices. We focus here on public sector customers who ...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gabriele Gianini</style></author><author><style face="normal" font="default" size="100%">Sillitti, Alberto</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Sharing ExperienceS on Agile Methodologies in Open Source Software development SESAMOSS 2005</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">361</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Coleman, E.G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The social construction of freedom in free and open source software: Hackers, ethics, and the liberal tradition</style></title><secondary-title><style face="normal" font="default" size="100%">Anthropology</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">culture</style></keyword><keyword><style  face="normal" font="default" size="100%">hacker</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">University of Chicago</style></publisher><pub-location><style face="normal" font="default" size="100%">Chicago, Illinois</style></pub-location><volume><style face="normal" font="default" size="100%">PhD</style></volume><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This dissertation, based on fieldwork conducted between January 2001 and May 2003 on the Debian free software project and among hackers living in the Bay area, is an ethnography focused on the ethics and politics of free and open source hackers. My aim in this dissertation is to evaluate the rise of expressive rights among hackers as a historically and culturally specific practice of liberal freedom that can only be made sensible through the lens of a hacker technical way of life--in which their pragmatics and poetics are given serious consideration. Moving and integrating various levels of analysis: the phenomenology of technical praxis, the sociological creation of an ethical practice that unfolds in the hacker public sphere and the FOSS project, and the historical rise of reflective signification through overt political dissent, I offer a comprehensive account of how hackers have come to value and enact freedom, what they mean by it, and suggest some ideas about the broader political effects of their practices. Instead of an emphasis of self-determination and individuality based on the acquisition of property, hackers have placed emphasis on individuality as a form of critical self-determination that requires unrestricted access to knowledge in order to constantly develop technical skills and to progress the state of their technical art. Important for the purposes of this dissertation is that hackers challenge one sacred realm of liberal jurisprudence--intellectual property--by drawing on and reformulating ideals from another one--free speech.</style></abstract><work-type><style face="normal" font="default" size="100%">PhD Dissertation</style></work-type><custom3><style face="normal" font="default" size="100%">phdthesis</style></custom3><label><style face="normal" font="default" size="100%">coleman2005</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Wagstrom, Patrick Adam</style></author><author><style face="normal" font="default" size="100%">Herbsleb, James</style></author><author><style face="normal" font="default" size="100%">Carley, Kathleen</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Social Network Approach To Free/Open Source Software Simulation</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">social network analysis</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.178.4984</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">16-23</style></pages><abstract><style face="normal" font="default" size="100%">Free and Open Source Software (F/OSS) development is a complex process that is just beginning to be understood. The actual development process is frequently characterized as disparate volunteer developers collaborating to create a piece of software. The developers of F/OSS, like most software engineers, spend a significant portion of their time fostering collaboration through various channels social communication. We have analyzed several methods of communication; a social networking site, project mailing lists, and developer weblogs; to gain an understanding of the social network structure behind F/OSS projects. This social network data was used to create a model of F/OSS development that allows for multiple projects, users, and developers with varying goals and socialization methods. Using this model we have been able to replicate some of the known phenomena observed in F/OSS and provide a first step in the creation of a robust model of F/OSS. </style></abstract><notes><style face="normal" font="default" size="100%">&quot;Second, we use mailing list archives for three different projects. This gives us a more stringent network measure, since links are generated only when one developer communicates directly with another.&quot;
 
&quot;The mailing lists were the developers list from a well deployed database server, the general list for an text and file processing library, and the general list for a smaller F/OSS web browser.&quot;</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">DUCHENEAUT, NICOLAS</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Socialization in an Open Source Software Community: A Socio-Technical Analysis</style></title><secondary-title><style face="normal" font="default" size="100%">Computer Supported Cooperative Work (CSCW)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archive</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">open source project browser</style></keyword><keyword><style  face="normal" font="default" size="100%">participation</style></keyword><keyword><style  face="normal" font="default" size="100%">python</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword><keyword><style  face="normal" font="default" size="100%">tools</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://dx.doi.org/10.1007/s10606-005-9000-1</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer Netherlands</style></publisher><volume><style face="normal" font="default" size="100%">14</style></volume><pages><style face="normal" font="default" size="100%">323-368</style></pages><abstract><style face="normal" font="default" size="100%">Open Source Software (OSS) development is often characterized as a fundamentally new way to develop software. Past analyses and discussions, however, have treated OSS projects and their organization mostly as a static phenomenon. Consequently, we do not know how these communities of software developers are sustained and reproduced over time through the progressive integration of new members. To shed light on this issue I report on my analyses of socialization in a particular OSS community. In particular, I document the relationships OSS newcomers develop over time with both the social and material aspects of a project. To do so, I combine two mutually informing activities: ethnography and the use of software specially designed to visualize and explore the interacting networks of human and material resources incorporated in the email and code databases of OSS. Socialization in this community is analyzed from two perspectives: as an individual learning process and as a political process. From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts. I conclude by discussing how these results could inform the design of software to support socialization in OSS projects, as well as practical implications for the future of these projects.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;I present the results of my analyses of participation patterns in a particular OSS project, used as a case study: Python. More precisely, I use the Open Source Project Browser to qualitatively track and analyze the trajectories of several project members who evolved (or not) into full-fledged participants. This allows me to later discuss how socialization proceeds in an OSS community such as Python&quot;

&quot;Over the course of 2002, I progressively retrieved the entire email archive of python-dev (the developers’ mailing list) and the CVS source tree for the project. &quot;

&quot;I read the entirety of the messages written by these participants and also looked at the software code they produced. There were striking similarities between their progressions over time, which I will de- scribe shortly. Overall the trajectory of these participants reflects successful socialization in Python: an evolution from newcomer to developer.&quot;

http://www2.parc.com/csl/members/nicolas/documents/JCSCW-OSS.pdf</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sandusky, Robert J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Software Problem Management as Information Management in a F/OSS Development Community</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1533</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">44-49</style></pages><abstract><style face="normal" font="default" size="100%">Bug reports created by a large, successful open source software development community show that software problem management (SWPM) is first of all information management and secondarily a problem solving activity. Solving software problems occurs only after a bug report, a first-class information object, has been created and “triaged” by community members. One predominant structural feature of defect tracking repositories is the evolving &quot;bug report network&quot; (BRN). Community members create BRNs by progressively asserting various formal and informal relationships between bug reports (BRs). In one F/OSS bug repository under study, participants assert two formal relationships (duplications and dependencies) and various informal relationships (like &quot;see also&quot; references). BRNs can be interpreted as (1) information ordering strategies that support collocation of related BRs, decreasing cognitive and organizational effort; (2) sense-making strategies wherein BRNs provide mor...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ven, Kris</style></author><author><style face="normal" font="default" size="100%">Sörensen, Kenneth</style></author><author><style face="normal" font="default" size="100%">Verelst, Jan</style></author><author><style face="normal" font="default" size="100%">Sevaux, Marc</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Stimulating Collaborative Development in Operations Research with libOR</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1534</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">71-75</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we describe the development of libOR, an on-line library for the operations research (OR) community. The design and operation of this website is inspired by the Open Source movement and recent developments such as Wikipedia. In operations research, data sets are exchanged between researchers in order to test the performance of newly developed algorithms. Currently, the exchange of these data sets suffers from many problems. One of the main problems is that data sets are currently exchanged through a centrally maintained website, which makes it slow to respond to new developments. By applying an Open Source approach to content creation, we hope to spur the diffusion of information within the operations research community.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Robert Heckman</style></author><author><style face="normal" font="default" size="100%">Hala Annabi</style></author><author><style face="normal" font="default" size="100%">Chengetai Masango</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A structurational perspective on leadership in Free/Libre Open Source Software teams</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/623</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">9-15</style></pages><abstract><style face="normal" font="default" size="100%">In this conceptual paper, we present a structuration- based theory of leadership behaviours in self-organizing distributed teams such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on a functional view of leadership and structuration theory, we suggest that leaders are individuals who develop team structures that then guide the actions of team members. Specifically, we examine structures of signification in the form of shared mental models, structures of domination in the form of role structures and structures of legitimation in form of rules and norms. The main contribution of our paper is the integration of various social theories to describe emergent leadership behaviours in distributed teams. We develop a set of prop...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sherae Daniel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Structure, Cohesion, and Open Source Software Success</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">interest community</style></keyword><keyword><style  face="normal" font="default" size="100%">network externalities</style></keyword><keyword><style  face="normal" font="default" size="100%">open source software</style></keyword><keyword><style  face="normal" font="default" size="100%">software quality</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1536</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">317-319</style></pages><abstract><style face="normal" font="default" size="100%">This paper proposes a dissertation designed to understand how the open source software (OSS) development group and its associated interest community jointly and independently impact OSS success for a single OSS project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ayre, Jamie</style></author><author><style face="normal" font="default" size="100%">Gasperoni, Franco</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A Successful Business Model for Free Software</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/627</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">135-139</style></pages><abstract><style face="normal" font="default" size="100%">The objective of this article is to offer a return on experience explaining how the legal fundamentals on which Free Software is based allow for a long-lasting business model based on a special kind of expert knowledge-based support that benefits customers and guarantees the creation of a local pool of expertise. This article is based on our experience with GNAT Pro. GNAT Pro is the Free Software development environment for the Ada 95 programming language. It comprises a compiler that is part of GCC (the GNU Compiler Collection), a toolset and graphical Integrated Development Environment, and a set of supporting libraries. Developing, maintaining, and marketing GNAT Pro for ten years have provided significant experience with both technical and non-technical aspects of Free Software. This article summarizes the principal legal and business lessons learned.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>13</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Shiyevina Amelia Abdool</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Theory Of FOSS And Its Acceptance In Developing Nations</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/FOSS_IN_POLITICS.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free and Open Source Software (FOSS) is on the march across the globe, and it offers a reliable alternative to proprietary, commercial products and addresses the full range of users' needs. For example FOSS Apache provides the majority of web pages due to its huge installed user base, with the last figures showing Apache occupying 67% of all web sites world wide.

Since FOSS is world class, (i.e. it is free to share/distribute amongst individuals, clients, offices, etc.) and can be modified according to an individual's/organization's motives, it may be viewed as a competitor to proprietary and commercial products. For instance, when compared to the existing standard, user-friendly programs that run on Microsoft Windows and Apple operating systems, FOSS offers alternate operating systems that can be used on all computer systems and a range of Internet server software with advanced functionality.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Bleek, Wolf-Gideon</style></author><author><style face="normal" font="default" size="100%">Finck, Matthias</style></author><author><style face="normal" font="default" size="100%">Pape, Bernd</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards an Open Source Development Process - Evaluating the Migration to an Open Source Project by Means of the Capability Maturity Model</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1543</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">37-43</style></pages><abstract><style face="normal" font="default" size="100%">In this paper we review the ongoing development of a Web-based community system that has been migrated from a closed software development to an open source project. We identify three different phases in the migration process where the development process changed significantly. We analyse these phases by means of the Capability Maturity Model (CMM). The insights gained show the implications of such a migration process towards open source concerning the process quality of a development process. They also show underlying assumptions of the CMM that do not totally match with developments in this specific case study. As a helpful outcome, our reflection about the ongoing software development process helped identify two crucial factors: reflection about the process is possible even at lower levels and how to handle people's fluctuation to sustain a development project.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Adams, Paul</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards Supporting Agile Practice Within The Libre Software Paradigm</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">agile methods</style></keyword><keyword><style  face="normal" font="default" size="100%">agile practice</style></keyword><keyword><style  face="normal" font="default" size="100%">extreme programming</style></keyword><keyword><style  face="normal" font="default" size="100%">libre software</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">XP</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1546</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">303-304</style></pages><abstract><style face="normal" font="default" size="100%">Individual agile methods have never been practiced as defined, in the same way that Royce's waterfall [1] model never reflected actual practice. Instead, practitioners adapted the core principles of these processes in order to suit their needs. Understanding this is key to appreciating the agile mindset. What does exist is a set of principles1 which, when followed loosely, form the agile practices. It is an important part of the agile mentality that the individuals within a project are more important that the process they follow. However, the individual methods do have their own identifying features that make them unique; for example testing must be performed before coding within eXtreme Programming (XP) [2]. However, if practitioners were to apply XP, exactly as Beck describes it, then they are probably not “doing agile” as they may not be following the process that suits their needs best. One of the interesting features of the XP method is its requirement of a collocated team. Th...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">González-Barahona, Jesús M.</style></author><author><style face="normal" font="default" size="100%">Chris Tebb</style></author><author><style face="normal" font="default" size="100%">Vania Dimitrova</style></author><author><style face="normal" font="default" size="100%">Chaparro, Diego</style></author><author><style face="normal" font="default" size="100%">Romera, Teo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Transfering Libre Software Development Practices to the Production of Educational Resources: the Edukalibre Project</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">educational resources</style></keyword><keyword><style  face="normal" font="default" size="100%">information systems</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">software development practices</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1548</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">341-348</style></pages><abstract><style face="normal" font="default" size="100%">The transfer of methodologies common in libre (free, open source) sofware development to the domain of educational resources can radically change the way educational content is developed and used, enabling both educational practitioners and students to become actively involved in its creation and distribution. New software architectures and tools are needed to effectively support this process. This paper describes a platform aimed to support the creation of free, collaboratively constructed educational content on the web, which has been developed within the Edukalibre project. It provides easy access to core technologies: a control version system combined with conversion tools to produce several convenient formats for each document. Its modular architecture offers many different interfaces to the users. The Edukalibre platform is distributed as libre software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Tartari, Dimitri</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Un'applicazione Open Source: l'Osservatorio sull'e-government e la società dell'informazione</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1550</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">291-293</style></pages><abstract><style face="normal" font="default" size="100%">I processi d'innovazione, conseguenza dei progetti di e-government, che da alcuni anni interessano gli EELL, possono essere apprezzati solo se osservati nella loro veste di azioni integrate comuni a più soggetti. Predisporre uno strumento logico-tecnologico che colmi le carenze informative e che sia di supporto, alle amministrazioni territoriali, in sede di programmazione e pianificazione delle politiche è quanto si è sperimentato in Regione Emilia-Romagna. Sono stati così realizzati una banca dati ed un applicativo web-based, entrambi basati su componenti software Open Source. Tale scelta è stata dettata dalla volontà di diffondere e facilitare questa pratica in altre realtà territoriali. Questo esperimento, oramai attività consolidata, ha prodotto risultati informativi per il territorio regionale ed è punto di partenza per un'evoluzione su scala nazionale.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Neamtiu, Iulian</style></author><author><style face="normal" font="default" size="100%">Foster, Jeffrey S.</style></author><author><style face="normal" font="default" size="100%">Hicks, Michael</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding source code evolution using abstract syntax tree matching</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">abstract syntax trees</style></keyword><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bind</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">linux</style></keyword><keyword><style  face="normal" font="default" size="100%">openssh</style></keyword><keyword><style  face="normal" font="default" size="100%">software evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword><keyword><style  face="normal" font="default" size="100%">source code analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">vsftpd</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083143</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/2Understanding.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">2-6</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Mining software repositories at the source code level can provide a greater understanding of how software evolves. We present a tool for quickly comparing the source code of different versions of a C program. The approach is based on partial abstract syntax tree matching, and can track simple changes to global variables, types and functions. These changes can characterize aspects of software evolution useful for answering higher level questions. In particular, we consider how they could be used to inform the design of a dynamic software updating system. We report results based on measurements of various versions of popular open source programs, including BIND, OpenSSH, Apache, Vsftpd and the Linux kernel.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Liu, Ying</style></author><author><style face="normal" font="default" size="100%">Stroulia, Eleni</style></author><author><style face="normal" font="default" size="100%">Erdogmus, Hakan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Understanding the Open-Source Software Development Process: a Case Study with CVSChecker</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1551</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">154-161</style></pages><abstract><style face="normal" font="default" size="100%">The open-source process model is emerging as a new lightweight paradigm for software development and has already produced several successful products. This process is fundamentally different from more traditional analysis- and design-driven processes, which raises a set of interesting research questions: what activities are carried out in open-source projects and by whom? Are there typical or exceptional patterns? CVSChecker is a tool designed to analyze the performance of individual developers and the work-distribution patterns of teams based on historical source-code repository data. In this paper, we report on a case study conducted using CVSChecker to examine a small open-source project. We discuss the insights that the CVSChecker analysis produced regarding this project and compare them to results from previous case studies performed with senior student teams.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Howison, James</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Unreliable Collaborators: Coordination in distributed volunteer teams</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">coordination</style></keyword><keyword><style  face="normal" font="default" size="100%">floss organization</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">volunteer teams</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1552</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">305-306</style></pages><abstract><style face="normal" font="default" size="100%">Drawing together the interest, skills and resources of individuals to pursue productive activity is the cornerstone of wealth creation. Recently, new forms of productive activity have emerged that draw together highly motivated, often volunteer, participants to collaborate through low-cost information systems to produce high quality products that rival those produced by wealthy firms and markets. Examples include free (librÂ´e) and open source software (FLOSS), such as Linux, and collaboratively edited texts, such as Wikipedia and the Open Directory. There is an opportunity to study these novel activities, to understand their organization, in order to both further their continued success and to assess whether and which of their novel organization techniques might be used in wider domains of human collaborative activity.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kim, Miryung</style></author><author><style face="normal" font="default" size="100%">Notkin, David</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using a clone genealogy extractor for understanding and supporting evolution of code clones</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">clone</style></keyword><keyword><style  face="normal" font="default" size="100%">clone detection</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">maintenance</style></keyword><keyword><style  face="normal" font="default" size="100%">refactoring</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083146</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/17Using.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">17-23</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">Programmers often create similar code snippets or reuse existing code snippets by copying and pasting. Code clones —syntactically and semantically similar code snippets—can cause problems during software maintenance because programmers may need to locate code clones and change them consistently. In this work, we investigate (1) how code clones evolve, (2) how many code clones impose maintenance challenges, and (3) what kind of tool or engineering process would be useful for maintaining code clones.
Based on a formal definition of clone evolution, we built a clone genealogy tool that automatically extracts the history of code clones from a source code repository (CVS). Our clone genealogy tool enables several analyses that reveal evolutionary characteristics of code clones. Our initial results suggest that aggressive refactoring may not be the best solution for all code clones; thus, we propose alternative tool solutions that assist in maintaining code clones using clone genealogy information.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Ardagna, Claudio Agostino</style></author><author><style face="normal" font="default" size="100%">Damiani, Ernesto</style></author><author><style face="normal" font="default" size="100%">Frati, Fulvio</style></author><author><style face="normal" font="default" size="100%">Montel, Martin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Open Source Middleware for Securing e-Gov Applications</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1553</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">172-178</style></pages><abstract><style face="normal" font="default" size="100%">Nowadays, a global information infrastructure connects remote parties through the use of large scale networks, and many companies focus on developing e-services based on remote resources and on interaction between remote parties. In such a context, e-Government (e-Gov) systems became of paramount importance for the Public Administration, and many ongoing development projects are targeted on their implementation and release. For open source software to play an important role in this scenario, two main technological requirements must be fulfilled: (i) the identification and optimization of de facto standards for building e-Gov open source software components and (ii) a standard integration strategy of these components into an open source middleware layer, capable of conveying a completely open-source e-Gov solution. In this paper, we argue that e-Gov systems should be constructed on a open source middleware layer, providing full public responsibility in its development. W...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Adams, Paul</style></author><author><style face="normal" font="default" size="100%">Nutter, David</style></author><author><style face="normal" font="default" size="100%">Rank, Stephen</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Open Source Tools to Support Collaboration Within CALIBRE</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1555</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">61-65</style></pages><abstract><style face="normal" font="default" size="100%">This paper describes the deployment of Plone, an Open-Source content management system, to support the activities of CALIBRE, an EU-funded coordination action integrating research into Libre software. The criteria by which Plone was selected are described, and the goodness of fit to these criteria is analysed. As a coordination action, CALIBRE involves 12 partners with different requirements and characteristics. The CALIBRE Working Environment (CWE) must therefore support a variety of users with different levels of technical expertise and expectations. Implementation of the support infrastructure for CALIBRE is ongoing, and has provided some interesting insights into the benefits of the use of libre software. Although Plone has not been explicitly developed as a collaboration infrastructure, with its wealth of plugins, it has proven highly adaptable for this purpose.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Adams, Paul</style></author><author><style face="normal" font="default" size="100%">Nutter, David</style></author><author><style face="normal" font="default" size="100%">Rank, Stephen</style></author><author><style face="normal" font="default" size="100%">Boldyreff, Cornelia</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using Plone To Support Collaborative Research</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">collaboration environment</style></keyword><keyword><style  face="normal" font="default" size="100%">collaborative research</style></keyword><keyword><style  face="normal" font="default" size="100%">content management system</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">plugin</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1558</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">296-297</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Eckert, Daniel</style></author><author><style face="normal" font="default" size="100%">Koch, Stefan</style></author><author><style face="normal" font="default" size="100%">Mitlöhner, Johann</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Using the Iterated Prisoner's Dilemma for Explaining the Evolution of Cooperation in Open Source Communities</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1559</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">186-191</style></pages><abstract><style face="normal" font="default" size="100%">Software development, and especially open source projects, typically involve repeated interactions between participants and groups of participants. We propose to analyse this situation by means of the standard model for the evolution of cooperation, the iterated prisoner's dilemma. The prisoner's dilemma is a well-known model for a two-person game, in which each side can choose to either cooperate or defect, and in which the payoffs are arranged in a defined hierarchy (e.g. the highest payoff is achieved by defecting while the other player cooperates). As a first step, the prisoner's dilemma needs to be formulated for the open source development model, i.e. what constitutes cooperation, playing defect and payoffs. Then, computer simulations using a population of stochastic reactive strategies can be applied, using a strategy's payoff as fitness measure for determining its frequency in the next generation. As a further extension, the effects of misinterpretation of other...</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Davoli, Renzo</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Virtual Square</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1560</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">76-81</style></pages><abstract><style face="normal" font="default" size="100%">It is common to call “virtual world” the set of abstractions given to humans by computers and networks. When the computers and the networks are emulated by programs, i.e. are virtual machines and virtual networks, there is one more layer of virtuality: a kind of virtual squared world. Virtual square (V²) is the project to study how to exploit the possibilities given by multi layered virtuality. V² integrates the existing technologies in system emulation with a new overlay network that is able to integrate virtual machines, real computers and processes. The virtual networking infrastructure, the educational virtual machine uMPS and the user level network virtual machine Ale4NET are original contributions made by this project. All the code developed for Virtual Square as well as all the code of the other virtual machines presented here have been released as Open Source or Free Software.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Attwell, Graham</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">What is the significance of Open Source Software for the education and training community?</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">economic issues</style></keyword><keyword><style  face="normal" font="default" size="100%">education</style></keyword><keyword><style  face="normal" font="default" size="100%">open source</style></keyword><keyword><style  face="normal" font="default" size="100%">pedagocic impact</style></keyword><keyword><style  face="normal" font="default" size="100%">training</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://pascal.case.unibz.it/handle/2038/1563</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">353-358</style></pages><abstract><style face="normal" font="default" size="100%">There is growing interest in the education community in the development and use of Open Source Software. This paper explains the ideas behind OSS and how what its significance is for education. It examines regional and national initiatives to promote the use of OSS. The paper considers the advantages of OSS and potential problems. It goes on to look at the idea of open content and the sharing of learning content, and provides short case studies. The paper concludes that the major significance of OSS and open content is in the new social relations engendered and in fostering innovation in e-learning, both in application development and new pedagogies.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sliwerski, J</style></author><author><style face="normal" font="default" size="100%">Zimmermann, Thomas</style></author><author><style face="normal" font="default" size="100%">Zeller, Andreas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">When do changes induce fixes?</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2005 international workshop on Mining software repositories</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">MSR '05</style></tertiary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">change analysis</style></keyword><keyword><style  face="normal" font="default" size="100%">cvs</style></keyword><keyword><style  face="normal" font="default" size="100%">eclipse</style></keyword><keyword><style  face="normal" font="default" size="100%">evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1082983.1083147</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/24WhenDoChanges.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><pages><style face="normal" font="default" size="100%">24-28</style></pages><isbn><style face="normal" font="default" size="100%">1-59593-123-6</style></isbn><abstract><style face="normal" font="default" size="100%">As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes—changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Karim R Lakhani</style></author><author><style face="normal" font="default" size="100%">Wolf, R.</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Feller, J.</style></author><author><style face="normal" font="default" size="100%">Fitzgerald, Brian</style></author><author><style face="normal" font="default" size="100%">Hissam, S.</style></author><author><style face="normal" font="default" size="100%">Karim R Lakhani</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Why hackers do what they do: Understanding motivation and effort in free/open source software projects</style></title><secondary-title><style face="normal" font="default" size="100%">Perspectives on Free and Open Source Software</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lakhaniwolf.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">MIT Press</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><custom3><style face="normal" font="default" size="100%">incollection</style></custom3><label><style face="normal" font="default" size="100%">lakhani2005</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Julien Bourgeois</style></author><author><style face="normal" font="default" size="100%">François Spies</style></author><author><style face="normal" font="default" size="100%">Dodero, Gabriella</style></author><author><style face="normal" font="default" size="100%">Vittoria Gianuzzi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Workshop on &quot;Open Source and Multimedia&quot;</style></title><secondary-title><style face="normal" font="default" size="100%">OSS2005: Open Source Systems </style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">360</style></pages></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kwan, Stephen K.</style></author><author><style face="normal" font="default" size="100%">Joel West</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Bolin, Sherrie</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">A Conceptual Model for Enterprise Adoption of Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">The Standards Edge: Open Season</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">Sheridan Books</style></publisher><pub-location><style face="normal" font="default" size="100%">Ann Arbor, Mich.</style></pub-location><pages><style face="normal" font="default" size="100%">51-62</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">F.M. Harper</style></author><author><style face="normal" font="default" size="100%">X. Li</style></author><author><style face="normal" font="default" size="100%">Y. Chen</style></author><author><style face="normal" font="default" size="100%">Konstan, J.A.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">An Economic Model of User Rating in an Online Recommender System</style></title><secondary-title><style face="normal" font="default" size="100%">10th International Conference on User Modeling</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pub-location><style face="normal" font="default" size="100%">Edinburgh, UK</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gregorio Robles</style></author><author><style face="normal" font="default" size="100%">Amor, J. J.</style></author><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author><author><style face="normal" font="default" size="100%">Herraiz, I.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Evolution and growth in large libre software projects</style></title><secondary-title><style face="normal" font="default" size="100%">Principles of Software Evolution, Eighth International Workshop on</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><pages><style face="normal" font="default" size="100%">165-174</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><custom1><style face="normal" font="default" size="100%">software engineering</style></custom1></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Gallivan, M. J.</style></author><author><style face="normal" font="default" size="100%">Benbunan-Fich, R.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A framework for analyzing levels of analysis issues in studies of e-collaboration</style></title><secondary-title><style face="normal" font="default" size="100%">Ieee Transactions on Professional Communication</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">48</style></volume><pages><style face="normal" font="default" size="100%">87-104</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">There has been a proliferation of competing explanations regarding the inconsistent results reported by the e-collaboration literature since its inception. This study advances another possible explanation by investigating the range of multilevel issues that can be encountered in research on the use of synchronous or asynchronous group support systems. We introduce concepts of levels of analysis from the management literature and then examine all empirical studies of e-collaboration from seven information systems journals for the period 1999-2003. We identified a total of 54 studies of e-collaboration in these journals, and after excluding 18 nonconforming studies-those that were primarily conceptual, qualitative, or exploratory only-we analyzed the levels of analysis issues in the remaining 36 empirical studies. Based on our analysis and classification of these studies into six different clusters according to their levels of analysis, we found that a majority of these studies contain one or more problems of levels incongruence that cast doubts on the validity of their results. It is indeed possible that these methodological problems are in part responsible for the inconsistent results reported in this literature, especially since researchers frequent decisions to analyze data at the individual level-even when the theory was formulated at the group level and when the research setting featured individuals working in groups-may very well have artificially inflated the authors' chances of finding statistically significant results. Based on our discussion of levels of analysis concepts, we hope to provide guidance to empirical researchers who study e-collaboration.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000227260800008</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 3</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cecchet, E.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">From research prototypes to industrial strength open source products - The ObjectWeb experience</style></title><secondary-title><style face="normal" font="default" size="100%">Sofsem 2005:Theory and Practice of Computer Science</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><volume><style face="normal" font="default" size="100%">3381</style></volume><pages><style face="normal" font="default" size="100%">17-27</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Open source software has become a common way of disseminating research results. In this talk, we first introduce the motivations and implications of releasing research prototypes as open source software (OSS). ObjectWeb is an international consortium fostering the development of open source middleware. We give an overview of tools available for OSS development and management based on ObjectWeb. experiences. The infrastructure required for hosting such developments is also described; We report various, experiences and practices of small and large ObjectWeb projects in their way to reach the quality of industrial strength products. Finally, we summarize the lessons learned from the success and failures of these projects.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000228554400002</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 0</style></notes><custom1><style face="normal" font="default" size="100%">computer science</style></custom1><custom2><style face="normal" font="default" size="100%">case study</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christoper Kelty</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Geeks, Social Imaginaries, and Recursive Publics</style></title><secondary-title><style face="normal" font="default" size="100%">Cultural Anthropology</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://www.jstor.org/stable/3651533</style></url></web-urls></urls><number><style face="normal" font="default" size="100%">2</style></number><publisher><style face="normal" font="default" size="100%">Blackwell Publishing on behalf of the American Anthropological Association</style></publisher><volume><style face="normal" font="default" size="100%">20</style></volume><pages><style face="normal" font="default" size="100%">185-214</style></pages><isbn><style face="normal" font="default" size="100%">08867356</style></isbn><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This article investigates the social, technical, and legal affiliations among &quot;geeks&quot; (hackers, lawyers, activists, and IT entrepreneurs) on the Internet. The mode of association specific to this group is that of a &quot;recursive public sphere&quot; constituted by a shared imaginary of the technical and legal conditions of possibility for their own association. On the basis of fieldwork conducted in the United States, Europe, and India, I argue that geeks imagine their social existence and relations as much through technical practices (hacking, networking, and code writing) as through discursive argument (rights, identities, and relations). In addition, they consider a &quot;right to tinker&quot; a form of free speech that takes the form of creating, implementing, modifying, or using specific kinds of software (especially Free Software) rather than verbal discourse.</style></abstract><custom3><style face="normal" font="default" size="100%">article</style></custom3><label><style face="normal" font="default" size="100%">kelty2005</style></label></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cosley, D.</style></author><author><style face="normal" font="default" size="100%">D. Frankowski</style></author><author><style face="normal" font="default" size="100%">S. Kiesler</style></author><author><style face="normal" font="default" size="100%">Terveen, L.</style></author><author><style face="normal" font="default" size="100%">Riedl, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Oversight Improves Member-Maintained Communities</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Portland OR</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kapoor, N.</style></author><author><style face="normal" font="default" size="100%">Konstan, J.A.</style></author><author><style face="normal" font="default" size="100%">Terveen, L. G.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Peer Photos Influence Member Participation in Online Communities</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Portland, OR</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yan Li</style></author><author><style face="normal" font="default" size="100%">Chuan-Hoo Tan</style></author><author><style face="normal" font="default" size="100%">Hock-Hai Teo</style></author><author><style face="normal" font="default" size="100%">Alex Siow</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">A human capital perspective of organizational intention to adopt open source software</style></title><secondary-title><style face="normal" font="default" size="100%">International Conference on Information Systems</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">Survey</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Hanson, V. L.</style></author><author><style face="normal" font="default" size="100%">Brezin, J. P.</style></author><author><style face="normal" font="default" size="100%">Crayne, S.</style></author><author><style face="normal" font="default" size="100%">Keates, S.</style></author><author><style face="normal" font="default" size="100%">Kjeldsen, R.</style></author><author><style face="normal" font="default" size="100%">Richards, J. T.</style></author><author><style face="normal" font="default" size="100%">Swart, C.</style></author><author><style face="normal" font="default" size="100%">Trewin, S.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Improving Web accessibility through an enhanced open-source browser</style></title><secondary-title><style face="normal" font="default" size="100%">Ibm Systems Journal</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">44</style></volume><pages><style face="normal" font="default" size="100%">573-588</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The accessibilityWorks project provides software enhancements to the Mozilla (TM) Web browser and allows users to control their browsing environment. Although Web accessibility standards specify markup that must be incorporated for Web pages to be accessible, these standards do not ensure a good experience for all Web users. This paper discusses user controls that facilitate a number of adaptations that can greatly increase the usability of Web pages for a diverse population of users. in addition to transformations that change page presentation, innovations are discussed that enable mouse and keyboard input correction as well as vision-based control for users unable to use their hands for computer input.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000231303100010</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 2</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Alpern, B.</style></author><author><style face="normal" font="default" size="100%">Augart, S.</style></author><author><style face="normal" font="default" size="100%">Blackburn, S. M.</style></author><author><style face="normal" font="default" size="100%">Butrico, M.</style></author><author><style face="normal" font="default" size="100%">Cocchi, A.</style></author><author><style face="normal" font="default" size="100%">Cheng, P.</style></author><author><style face="normal" font="default" size="100%">Dolby, J.</style></author><author><style face="normal" font="default" size="100%">Fink, S.</style></author><author><style face="normal" font="default" size="100%">Grove, D.</style></author><author><style face="normal" font="default" size="100%">Hind, M.</style></author><author><style face="normal" font="default" size="100%">McKinley, K. S.</style></author><author><style face="normal" font="default" size="100%">Mergen, M.</style></author><author><style face="normal" font="default" size="100%">Moss, J. E. B.</style></author><author><style face="normal" font="default" size="100%">Ngo, T.</style></author><author><style face="normal" font="default" size="100%">Sarkar, V.</style></author><author><style face="normal" font="default" size="100%">Trapp, M.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Jikes research virtual machine project: Building an open-source research community</style></title><secondary-title><style face="normal" font="default" size="100%">Ibm Systems Journal</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">44</style></volume><pages><style face="normal" font="default" size="100%">399-417</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper describes the evolution of the Jikes (TM) Research Virtual Machine project from an IBM internal research project, called Jalapeno, into an open-source project. After summarizing the original goals of the project, we discuss the motivation for releasing it as an open-source project and the activities performed to ensure the success of the project. Throughout, we highlight the unique challenges of developing and maintaining an open-source project designed specifically to support a research community.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000229333800018</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 3</style></notes><custom1><style face="normal" font="default" size="100%">information systems</style></custom1><custom2><style face="normal" font="default" size="100%">case study</style></custom2></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Sandusky, R. J.</style></author><author><style face="normal" font="default" size="100%">Gasser, L.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Negotiation and the coordination of information and activity in distributed software problem management</style></title><secondary-title><style face="normal" font="default" size="100%">International ACM SIGGROUP Conference on Supporting Group Work</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">Sanibel Island, Florida, USA</style></pub-location><pages><style face="normal" font="default" size="100%">187-196</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The social structure of Free and Open Source Software development</style></title><secondary-title><style face="normal" font="default" size="100%">First Monday</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><number><style face="normal" font="default" size="100%">2</style></number><volume><style face="normal" font="default" size="100%">10</style></volume><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>5</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors><secondary-authors><author><style face="normal" font="default" size="100%">Acuña, S.T.</style></author><author><style face="normal" font="default" size="100%">Juristo, N.</style></author></secondary-authors></contributors><titles><title><style face="normal" font="default" size="100%">Socio-Technical Interaction Networks in Free/Open Source Software Development Processes</style></title><secondary-title><style face="normal" font="default" size="100%">Software Process Modeling</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><publisher><style face="normal" font="default" size="100%">Springer Science+Business Media Inc.</style></publisher><pub-location><style face="normal" font="default" size="100%">New York</style></pub-location><pages><style face="normal" font="default" size="100%">1-27</style></pages><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Remillard, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Source code review systems</style></title><secondary-title><style face="normal" font="default" size="100%">Ieee Software</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2005</style></year></dates><number><style face="normal" font="default" size="100%">1</style></number><volume><style face="normal" font="default" size="100%">22</style></volume><pages><style face="normal" font="default" size="100%">74-77</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><accession-num><style face="normal" font="default" size="100%">WOS:000226037400020</style></accession-num><notes><style face="normal" font="default" size="100%">Times Cited: 1</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joel West</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Contrasting Community Building in Sponsored and Community Founded Open Source Projects</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/westomahony.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Siobhan O'Mahony</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Hacking Alone? The Effects of Online and Offline Participation on Open Source Community Leadership</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/omahonyferraro2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Research on computer mediated communication has examined how a lack of social presence affects participation, communication and leadership in online groups, but until recently, has not examined offline relations or emergent social structures. The few studies examining these issues have not been integrated with research on open source communities. Online communities producing open source software face even greater problems of governance than affinity or interest based online communities, as leadership responsibilities extend beyond mailing list management to managing release dates, public relations, and collaborations with firms. With data from one open source community's online and offline networks over three consecutive years, we assess factors affecting voting participation and leadership. We find that the more developers one has met face to face, the more likely one was to vote in a leadership election. Controlling for contributions of code, developers are more likely to hold a top leadership position when they participate more in online discussions. However, online participation in technical discussions did not affect leadership as much as occupying a structurally advantaged position in the community's social network. We conclude with theoretical implications that consider the dynamics of online and offline networks for governing distributed online communities.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>32</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Hacking Practices and Software Development: A Social Worlds Analysis of ICT Innovation and the Role of Free/Libre Open Source Software</style></title><secondary-title><style face="normal" font="default" size="100%">PhD Thesis</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lin2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Through use of social worlds theory and qualitative research methods, this thesis explores hackers' practices and their relationships with the computing world and the wider society from a socio-technical perspective. Through engaging with a constellation of open source practices (OSPs), actors and actants communicate, negotiate, and shape each other?s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.</style></abstract><notes><style face="normal" font="default" size="100%">Through use of social worlds theory and qualitative research methods, this thesis explores hackers' practices and their relationships with the computing world and the wider society from a socio-technical perspective. The hacker social world comprises actors from diverse social-technical backgrounds who share a constellation of im/material practices, namely open source practices (OSPs). Through engaging with these collective practices, actors and actants communicate, negotiate, and shape each other's identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.The major findings of my research are: (1) As a community of open source practices, the FLOSS social world allows diverse actors to engage in the innovation process and therefore fosters a greater innovation resource than other relatively conventional software engineering models. (2) The strategic collaboration between the public (i.e. the free software community) and the private (i.e. information technology corporations) sectors symbolises a pattern of hybrid innovation that entails complex communications and networks, though stabilizing these can be problematic. (3) Tacit knowledge anchored in everyday experiences is particularly valued in a community-based innovation system where social networking and information sharing are extensive. (4) The development of FLOSS democratises software innovation process and allows lay people to develop their understanding and knowledge of a shared problem/issue, especially through the web, to challenge established views on the issue.</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jurgen Bitzer</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Intrinsic Motivation in Open Source Software Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/bitzerschrettlschroder.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This papers sheds light on the puzzling evidence that even though open source software (OSS) is a public good, it is developed for free by highly qualified, young and motivated individuals, and evolves at a rapid pace. We show that once OSS development is understood as the private provision of a public good, these features emerge quite naturally. We adapt a dynamic private-provision-of-public-goods model to reflect key aspects of the OSS phenomenon. In particular, instead of relying on extrinsic motives for programmers (e.g. signaling) the present model is driven by intrinsic motives of OSS programmers, such as user-programmers, play value or homo ludens payoff, and gift culture benefits. Such intrinsic motives feature extensively in the wider OSS literature and contribute new insights to the economic analysis.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chen, Kai</style></author><author><style face="normal" font="default" size="100%">Schach, Stephen R.</style></author><author><style face="normal" font="default" size="100%">Yu, Liguo</style></author><author><style face="normal" font="default" size="100%">Offutt, Jeff</style></author><author><style face="normal" font="default" size="100%">Heller, Gillian Z.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open-Source Change Logs</style></title><secondary-title><style face="normal" font="default" size="100%">Empirical Softw. Engg.</style></secondary-title><alt-title><style face="normal" font="default" size="100%">http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.130.6329&amp;rep=rep1&amp;type=pdf</style></alt-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">change log</style></keyword><keyword><style  face="normal" font="default" size="100%">gcc</style></keyword><keyword><style  face="normal" font="default" size="100%">GCC-g</style></keyword><keyword><style  face="normal" font="default" size="100%">GNUJSP</style></keyword><keyword><style  face="normal" font="default" size="100%">Jikes</style></keyword><keyword><style  face="normal" font="default" size="100%">log files</style></keyword><keyword><style  face="normal" font="default" size="100%">Open-source software</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://portal.acm.org/citation.cfm?id=990374.990391</style></url></web-urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/chen.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Kluwer Academic Publishers</style></publisher><pub-location><style face="normal" font="default" size="100%">Hingham, MA, USA</style></pub-location><volume><style face="normal" font="default" size="100%">9</style></volume><pages><style face="normal" font="default" size="100%">197–210</style></pages><abstract><style face="normal" font="default" size="100%">A recent editorial in Empirical Software Engineering suggested that open-source software projects offer a great deal of data that can be used for experimentation. These data not only include source code, but also artifacts such as defect reports and update logs. A common type of update log that experimenters may wish to investigate is the ChangeLog, which lists changes and the reasons for which they were made. ChangeLog files are created to support the development of software rather than for the needs of researchers, so questions need to be asked about the limitations of using them to support research. This paper presents evidence that the ChangeLog files provided at three open-source web sites were incomplete. We examined at least three ChangeLog files for each of three different open-source software products, namely, GNUJSP, GCC-g++, and Jikes. We developed a method for counting changes that ensures that, as far as possible, each individual ChangeLog entry is treated as a single change. For each ChangeLog file, we compared the actual changes in the source code to the entries in the ChangeLog file and discovered significant omissions. For example, using our change-counting method, only 35 of the 93 changes in version 1.11 of Jikes appear in the ChangeLog file—that is, over 62% of the changes were not recorded there. The percentage of omissions we found ranged from 3.7 to 78.6%. These are significant omissions that should be taken into account when using ChangeLog files for research. Before using ChangeLog files as a basis for research into the development and maintenance of open-source software, experimenters should carefully check for omissions and inaccuracies.</style></abstract><notes><style face="normal" font="default" size="100%">&quot;We decided to compare actual differences in the source code with entries in the ChangeLog file. We used lxr, the Linux cross-referencing tool..., to determine the precise differences between two successive software versions. We then compared these differences with the records in the ChangeLog file to check the completeness of the ChangeLog file.&quot;
</style></notes></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Patterns of Free Revealing ? Balancing Code Sharing and Protection in Commercial Open Source Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">September</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/henkel2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Commercial firms increasingly contribute to the development of open source software (OSS). However, a conflict often arises between the requirements of the General Public License to make &quot;derived work&quot; available, and firms? interest to protect their intellectual property embodied in the code. If there are ways to mitigate or solve this conflict, the conditions under which OSS will be an appealing solution to firms become much more general. This paper is the first to provide a quantitative empirical study of this conflict and the ways firms deal with it. I present a study of embedded Linux, based on an online-survey that yielded 268 valid responses. It turns out that firms routinely use various means to protect their developments, while keeping the GPL. Still, they do reveal a considerable share of their code? on average, 49%. Heterogeneity between firms is analyzed using multivariate analysis. I show how the relative importance of various benefits and downsides of revealing determines a firm?s pattern of revealing. An analysis of reported reasons for revealing and of the type of code that is revealed provides further insights into these patterns. Putting the different dimensions of revealing behavior together, I find that consistent patterns of revealing can be identified for different types of firms.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Biella Coleman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">How Free Become Open and Everything Else Under the Sun</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/colemanhill.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free and Open Source Software (FOSS) has been adopted as a political tool by leftist activists. At the same time, it has been embraced by large corporations to extend profits and has been criticized as an integral force in late capitalism. It has been adopted by members of the growing Commons movement as a model for limiting the power of capitalism. This essay attempts to confront the variability of these relationships through a cursory analysis of each field and through an look at FOSS philosophy and practice. It argues that Free Software exists as a politically agnostic field of practice–built on and through a broadly defined philosophy. It analyzes the way that this philosophy is well suited for the spread of FOSS technologies and its translation into the terms of radically different, even oppositional, social and political movements.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christoper Kelty</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Papers from Anthropological Quarterly (Vol 77, No 3) - Social Thought and Commentary: Culture's Open Source</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">October</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/aq_cultures_opensources.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Listing of papers: Christopher M. Kelty | Culture's Open Sources: Software, Copyright, and Cultural Critique –- Gabriella Coleman | The Political Agnosticism of Free and Open Source Software and the Inadvertent Politics of Contrast –- Alex Golub | Copyright and Taboo –- Anita Chan | Coding Free Software, Coding Free States: Free Software Legislation and the Politics of Code in Peru–- Christopher M. Kelty | Punt To Culture–- Rosemary J. Coombe &amp; Andrew Herman | Rhetorical Virtues: Property, Speech, and the Commons on the World-Wide Web–- Glenn Otis Brown | Commentary</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jean-Michel Dalle</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SimCode: Agent-based Simulation Modelling of Open-Source Software Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/dalledavid2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">We present an original modeling tool, which can be used to study the mechanisms by which free/libre and open source software developers' code-writing efforts are allocated within open source projects. It is first described analytically in a discrete choice framework, and then simulated using agent-based experiments. Contributions are added sequentially to either existing modules, or to create new modules out of existing ones: as a consequence, the global emerging architecture forms a hierarchical tree. Choices among modules reflect expectations of peer-regard, i.e. developers are more attracted a) to generic modules, b) to launching new ones, and c) to contributing their work to currently active development sites in the project. In this context, we are able - particularly by allowing for the attractiveness of &quot;hot spots&quot;– to replicate the high degree of concentration (measured by Gini coefficients) in the distributions of modules sizes. The latter have been found by empirical studies to be a characteristic typical of the code of large projects, such as the Linux kernel. Introducing further a simple social utility function for evaluating the mophology of &quot;software trees,&quot; it turns out that the hypothesized developers' incentive structure that generates high Gini coefficients is not particularly conducive to producing self-organized software code that yields high utility to end-users who want a large and diverse range of applications. Allowing for a simple governance mechanism by the introduction of maintenance rules reveals that &quot;early release&quot; rules can have a positive effect on the social utility rating of the resulting software trees.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">James Howison</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The social structure of Free and Open Source software development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">November</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/crowstonhowison.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">Syracuse University School of Information Studies</style></publisher><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Metaphors, such as the Cathedral and Bazaar, used to describe the organization of FLOSS projects typically place them in sharp contrast to proprietary development by emphasizing FLOSS's distinctive social and communications structures. But what do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects? Questioning the assumption of distinctiveness is important because practitioner-advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production. To address this question, we examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. We found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users.</style></abstract><work-type><style face="normal" font="default" size="100%">Working Paper</style></work-type></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Collaboration, Leadership, Control, and Conflict Negotiation in the NetBeans.org Community</style></title><secondary-title><style face="normal" font="default" size="100%">4th. Workshop on Open Source Software Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">netbeans</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May 25</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/jensen.pdf</style></url></related-urls></urls><pub-location><style face="normal" font="default" size="100%">Edinburgh, Scotland, UK</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>10</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Chris Jensen</style></author><author><style face="normal" font="default" size="100%">Walt Scacchi</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Data Mining for Software Process Discovery in Open Source Software Development Communities</style></title><secondary-title><style face="normal" font="default" size="100%">Proc. Workshop on Mining Software Repositories, in conjunction with ICSE 2004</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">Edinburgh, Scotland, UK</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Yu-wei Lin</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Epistemologically Multiple Actor-Centred System: or EMACS at Work!</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/lin.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This paper analyses the innovation process of EMACS (short for Editing MACroS) from a socio-technical perspective. I investigates how actors from different backgrounds contribute multiple ways of knowing, understanding and resolving problems that arise in the innovation process. The analysis of EMACS is especially useful since it spans the period that saw the origins of the free software movement and the subsequent development of a broader free/libre open source software (FLOSS) social world.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The Jukebox Mode of Innovation: a Model of Commercial Open Source Development</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/henkel.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">In this paper, I explore the circumstances under which innovation processes without secrecy or intellectual property protection are viable, and where free revealing of innovations is a profit-maximizing strategy. Motivated by an empirical study of embedded Linux, I develop a duopoly model of quality competition. Firms require two complementary technologies as inputs, but differ with respect to the relative importance of these technologies. I find that a regime with compulsory revealing can lead to higher product qualities and higher profits than a proprietary regime. When the decision to reveal is endogenized, equilibria with voluntary revealing arise, again superior to the proprietary outcome.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>34</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Zheshi Peng</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Linux Adoption by Firms</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/peng.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The objective of this study is to examine the evolution of the market for Linux based products for the 1993-2003 period. Using data on 317 Linux suppliers available online, the differences in firms? size and in their first products were explored across the adoption stages of the Linux life cycle. Then two temporal patterns of the Linux-market were identified: changes in the entry rate of new Linux suppliers and changes in product diversity. Finally, the attributes of the partnerships formed by four major Linux distributors were examined. The study determined whether the number of partnerships formed by Linux distributors was related to the number of new entrants, whether the motives for partnerships formed by Linux distributors varied over adoption stages, and whether the type of partner selected by Linux distributors was a function of partnership motive. This study builds on the literature on open source software and traditional theories of technology adoption to make three important contributions. First, it develops a method to identify the stages of the life of a new technology. Secondly, it provides a way to measure the temporal patterns of the evolution of a new market. Finally, it validates the densitydependence model using data on open source.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Margret Elliott</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Mobilization of Software Developers: The Free Software Movement</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/elliottscacchi2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Free/open source software (F/OSS) development projects are growing at a rapid rate. Globally dispersed virtual communities with large groups of software developers contribute time and effort often without pay. One force behind this phenomenon is the Free Software Movement (FSM), a 20 year-old social movement whose purpose is to promote the use of free software instead of proprietary software. We show how the ideology of the FSM influences software development work practices in F/OSS communities and how an occupational community of F/OSS developers has emerged from this movement. We present results from an empirical study of a F/OSS development community, GNUenterprise (GNUe) whose purpose is to build an Enterprise Resource Planning system. We show how the beliefs in freedom and freedom of choice, and the values of cooperative work and community building are manifested in the GNUe norms of informal self-management, immediate acceptance of fellow contributors, and open disclosure.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Joachim Henkel</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Munich/MIT Suvey: Development of Embedded Linux</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/henkeltins.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The use of Linux in embedded devices has increased enormously in recent years. Most of the publicly available code for embedded Linux is developed and contributed by commercial firms, not by hobbyists. This raises the question if and how the development process differs from that of other OSS. This issue was addressed in a survey of embedded Linux developers yielding 268 valid responses. This paper is a collection of descriptive results from the survey.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Kevin Crowston</style></author><author><style face="normal" font="default" size="100%">Hala Annabi</style></author><author><style face="normal" font="default" size="100%">Howison, James</style></author><author><style face="normal" font="default" size="100%">Chengetai Masango</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Towards a Portfolio of FLOSS project Success Measures</style></title><secondary-title><style face="normal" font="default" size="100%">Workshop on Open Source Software Engineering, International Conference on Software Engineering</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">downloads</style></keyword><keyword><style  face="normal" font="default" size="100%">project success</style></keyword><keyword><style  face="normal" font="default" size="100%">sourceforge</style></keyword><keyword><style  face="normal" font="default" size="100%">team</style></keyword><keyword><style  face="normal" font="default" size="100%">team size</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">May</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Robert A Gehring</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Jarbuch 2004 (in German)</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The &quot;Open Source Jahrbuch 2004&quot; (open source yearbook 2004) is the first publication in German to cover the topic with an interdisciplinary approach. In contains contributions from practitioners as well as from scientists and aims to supply the reader with a comprehensive picture of how rich the open source phenomenon is. Open source means much more than only software. The subtitle of the book, &quot;Zwischen Softwareentwicklung und Gesellschaftsmodell&quot;, i.e. &quot;Between Software Development and Social Model&quot;, circumscribes the reach of this new way of dealing with information artefacts. The book is directed towards decision-makers from both politics and business as well as to scientists doing reasearch in this field. It delivers first-hand insights as a basis for understanding the potentials and constraints of open source.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">George Blanas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SOS-ware DEVILS[Strategic Open Software DEVelopment ILlnesseS]</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/blanas1.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Certain categories of software play a strategic role in contemporary public and private organizations. While software use is accelerated and diffused to more and more people and organisations, software development follows a reverse trend where fewer players form oligopolies, with some of them having almost reached a state of monopoly in certain areas. The evil consequences of such an evolution can be numerous, some of them relate to economic and security dependence and some others to phenomena of knowledge dependence and hysteresis. Within the current paper, we formulate a general framework that categorises the types of illnesses in open strategic software development from a number of viewpoints and the types of damages that could be inflicted to organizations and states as a result of false expectations if these illnesses persist. Finally, we identify the areas where research is considered to be urgently needed.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">George Blanas</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">SOS-ware [Strategic Open Software] Perspectives</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/blanas2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">Certain types of software play a strategic role in the development of the various aspects of organizational life. One of these roles is knowledge development that can act as a facilitator of economic diamonds. We review the characteristics of strategic software and we try to answer the question whether there can exist open software development that would be able to incorporate these characteristics. Based on this review, and on certain case studies, we present a theory, on how open software might be able to close the gaps in knowledge creation and usage - or the reverse, ie. to become a vehicle for an acceleration of this hysteresis.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jen-Fang Lee</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Theory Development for Organizational Platform of User Collaboration Innovation Community</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">March</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/leechan2.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">This study proposes the concept of the ?User Collaboration Innovation Community?, tries to understand this new phenomenon by conducting projects where the opening of source software is the subject of this analysis, borrows the observation variables and propositions adopted by Mintzberg on structures of the innovative organization, and summarizes the opinions of scholars of organizational economics, the relationship between property rights and organization performance. This study further infers a series of conceptual framework and propositions on the relationships among ?organization structure, property right, and organization innovation? for ?the organizational platform of the user collaboration innovation community?. We expect that the construction of this concept framework will function as a concrete description and presentation of the innovation model of the User Collaboration Innovation Community and will serve as a clear path to be followed for continuous research in the future.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Luis Lopez</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Applying Social Network Analysis to the Information in CVS Repositories</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/llopez-sna-short.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">The huge quantities of data available in the CVS repositories of large, long-lived libre (free, open source) software projects, and the many interrelationships among those data offer opportunities for extracting large amounts of valuable information about their structure, evolution and internal processes. Unfortunately, the sheer volume of that information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. In this paper, we propose the use of a well known set of methodologies (social network analysis) for characterizing libre software projects, their evolution over time and their internal structure. In addition, we show how we have applied such methodologies to real cases, and extract some preliminary conclusions from that experience.</style></abstract></record><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Jesus M. Gonzalez-Barahona</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Community structure of modules in the Apache project</style></title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">June</style></date></pub-dates></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/barahona-apache_structure.pdf</style></url></related-urls></urls><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">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 evolut
